TODO for AI
vs 
n8n
By Marcell Havlik, founder of TODO for AI · Updated
Fair-code workflow automation you can self-host, priced per whole workflow run. Here is where each one wins, with numbers, and who should pick which.
| Fact | n8n | TODO for AI |
|---|---|---|
| Interface | Web, self-hosted or cloud | Web, desktop, mobile, CLI, IDE (Zed, JetBrains, VS Code), voice |
| Models | Any, you supply the keys | Claude, GPT, Gemini, Grok and other supported models |
| Source | Partly open | Edge + CLI public |
| Starts at | Self-host free | Free |
Key takeaways
- Models. n8n model choice: Any, you supply the keys. TODO for AI includes Claude, GPT, Gemini and Grok on paid plans. Pick the model for each job; let another review the result.
- Benchmark. TODO for AI scored 91.0% on Terminal-Bench 2.1 with Opus 5.5 (high) (own harness, 81/89 tasks, 2026-10-26; not an official leaderboard submission).
- Price. n8n pricing: Community Edition free to self-host under a fair-code licence. Cloud Starter €20/month for 2,500 executions, Pro €50 for 10,000, Business €667 self-hosted for 40,000, Enterprise custom. TODO for AI has a free plan (Claude Sonnet only), then Starter $20, Pro $100 or Ultra $200 a month with the supported multi-vendor catalog.
- Shared business work. TODO for AI: Your whole team and its AI agents, on one board. Shared company context, brand voice and memory. AI working in your connected tools, signed-in browser and machines.
- Included usage. One shared pool of credits, with the cloud VM and browser included. Personal session and weekly limits apply. Credit usage depends on the model; see the pricing page for plan details.
- Who should pick which. Pick n8n if Data must stay on your own infrastructure. Pick TODO for AI if the people with the work are not going to build workflows.
n8n
Any, you supply the keys
TODO for AI
Supported vendorsWhere our product fits
One board for the company’s work.
People decide. Agents do the work.
Your whole team and its AI agents, on one board. Shared company context, brand voice and memory. AI working in your connected tools, signed-in browser and machines.
Chase the invoice. Ship the website update. Prepare the report. Fix the code. Every task keeps its request, contributors and result together, ready for the next colleague or agent to pick up.
Keep n8n where it fits. Bring the rest of the company’s backlog here.
Plans and usage limitsWhat n8n is, and where it stops
n8n is the developer's answer in this category. Self-host it and the data never leaves your infrastructure, the Code node runs real JavaScript or Python, the Execute Command node reaches the host itself, the AI agent nodes are the deepest here, and executions are counted per whole workflow run rather than per step, so elaborate workflows are not punished. For a technical team it is the best value in automation.
It asks for a developer, though. Building in n8n means understanding nodes, expressions and data shapes, which is why it rarely spreads past the person who set it up. And it remains a builder: the workflow exists before the value does. Self-hosting is free in the sense that your own uptime, upgrades and secret management are free.
Technical teams who want automation they can self-host and extend in code.
Three reasons n8n users look elsewhere
n8n workflows tend to live with whoever built them. A colleague who wants the same job done writes a ticket rather than a workflow.
The workflow has to exist before it runs. A task you would describe once in a sentence never justifies the build.
Self-hosted, the Execute Command node reaches the host you administer, which is a real capability and a real security decision. On Cloud there is no such host at all, and neither mode gives an agent a session in your own logged-in Chrome.
Six dimensions that decide it
n8n 23/30TODO for AI 28/30How does n8n compare to TODO for AI, feature by feature?
| Feature | n8n | TODO for AI |
|---|---|---|
Persistent cloud VM A hosted workspace with persistent files, separate from the machines you connect. | Your own server, self-hosted | Yes |
Model choice | Any, your own keys | Supported models across vendors |
Cross-vendor review Review GPT output with Claude, or the other way around. | No | Yes |
Drives your real browser Browser extension (Chrome, Firefox) plus cloud browsers. | Community browser nodes | Yes |
Business tasks, not only code SEO, email, ads, social, CRM via CLI tools. | Nodes + HTTP + code | Yes |
Any CLI as an integration | Code node + MCP | Any binary |
Voice control | No | Yes |
People and agents on one board Colleagues and agents work the same list. Items show who contributed and which agent ran them; filter the board by person. | No | Yes |
Many agents, each configured Each agent gets its own model, prompt, tools and permissions. Runs remain subject to usage limits. | AI agent + LangChain nodes | Configured per task |
Projects for the whole company Engineering, marketing, ops, finance: separate projects and agents, one team and one bill. | Workflows and projects | Unlimited, shared |
Team roles and usage Pooling is not exclusive to TODO for AI. A shared budget does not remove personal session or weekly limits. | Seats, self-host unlimited | Shared credits, per-seat limits |
Tool permissions | Project-level | Allow, approve, block |
Open runtime | Fair-code, self-hostable | Edge + CLI public |
Same ladder, different meter
Executions count whole workflow runs with unlimited steps inside, which is the friendliest meter in this category. Model calls are billed by whichever provider's key you supply.
One shared pool of credits, with the cloud VM and browser included. Personal session and weekly limits apply. Credit usage depends on the model; see the pricing page for plan details.