Last updated: 2026-10-13
Temporal is an open source (MIT) durable execution platform that runs business workflows as code, with SDKs in 7 languages. Its server persists every workflow step, so a run resumes exactly where it stopped after a crash, a deploy or a pause lasting months, without hand-written retry or timeout logic.
About Temporal
Temporal is a durable execution platform. You write a business process as ordinary code, and the Temporal server records each step so that a workflow can crash, redeploy or sleep for months and then continue from the exact point it stopped. Instead of building retry queues, timers and state machines for every service, teams lean on the platform for automatic retries with backoff, durable timers, signals and queries. Its founders co-created the Cadence workflow engine at Uber, and the company reports more than 2,900 customers, with Stripe, Datadog and Snapchat named on its own about page.
The core platform is open source under the MIT license, so you can run the whole thing yourself at no licence cost, with SDKs for Go, Java, Python, TypeScript, .NET, Ruby and PHP. The alternative is Temporal Cloud, the managed service, which moved to published pay-as-you-go pricing: no base fee, a per-Action rate, and storage billed by the GB-hour. Business, Enterprise and Mission Critical add support rather than features, because the vendor says no features are locked behind plan upgrades. Cloud lists SOC 2 and HIPAA support, a 99.9% SLA and a 99.99% option with high availability. The pricing page also lists durable AI agent support through the OpenAI Agents SDK and Google ADK, marked as a preview, which makes Temporal relevant to teams building long-running agents on models from OpenAI and others.
Where does it fit? Payment flows, order pipelines, provisioning jobs and any process that spans several services and must not lose state are the natural use. If you want a lighter route, Inngest targets event-driven functions on serverless platforms and Trigger.dev targets TypeScript stacks, while visual builders like n8n, Zapier and Make suit teams that would rather not write workflow code at all. See the AI development services directory for related infrastructure, or read the guide on automating repetitive work with AI without writing code.
The other side of the argument is real. Temporal asks engineers to learn a programming model with deterministic workflow code, separate workers and versioning rules, and that onboarding cost is high for a team that only needs a nightly job or a webhook handler. Self-hosting a production cluster takes genuine operational skill, and Cloud costs scale with Actions, so chatty workflows can surprise a budget; the vendor's pricing FAQ covers how to estimate Action counts before committing. Simple CRUD services and single-step scripts do not need durable execution. Not sure whether you do? Describe the job to Smart Match and compare it with lighter options before adopting a workflow engine.
Pricing
Self-hosting the open source platform costs nothing beyond your own infrastructure. 00105 per GB-hour for Retained Storage. Developer support is billed at 10% of usage.
New accounts get $150 in credits that expire after 90 days, and a card is required to sign up. 5M Actions; Enterprise and Mission Critical are annual commitments quoted by sales. Replicating a namespace for high availability doubles its Action and Storage charges.
Startups under $30M in funding can apply for $6,000 in credits. dev](/hub/tools/trigger) and Inngest, or browse the workflow automation directory.
| Tier | Monthly price | What it includes |
|---|---|---|
| Open Source (self-hosted) | Free | Full platform: Temporal Service, UI and CLI, MIT license, Seven language SDKs, plus the CLI and web UI, Community support via Slack and forum, You run and scale the cluster yourself |
| Temporal Cloud (pay-as-you-go) | Free | No base monthly fee, $50 per million Actions at the entry rate, stepping down with volume, $0.042 per GB-hour Active Storage, $0.00105 Retained Storage, 99.9% SLA, 99.99% with high availability, SAML SSO, audit logging, API keys, service accounts, Developer support billed at 10% of usage |
| Business | $500/mo | 2.5M Actions, 2.5 GB Active and 100 GB Retained Storage included, 2-business-hour P0 response, Commitment discounts on 1, 2 or 3 year terms, Provisioned capacity available, SCIM as a $500 a month add-on |
| Enterprise | Custom | 10M Actions, 10 GB Active and 400 GB Retained Storage included, 24/7 support, P0 response under 30 minutes, Private Slack channel, SCIM included, Annual commitment, contact sales |
| Mission Critical | Custom | Everything in Enterprise, P0 response under 15 minutes, Dedicated Platform Architect, Annual commitment, contact sales |
Key Features
- Durable Workflows: Workflow state survives crashes and deploys, so a run can pause for months and resume from its exact point without recovery code.
- Built-in Failure Handling: Automatic retries with backoff, four timeout classes, heartbeating and saga compensation replace hand-written error handling.
- Seven Language SDKs: Seven supported languages let each team write workflows in the stack it already runs, with time-skipping tests for fast checks.
- Long-Running Timers and Schedules: Durable timers sleep for months and cron-style Schedules support backfill, with Continue-As-New for very long histories.
- Pay-As-You-Go Cloud: Temporal Cloud carries no monthly minimum and meters each Action, with a 99.9% SLA and 99.99% on high availability.
- Durable AI Agents: Integrations with the OpenAI Agents SDK and Google ADK run LLM and tool calls as durable Activities (listed as preview).
Pros
- Removes retry, timeout and state-persistence plumbing that backend teams otherwise rewrite for every service.
- MIT-licensed and self-hostable, so teams that want zero licence cost and full infrastructure control are not tied to the managed product.
- Cloud pricing is now public and usage-based with no base fee, so a team can start on free credits and see costs before talking to sales.
- Production use at companies including Stripe and Datadog (named on the vendor's about page) lowers adoption risk for an infrastructure dependency.
Cons
- The workflow-as-code model, with deterministic code and separate workers, takes real time to learn and slows initial onboarding.
- A production self-hosted cluster demands operational expertise, and Cloud moves that cost onto a per-Action bill that grows with chatty workflows.
- Support is a paid layer, and 24/7 response needs an Enterprise commitment.
- Overkill for simple CRUD services, single-step scripts or short jobs that never need durable state.
Data Handling
- Compliance
- SOC 2 · HIPAA
Frequently Asked Questions
How much does Temporal Cloud cost?
Temporal Cloud has no base monthly fee. Actions start at $50 per million and fall to $25 for the 100M to 200M band, storage is $0.042 per GB-hour active and $0.00105 retained, and developer support is 10% of usage. Business support costs $500 a month or 10% of usage, whichever is higher, and covers 2.5M Actions, while the two top support levels are priced by the sales team.
Is there a free version of Temporal?
Yes. You can self-host the whole product with no licence fee, since the code is MIT licensed, and pay only for your own servers. Temporal Cloud has no permanent free plan, but new accounts get $150 in credits that last 90 days, and a card is needed to sign up.
Which workflow tools compete with Temporal?
Inngest fits event-driven functions on serverless platforms, with a free plan of 50,000 executions a month before Pro at $99 a month. Trigger.dev suits TypeScript stacks, from a free plan to $50 a month on Pro, with compute billed separately. No-code builders such as n8n cover automations that need no engineering. All three skip the work of operating or learning Temporal.
When is Temporal the wrong choice?
Skip it for simple CRUD services, nightly scripts and short jobs that never need to resume after a failure. The programming model has a learning curve, a self-hosted cluster needs operations skill, and Cloud bills per Action. Teams with one language and a small workload often ship faster on a lighter queue or a serverless workflow tool.
How do I get started with Temporal?
Install the Temporal CLI, start the local development server and add the SDK for your language from the quickstarts at docs.temporal.io. Write one workflow and one activity, run a worker, and watch the execution in the web UI. When you are ready for production, sign up for Temporal Cloud and use the $150 credit to estimate your Action volume.
Top Alternatives
- Inngest: Inngest suits teams on Vercel, Cloudflare or Next.js that want event-driven functions with no cluster to run. Temporal is the heavier choice for multi-language backends that want full control, either self-hosted or on Cloud.
- Trigger.dev: Trigger.dev has a free plan and paid tiers from $10 a month for TypeScript stacks. Temporal Cloud has no base fee but bills per Action, which favours workloads that need seven language SDKs and durable execution at scale.
HokAI guides covering Temporal
- AI Development Services in 2026: Which Layer You Actually Need: AI development services means four separate infrastructure layers, not one purchase: sandboxing, prompt testing, workflow durability, and API governance.
- Trigger.dev vs Inngest: Which Should You Use in 2026?: Trigger.dev and Inngest both push free self-hosting, but their docs warn against it in production. Real 2026 pricing and the agent-pause gap that decides this.
- Inngest vs LlamaIndex: Why the Comparison Is the Wrong Question: Inngest and LlamaIndex both surface in AI agent searches, but they solve different layers of the stack: one runs step functions, the other builds RAG pipelines.