editor vs workflow-builder-template
Two of the top ai editors and workflow canvases, side by side: score, setup, license, activity and what each review found.
editor
Notion-style Nuxt editor with AI completions and optional collaboration
workflow-builder-template
Visual AI workflow builder on Workflow DevKit with real integrations
| What we compare | editor | workflow-builder-template |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 5, niche | 68, popular |
| Freshness | 100, active | 34, slowing |
| Maintenance | 33, patchy | 0, weak |
| Easy to run | 67, easy | 33, some setup |
| Agent-ready | 0, none | 30, minimal |
| Facts from GitHub and the README | ||
| Stars | 171 | 1.2k |
| License | MIT (permissive) | Apache-2.0 (permissive) |
| Last commit | Oct 2026 | Jan 2026 |
| Last release | None published | None published |
| Language | TypeScript | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
editor
Nuxt template on the Nuxt UI Editor component and TipTap: headings, tables, slash commands, drag handle, mentions, emoji, markdown output and image upload via NuxtHub Blob. AI features (inline completions, continue, fix grammar, extend, simplify, summarize, translate) stream through AI SDK useCompletion and Vercel AI Gateway; collaboration uses Y.js with PartyKit. Scaffold with npm create nuxt -t ui/editor.
Who it is for: Vue and Nuxt teams adding an AI writing editor
Strengths
- AI, blob storage and collaboration are each optional and env-gated
- One AI Gateway key instead of per-provider keys
- Collaboration via Y.js, swappable from PartyKit to Liveblocks or Tiptap
- Live demo at editor-template.nuxt.dev
Weaknesses
- No auth or document persistence; content is not saved server-side
- Collaboration requires deploying a separate PartyKit server
- Translate supports English, French, Spanish and German only
- No tests
- TypeScript, Vercel AI Gateway via AI SDK useCompletion
- Needs Vercel AI Gateway key (optional), Blob storage: Vercel Blob, R2 or S3 (optional), PartyKit (optional)
- GitHub template
- env example file
workflow-builder-template
Next.js 16 app with a React Flow canvas, Monaco editor, Better Auth, Drizzle on Postgres and Workflow DevKit execution. Trigger nodes (webhook, schedule, manual, database event) feed plugins for AI Gateway, Resend, Linear, Slack, GitHub, Stripe, Firecrawl, Perplexity, fal.ai, Clerk, Blob, v0, Webflow and Superagent; workflows can be generated from a prompt and exported as TypeScript with the use workflow directive.
Who it is for: Teams building a Zapier-style AI automation product
Strengths
- Fourteen integration plugins with executable step code, not mocks
- Workflows export to TypeScript with the use workflow directive
- Execution history and per-node logs stored in Postgres
- Better Auth and Drizzle already wired
Weaknesses
- Each integration needs its own API key
- AI generation goes through Vercel AI Gateway only
- Last commit 2026-01
- Built on Workflow DevKit; swapping the engine is a rewrite
- TypeScript, Vercel AI Gateway (OpenAI GPT-5)
- Needs PostgreSQL, Vercel AI Gateway API key, integration API keys (Resend, Linear, Slack, Stripe and others)
- GitHub template
- sign-in: Better Auth