Workflow Automation Platforms
n8n pricing: should I pick Starter or Pro if I need more concurrency and execution history/search?
7 min read
Most teams hit n8n’s pricing question the moment they move from “trying things out” to “running real workloads.” If you’re wondering whether to stay on Starter or move to Pro for higher concurrency and better execution history/search, you’re basically asking: “How much parallelism and observability do I need for production?”
Quick Answer: If you care about running more workflows in parallel and being able to search and inspect more past executions, Pro is usually the safer choice for production use. Starter is great for low-volume or non-critical workflows; Pro is built for teams that need concurrency, history, and control.
Frequently Asked Questions
How do I decide between Starter and Pro if concurrency and history are my main concerns?
Short Answer: Pick Starter if you’re testing n8n or running low-volume, non-critical automations; pick Pro if you need to run more workflows in parallel and rely on execution history/search to operate in production.
Expanded Explanation:
The key difference isn’t just the monthly price—it’s your operational risk tolerance. Starter gives you 5 concurrent executions, 2.5k saved executions, and 7 days of log retention. That’s enough to prototype, schedule a few internal automations, and get a feel for the platform. But once you start wiring in critical triggers (webhooks from your product, security alerts, customer-facing flows), you’ll feel those limits quickly.
Pro increases concurrency to 20 executions in parallel, expands max saved executions to 25k, and extends log retention to 30 days. It also unlocks workflow history and execution search, so you can actually debug, audit, and optimize flows without guessing. If you’re on the hook for SLAs—or just don’t want “we can’t see what happened” to become a recurring incident—Pro is typically the right baseline.
Key Takeaways:
- Starter is ideal for experimentation and low-risk workloads with modest parallelism needs.
- Pro is designed for production workflows where concurrency, observability, and history aren’t optional.
What’s the practical impact of the concurrency difference between Starter and Pro?
Short Answer: Starter supports 5 concurrent executions; Pro supports 20. More concurrency means your workflows don’t pile up under load and time-sensitive jobs don’t get stuck waiting.
Expanded Explanation:
“Concurrent executions” is how many workflow runs n8n will actively process at the same time. On Starter, with 5 concurrent executions, the sixth execution waits in the queue until a slot frees up. That’s fine for low-frequency automations like daily syncs or backoffice tasks.
Once you’re triggering workflows from webhooks, app events, or multiple schedules—and especially if you have steps that wait (e.g., polling, external APIs, human approvals)—5 concurrent runs can become a bottleneck. You’ll see queueing during traffic spikes and longer end‑to‑end latency.
On Pro, 20 concurrent executions gives you 4x the headroom. That’s usually enough for small teams to handle real production load without hitting a concurrency ceiling, while still keeping costs predictable under n8n’s “per execution” billing model (a single run of the entire workflow, regardless of steps).
Steps:
- Map your triggers: list webhooks, schedules, and event-driven workflows and note peak times (product releases, campaigns, end-of-month).
- Estimate concurrency: ask “how many workflows might run at once in a spike?” rather than average load.
- If you see yourself regularly crossing 5 parallel runs or you’re sensitive to latency, move to Pro for the 20 concurrent executions.
How do execution history and search differ between Starter and Pro, and why should I care?
Short Answer: Both plans log executions, but Pro adds execution search and workflow history with higher limits and longer retention—critical if you need to debug, audit, and optimize workflows over time.
Expanded Explanation:
On Starter, you get execution logging, error workflows, and “debug in editor,” plus:
- Up to 2.5k saved executions
- 7 days of execution log retention
That’s enough to debug recent issues, but you’ll lose visibility into older runs and can’t rely on long-term traces for audits or performance patterns.
Pro increases those operational tools and limits:
- Execution search: find specific runs by workflow, status, or other filters instead of scrolling
- Workflow history: track changes to workflows over time
- Up to 25k saved executions
- 30 days of execution log retention
In practice, that means you can:
- Investigate intermittent bugs by pulling all failed runs over a month
- Trace a customer issue back to a specific execution ID
- Understand when a workflow changed and whether that correlates with new errors
If you’re running workflows that touch customers, money, or security data, the ability to search historical executions and see workflow history is not a luxury—it’s basic operational hygiene.
Comparison Snapshot:
- Starter: 2.5k saved executions, 7 days retention, no workflow history/execution search.
- Pro: 25k saved executions, 30 days retention, plus workflow history and execution search.
- Best for: Teams that treat n8n as production infrastructure, not just a side tool.
What else do I get on Pro that helps run production workflows safely?
Short Answer: Beyond concurrency and history, Pro adds admin roles, global variables, more shared projects, and more AI Workflow Builder credits—tools that make it easier to run and evolve workflows in a controlled way.
Expanded Explanation:
Once multiple people are touching automation, you need some guardrails. On Pro, you still get unlimited users, but you can structure collaboration and control in a more disciplined way:
- 3 shared projects instead of 1: group workflows by domain (e.g., “Customer Ops,” “SecOps,” “Billing”) and manage access more cleanly.
- Admin roles: give specific people control over configuration and governance instead of everyone being effectively “root.”
- Global variables: centralize environment-wide values (API endpoints, feature flags, shared IDs) so you don’t hard-code them into multiple workflows.
- 150 AI Workflow Builder credits (vs 50 on Starter): more room to experiment with AI-assisted workflow creation before standardizing them.
These aren’t bells and whistles—they’re the difference between “one person’s playground” and “a shared automation platform the team can trust.”
What You Need:
- A clear sense of which workflows are production-critical vs experimental.
- At least a basic ownership model (who’s admin, who’s editor) so you can use roles and projects effectively.
How should I think strategically about Starter vs Pro as my automation footprint grows?
Short Answer: Treat Starter as a sandbox or low-risk tier; move to Pro as soon as you need predictable performance, traceability, and shared ownership across teams.
Expanded Explanation:
The cost difference between Starter ($20/mo billed annually) and Pro ($50/mo billed annually) is trivial compared to the cost of outages, missed alerts, or manual firefighting. What Pro really buys you is:
- Performance safety: 20 concurrent executions and automatic retries reduce the risk of backlogs and timeouts during spikes.
- Operational visibility: more saved executions, longer retention, workflow history, and execution search mean you can diagnose issues instead of guessing.
- Team readiness: admin roles and more shared projects let multiple teams use n8n without stepping on each other.
Because n8n bills per execution (a full workflow run from start to finish, regardless of steps), you’re not penalized for building richer workflows with proper branching, retries, and guardrails. Pro makes it easier to do the “right” thing architecturally without watching a per-step meter.
If you already know you’ll be integrating n8n into customer-facing flows, security workflows, or finance operations, starting on Pro often saves a migration step and lets you design with production needs in mind from day one.
Why It Matters:
- You reduce operational and compliance risk by having better history, search, and governance.
- You create space for your automation footprint to grow without constantly worrying about hitting concurrency or visibility ceilings.
Quick Recap
If you’re just getting started, running a few low-volume internal workflows, and don’t need deep history or team controls, Starter is a solid way to test n8n’s capabilities. But if concurrency, execution history, and search are already on your radar, you’re effectively describing Pro’s sweet spot.
Pro gives you 4x concurrency (20 vs 5), 10x saved executions (25k vs 2.5k), longer retention (30 vs 7 days), plus workflow history, execution search, admin roles, more shared projects, and more AI workflow credits. For most teams treating n8n as production infrastructure, Pro is the more appropriate baseline.