I built Workflow Automation Platform (only vibe code it) - Looking for Feedback

Published: (January 18, 2026 at 06:01 AM EST)
2 min read
Source: Dev.to

Source: Dev.to

Overview

I just shipped ynode – an open‑source visual workflow automation platform. Think n8n, but lighter and more hackable.

What it does

  • Visual node‑based workflow builder (React Flow + TypeScript)
  • Create custom nodes via CLI (and using Node Assembler – in‑app editor)
  • Full‑stack: Vite frontend, Express backend, BetterSQLite storage
  • Extensible architecture with a pnpm monorepo

Tech stack

Frontend: React 19, Vite, React Flow
Backend: Node.js, Express, WebSocket
Database: SQLite with credential encryption
Language: TypeScript throughout

Why I’m sharing

  • Looking to get hired as a “vibe‑coder”
  • Exploring how to build profitable products with this approach

What I’m looking for

  • Honest feedback on the codebase – is it maintainable? Would you use it?
  • Use‑case ideas – what would you actually automate with this?
  • Direction – should I focus on turning this into a product, or keep it as a portfolio piece?

Repository

https://github.com/iamyureka/ynode

Try it, break it, fork it. I want to know if this is actually useful or just another side project collecting dust.

Current state

  • Fully functional local setup
  • Custom node generation via CLI
  • Clean monorepo architecture

Questions for the community

  1. Have you monetized projects built primarily with AI assistance?
  2. What makes a workflow automation tool worth paying for?
  3. Am I solving a problem that actually exists?
  4. Are “vibe‑coding” skills actually valuable for getting a job?

Note

Real talk: I can ship products fast this way, but I’m not sure if that translates to actual opportunities. Feedback welcome.

I am sorry for the tone 🙏

Back to Blog

Related posts

Read more »

Setup MonoRepo in Nest.js

Monorepos with Nest.js Monorepos are becoming the default choice for backend teams that manage more than one service or shared library. Nest.js works very well...