TL;DR
Temporal is MIT-licensed workflow orchestration with ~12k GitHub stars, used in production by Stripe, Snap, and Coinbase. Temporal Cloud starts at $100/month with no free production tier — a deliberate signal that this is serious infrastructure, not a prototyping toy.
- Essentials at $100/month covers 1M actions, 1GB active storage, 40GB retained storage
- Business at $500/month adds SAML SSO, 2.5M actions, 2.5GB active, 100GB retained
- Enterprise starts at 10M actions, contact sales; pay-as-you-go is an alternative to flat plans
- Startup program gives $6,000 in credits to sub-$30M-funded companies — roughly 5 years of Essentials
- Billing by "actions" maps directly to workflow logic, which is more predictable than compute-time pricing
This post is a part of series on commercial open source software pricing. See full list of articles here.
Temporal is a workflow orchestration engine — it lets you write durable, fault-tolerant business processes in regular code. Your workflow can run for days, survive server crashes, and resume exactly where it left off. ~12k GitHub stars, used by Stripe, Snap, Coinbase, and a bunch of other companies where reliability actually matters. They raised a $300M Series D at a $5B valuation, which tells you something about how seriously the market takes this.
- Website: temporal.io
- Pricing: temporal.io/pricing
- GitHub: github.com/temporalio/temporal
Plans
- Essentials — $100/month: 1M actions, 1GB active storage, 40GB retained storage.
- Business — $500/month: 2.5M actions, 2.5GB active, 100GB retained, SAML SSO.
- Enterprise: Contact sales, starts at 10M actions.
- Pay-as-you-go: Available as an alternative to flat plans.
- Startup program: $6,000 in free credits for companies with less than $30M in funding.
"Actions" is the right billing unit — and it's not obvious why
Most infrastructure tools bill by compute time, users, or seats. Temporal bills by "Actions" — discrete operations between your application and Temporal Cloud (scheduling an activity, completing a task, processing a signal, etc.).
This is unusual because Actions directly map to how much work your workflows are doing, not how long a server ran or how many people accessed the dashboard. A simple linear workflow might use 5-10 actions. A complex multi-step business process with retries, timers, and signals might use hundreds per run.
The implication: you can model your costs based on your actual business logic. A company processing 10,000 orders/day with a 5-action checkout workflow needs ~50M actions/month. That maps to Enterprise territory. A startup running a 3-action onboarding workflow at 1,000 new users/month needs 3M actions — well inside Essentials.
This is actually more predictable than compute-based pricing, where a bad deployment or retry storm eats your budget. Actions scale linearly with your actual workload.
The $100 floor is a statement
The Essentials plan starts at $100/month. There's no free tier for production use (startup credits aside). This is intentional — Temporal Cloud is not positioning itself as a cheap commodity. It's an infrastructure layer for serious production workflows.
$100/month is cheap for what it does. But the pricing signal says: if you're still prototyping, self-host. If you're in production, $100 is a rounding error compared to the cost of your engineers debugging a workflow that died in a multi-step process.
Self-hosting is real — and hard
Temporal's OSS is MIT licensed and fully functional. Companies do run it in production. But Temporal itself (the server, the cluster, Cassandra or Elasticsearch as backends) is genuinely complex to operate. The self-hosted path is not "run docker-compose and forget it."
The Cloud pricing confidence comes from this: they know their users are technical enough to know the infra cost of running Temporal themselves. $100/month for a managed, SLA-backed cluster is cheap when you factor in the engineering hours to maintain it.
The startup program is generous
$6,000 in free credits for sub-$30M-funded companies is roughly 5 years of Essentials at full price, or 1 year of Business. That's long enough to get to meaningful scale before you're paying. Sensible growth-stage acquisition strategy.
License
MIT for the core Temporal server and SDKs. You can self-host, fork, and run it commercially without restrictions. The managed cloud product (Temporal Cloud) is obviously proprietary. Clean separation.
Worth paying for?
If you're running anything in production where workflow failures cost real money or real user pain — yes, absolutely. Self-hosting is technically free but operationally expensive. The $100/month Essentials plan is a bargain against 1-2 engineering hours of debugging a failed workflow. The startup credits make the entry math even easier.
How Temporal pricing scales
Temporal has no free production tier — it starts at $100/month, and SAML SSO forces the $500/month Business tier.
Temporal pricing by tier. SSO lives on Business at 5× Essentials.
This post is a part of series on commercial open source software pricing. See full list of articles here.
I build Beton — open source revenue intelligence for B2B SaaS.
FAQ
Is Temporal open source?
Yes. The Temporal server and SDKs are MIT licensed — you can self-host, fork, and run it commercially without restrictions. Temporal Cloud, the managed product, is proprietary.
What's the cheapest Temporal Cloud plan?
Essentials at $100/month, which includes 1M actions, 1GB active storage, and 40GB retained storage. There is no free tier for production use beyond the startup credits program.
Why does Temporal bill by 'actions' instead of compute time or seats?
Actions are discrete operations between your application and Temporal Cloud — scheduling an activity, completing a task, processing a signal. They scale linearly with your actual workflow logic, which makes cost modeling more predictable than compute-based pricing where a retry storm can eat your budget.
Should I self-host Temporal instead of paying for Cloud?
You can — the OSS is MIT and fully functional. But operating the Temporal server with Cassandra or Elasticsearch backends is genuinely complex. For production workloads, $100/month for a managed, SLA-backed cluster is cheap against the engineering hours to maintain it yourself.
