Temporal alternatives, 2026.Q3: every real option, ranked

The short answer

Edition v2026.Q3 · pricing and status verified 2026-08-06.

Inngest is the strongest Temporal alternative for most — typeScript/serverless product teams who want durable step functions, events, and per-tenant flow control (debounce, throttle, concurrency) with zero infrastructure. Then: Trigger.dev · Hatchet · Restate. Below, all 24 real options in the orchestration category, with pricing and honest watch-outs — plus the 4 "alternatives" other lists still recommend that are dead, renamed, or sunsetting.

Why people look past Temporal at all: The steepest learning curve in the category — deterministic-workflow constraints, workers, task queues — and self-hosting the server is a real ops job. Per-action Cloud pricing gets chatty-agent expensive; every tool call and retry is an action.

The top Temporal alternatives, ranked

1. 2InngestInngest

   Hobby free (50k executions/mo) · Pro from $99/mo (1M executions, 100 concurrency) · Enterprise custom

   Best for TypeScript/serverless product teams who want durable step functions, events, and per-tenant flow control (debounce, throttle, concurrency) with zero infrastructure.

   Watch The server is SSPL with delayed Apache-2.0 — practically, you're buying the cloud. Execution-count pricing punishes chatty agents, and the eval push moves it onto Ev-element turf it hasn't proven yet.

   $21M Series A led by Altimeter, with a16z (Sep 16, 2025) [src] · Agent Evals, Sessions, run scoring shipped Jun 2026; AgentKit multi-agent networks with MCP tooling [src]

2. 3Trigger.devTrigger.dev (open source, Apache-2.0)

   Free ($5/mo credit, 100k runs-ish) · Hobby $10/mo · Pro $50/mo + per-second compute (from $0.0000169/s) · Enterprise custom

   Best for TypeScript agents that need long-running managed compute — no timeouts, checkpointed runs lasting hours — plus realtime streaming to your UI.

   Watch TypeScript-only in practice, and the value is the managed compute — self-hosting the full platform is much heavier than the license suggests. Per-second machine pricing needs watching on long agent loops; smallest war chest of the top three.

   14.9k GitHub stars, Apache-2.0; v4.4.6 released May 12, 2026 [src] · Per-second compute from $0.0000169/s + $0.000025/run; Pro $50/mo with 200+ concurrent runs (Aug 2026) [src]

3. 4HatchetHatchet (YC W24)

   MIT self-host free · Cloud: first 100k runs free then $10/1M · Team $500/mo + usage · Scale $1,000/mo · Enterprise custom

   Best for Teams already on Postgres who want a fully open-source (MIT) task queue, DAG, and durable-workflow engine without adopting a new database or a restrictive license.

   Watch The cloud jumps from hobby-cheap to $500/mo Team with 500 RPS and 3-day retention — mid-size pricing is lumpy. Small team, no disclosed funding beyond YC-stage, and Postgres becomes your scaling ceiling.

   7.3k GitHub stars, MIT license; hatchet-cli 0.88.0 released Jun 1, 2026 [src] · Cloud: 100k runs free, then $10/1M; Team $500/mo, Scale $1,000/mo w/ HIPAA (Aug 2026) [src]

4. 5RestateRestate (Stephan Ewen, Flink co-creator)

   Single-binary self-host (BSL 1.1 → Apache after 4 yrs) · Cloud free 50k actions/mo · usage plans from $75/mo · BYOC capacity pricing

   Best for Latency-sensitive, stateful agents and transactional workflows — virtual objects and durable promises in one Rust binary instead of a cluster.

   Watch Smallest community of the five (~4k stars) and BSL 1.1 is not open source — the license blocks offering Restate as a service. The architecture is novel enough that hiring for it is hard; funding beyond seed unverified.

   Restate Cloud public Sep 30, 2025: free 50k actions/mo, plans from $75/mo, BYOC 'up to 10x cheaper' (vendor claim) [src] · v1.6.2 (Feb 13, 2026), Rust runtime; SDKs for TS, Java/Kotlin, Python, Go, Rust; ~4k stars [src]

Every other live option in orchestration

The "Temporal alternatives" to avoid — no longer what they were

Listicles still recommend these. As of 2026-08-06, they are not what the listicles think.

How to choose

If agents touch money, customers, or anything you'd page someone over

Temporal — the learning curve is the price of the only orchestrator with OpenAI-scale production proof. Budget real onboarding time and watch per-action costs on chatty agents.

If you're a TS/serverless product team and your pain is events, retries, and per-tenant fairness (rate limits, debounce, concurrency)

Inngest — its flow-control primitives are the category's best, and the free 50k-execution tier covers most pre-launch products.

If your agent runs are long-lived compute (scraping, video, deep research) and you don't want to own workers

Trigger.dev — the only top pick that sells you the machines too, with checkpointed no-timeout runs.

If you already run Postgres and refuse non-OSS licenses

Hatchet for a standalone MIT engine, or DBOS if you'd rather add a library to your app than a service to your stack — Microsoft's pg_durable (Jun 2026) says this whole approach is directionally right.

If you're pre-PMF and tempted by all of the above

Don't over-buy. A cron, a queue, and your deploy platform's built-in workflows (Vercel, Cloudflare) cover more than you think — adopt real orchestration when a failed retry first costs you money.

This analysis is drawn from the Orchestration element dossier — the ranked top 5, the comparison matrix, and the complete field of 24 more tools live there, with every source. Data: or.json (CC BY 4.0).