Developer ToolsTempl
Type-safe HTML templating language for Go with compile-time safety
Inngest
Developer ToolsFreemiumDurable workflows, background jobs, and AI agents with zero queue plumbing
82/100
7 min readScreenshots
Inngest turns ordinary TypeScript, Python, or Go functions into durable, retryable step workflows without running Redis, Kafka, or Temporal. It is the fastest way to add reliable background jobs and AI agent orchestration to a serverless stack — if you can live with the SSPL licensing and resource-based pricing.
Inngest is a durable-execution platform that turns ordinary TypeScript, Python, or Go functions into retryable, stateful step workflows — no queues, no Redis, no separate worker pool required. We rate it 82/100 — for teams shipping background jobs, scheduled tasks, webhooks, and AI agent orchestration on serverless, it is the fastest path from idea to reliable production today. It is the wrong call for teams that require a fully self-hostable, Apache-2 licensed engine or prefer flat, predictable pricing tiers.
Inngest was founded in by Tony Holdstock-Brown (CEO) and Dan Farrelly (CTO), and has since raised a $6.1M seed round announced in and a $20M Series A led by Notable Capital in . The open-source core at github.com/inngest/inngest sits at roughly 5.2k stars, written in Go (60%) and TypeScript (39%), with active releases through April 2026.
The specific problem Inngest solves is what developers on Hacker News call the queue tax: every production backend eventually needs background jobs, retries, scheduling, fan-out, and long-running workflows, which traditionally means running Redis plus a queue library plus a worker pool plus dead-letter-queue monitoring plus state tracking. Inngest collapses all of that into a single SDK call — you write a normal function with step.run() and step.sleep() blocks, and Inngest handles durability, retries, and state transparently, even across serverless timeouts. Unlike Trigger.dev, which is TypeScript-first and task-centric, Inngest is fully event-driven and multi-language (TS, Python, Go, Java).
step.run() and Inngest persists its result so that retries resume from the last successful step. This eliminates the need to hand-roll idempotency keys for most workflows.step.waitForEvent() for days or weeks without consuming compute — you pay only for actual step executions.AgentKit SDK ships with routing, tool-use, and multi-agent patterns, and Inngest handles the durability and retries that LLM calls need (timeouts, rate limits, provider outages).
Sentiment on the Inngest 1.0 Show HN thread is broadly positive about developer experience but sharply critical about licensing. Multiple top commenters praised the dashboard, SDKs, and support as “top notch,” with one video-pipeline operator writing that they have used it for years and “it has always felt really polished.” A recurring pattern on r/webdev and r/typescript is the same story: teams replace a messy combination of BullMQ, Redis, cron jobs, and custom state tables with a single Inngest setup and cut both code and operational surface area.
Two complaints come up repeatedly. First, Inngest’s core server is licensed under the Server Side Public License (SSPL), not a true OSI-approved open-source license — several HN commenters accused the marketing of being misleading on this point. Second, full production self-hosting is not yet a shipped feature; the local dev server is open and free, but the production engine is Inngest Cloud only. Teams with hard on-prem or air-gapped requirements are better served by Temporal today.
Inngest uses a usage-based model keyed on step executions, not seats. The free tier is meaningful: 50,000 monthly executions is enough for many small production workloads.
| Plan | Price | Key Limits |
|---|---|---|
| Hobby | $0/mo | 50,000 executions, 5 concurrent steps, 3 users, 50 realtime connections, unlimited branch environments, community support |
| Pro | From $75/mo | 1M executions (up to 20M with add-ons), 100+ concurrent steps, 15+ users, 1,000+ realtime connections, 7-day trace retention, granular metrics |
| Enterprise | Custom | 500–50,000 concurrent steps, SAML/RBAC/audit logs, 90-day trace retention, exportable observability, dedicated Slack support |
| Overage | $0.00005 per step | Tiered, drops to $0.000015/step above 50M/month — volume discounts automatic |
Best for: startups and growth-stage engineering teams running backend workflows on serverless or hybrid infrastructure; TypeScript, Python, Go, and Java shops that want durable execution without running a dedicated cluster; teams building AI agents that need retries, tool-use, and human-in-the-loop pauses; anyone replacing a tangled BullMQ + Redis + cron setup.
Not ideal for: teams with strict on-prem, air-gapped, or SSPL-incompatible constraints today; organisations that require Apache-2 / MIT licensed dependencies; workloads that need millisecond-scale event processing (this is orchestration, not streaming — use Kafka).
Pros:
waitForEvent is more expressive than task-centric alternatives for long-running business workflowsCons:
Trigger.dev — TypeScript-first, task-centric, Apache-2 licensed and fully self-hostable today; the natural pick if TypeScript is your only language and licensing matters. Temporal — the battle-tested enterprise standard with the deepest self-hosting story and the steepest learning curve; better for on-prem and mission-critical workloads at giant scale. n8n — visual, no-code workflow builder rather than code-first; better for non-engineering teams, weaker for engineers who want to keep logic in their repo.
Yes, for most TypeScript, Python, or Go teams building durable workflows, background jobs, scheduled tasks, or AI agents in 2026 — Inngest is the fastest on-ramp to reliable execution in the category, and the Hobby tier is enough to run real production traffic. The 82/100 rating reflects a category-leading developer experience offset by two honest caveats: the SSPL licensing and the lack of production self-hosting. If neither blocks you, you will be shipping durable workflows by lunchtime. If either does, ship on Trigger.dev or Temporal instead.
Developer ToolsType-safe HTML templating language for Go with compile-time safety
Developer ToolsOpen-source API key management and rate limiting platform for modern developers
Developer ToolsOpen-source low-code platform for building internal business applications
Developer ToolsGit-friendly open-source API client for REST, GraphQL, and gRPC
ServiceNow and Accenture Launch Forward Deployed Engineering Program to Scale Agentic AI in the Enterprise (May 6, 2026)
At Knowledge 2026, ServiceNow and Accenture announced a joint forward deployed engineering program that drops co-located engineer pods into customer environments to ship agentic AI workflows natively on the ServiceNow AI Platform — with access to 300+ pre-built agent skills and the AI Control Tower as the governance backbone.
May 7, 2026
ReFiBuy Raises $13.6M Seed to Help Brands Get Recommended by AI Shopping Agents (May 5, 2026)
ReFiBuy, the Raleigh-based agentic commerce platform from ChannelAdvisor founder Scot Wingo, closed an oversubscribed $13.6M seed led by NewRoad Capital Partners on May 5, 2026 — betting that the next billion-dollar e-commerce moat is being chosen by ChatGPT, Claude and Perplexity.
May 7, 2026
OpenAI Replaces ChatGPT's Default Model With GPT-5.5 Instant — 52.5% Fewer Hallucinations, 30% Shorter Answers (May 5, 2026)
OpenAI on May 5 swapped GPT-5.3 Instant for the new GPT-5.5 Instant as ChatGPT's default model, claiming 52.5% fewer hallucinated claims on high-stakes prompts and 30% more concise answers. The model also rolls into the API as chat-latest and adds personalization from Gmail and past chats for Plus and Pro web users.
May 7, 2026
Is this product worth it?
Built With
Compare with other tools
Open Comparison Tool →