Inngest pricing, free plan and limits

Last updated: 2026-09-04

Launched in 2021, Inngest is a serverless, event-driven workflow engine for background jobs, scheduled tasks, and multi-step AI pipelines that needs no queue or worker infrastructure to manage. Each function step retries independently instead of restarting the whole run, functions deploy natively alongside Vercel, Cloudflare Workers, or any Node.js backend, and the open-source core engine can be self-hosted.

About Inngest

Inngest is an event-driven durable workflow platform founded in 2021 by Tony Holdstock-Brown and Dan Farrelly. The company has raised $34M across four rounds including a $3M seed in July 2023 from GGV Capital and a $6.1M Series A in January 2024 from Andreessen Horowitz, with a Series B in May 2025. Based in San Francisco with a 9-person team, Inngest lets developers build reliable background jobs, scheduled workflows, and AI agent tasks on serverless platforms without managing infrastructure.

The platform is serverless-first: TypeScript, Python, and Go SDKs deploy alongside your existing app on Vercel, Cloudflare Workers, Hono, or any Node.js backend, with the orchestration engine and dashboard hosted by Inngest rather than self-managed. The core engine is open-source and can be self-hosted, though the cloud product's dashboard, managed infrastructure, and observability stack stay cloud-only. Inngest added MCP (Model Context Protocol) support to its local dev server in 2026, letting Claude Code, Cursor, and other AI assistants connect directly to functions for debugging. The company states in its footer that Inngest is SOC 2 Type II compliant company-wide, with SAML, RBAC, audit trails, and HIPAA BAAs available as Enterprise add-ons.

Inngest competes with Trigger.dev, which runs compute but lacks the event-driven model, Temporal, which is enterprise-grade, self-hosts natively, and carries heavier infrastructure overhead, and traditional queue systems like BullMQ. Reviewers point to the combination of event-driven architecture, zero infrastructure on Vercel, and a free Hobby tier as the main reason early-stage teams pick it over those alternatives.

Screenshots

Pricing

Hobby: $0/month, 50,000 executions and 500,000 events included, 5 concurrent steps, 3 users, 3 workers. Pro: $99/month, 1,000,000 executions included with metered pay-as-you-go overage up to 20M, 100 concurrent steps, 15 users, 20 workers, 5,000,000 events included. Enterprise: custom pricing with SAML, RBAC, audit trails, and HIPAA BAAs.

50 per 1K; execution overage itself is metered at tiered rates Inngest does not publish as a flat figure. All plans include unlimited dev and staging environments, and the core engine can be self-hosted, though the managed dashboard and observability stack are cloud-only.

Key Features

• Event-Driven Workflows: Everything is triggered by events, eliminating the need to manage traditional queues or worker processes. Functions respond to events from webhooks, external services, or scheduled triggers.
• Step-Level Durability: Each step is backed by its own queue job with automatic retry on failure, saving costs and complexity compared to queue-level durability approaches used by other platforms.
• Multi-Tenant Flow Control: Built-in concurrency, throttling, rate limiting, prioritization, and debouncing controls handle multi-tenant fairness and reliability without custom implementation.
• Scheduled and Cron Jobs: Schedule jobs to run minutes or weeks into the future, enabling time-delayed workflows, deferred notifications, and reminder systems without additional infrastructure.
• Native Vercel Integration: Automatically syncs deployed code, sets environment variables, and manages infrastructure synchronization when you deploy Next.js apps, eliminating manual setup and worker processes.
• Event History and Replay: Stores full event history for observability, testing, and replay. Re-run failed workflows in bulk or test with historical events without re-triggering real upstream sources.

Pros

• The free Hobby tier is enough for most side projects and early-stage startups to run real background jobs without paying anything upfront.
• Automatic step-level retries mean a single flaky step gets retried in isolation rather than re-running an entire multi-step workflow, which reviewers say saves real debugging time.
• MCP support lets you debug and trigger functions directly from Claude Code or Cursor, a convenience most workflow platforms don't offer yet.

Cons

• The open-source core engine can be self-hosted, but the dashboard, managed infrastructure, and full observability stack are cloud-only, so a self-hosted deployment gives up most of what makes the hosted product easy to run.
• Every piece of workflow logic has to be wrapped in explicit step.* calls with cache keys for resumability, which is more verbose than Trigger.dev's plain async function style.
• Documentation thins out fast for advanced cases like multi-region setups and integration troubleshooting, so non-standard architectures take more trial and error to get working.
• Pro pricing adds up fast once you exceed the included limits: extra users, workers, span data, evaluation scores, and concurrent steps are each billed as separate line items on top of the $99/month base.

Visit Inngest Official Website