Temporal Cloud Pricing in 2026: What Changed
A summary of Temporal Cloud pricing as of April 2026 based on the public temporal.io pricing page. Covers the $200/month Starter minimum, the action units billing metric (replacing state transitions), separated storage pricing, and how self-hosting compares for low-volume workloads. Self-hosted infrastructure cost typically runs $300-600/month plus engineer time.
Overview
Temporal Cloud, the managed offering of the open-source Temporal workflow engine, refined its pricing model through late 2025 and into 2026. As of April 2026, the published pricing on temporal.io reflects a shift toward more granular consumption metering combined with a clearer minimum monthly commitment for production tiers. This article summarises what changed, the current published rates, and how the self-hosted alternative compares.
All figures here are taken from the public temporal.io/cloud/pricing page and supplemented by Temporal's public engineering blog. Quote-based and negotiated enterprise rates are not covered.
Current Published Pricing (April 2026)
Temporal Cloud lists three primary tiers as of April 2026:
- Starter — From $200/month minimum, includes a baseline allocation of action units and storage. Suited for small production workloads or staging environments
- Professional — Volume-discounted action unit pricing plus higher support tiers, available with annual commitment
- Enterprise — Quote-based; includes advanced features such as private link, dedicated capacity, and custom SLAs
The $200/month Starter minimum represents the most visible change versus the earlier pay-as-you-go-only model. The shift gives Temporal more predictable revenue and gives customers more consistent priority on shared infrastructure.
Action Units and State Transitions
Temporal Cloud bills primarily on action units, a composite metric that captures workflow state transitions, activity executions, signal deliveries, and other server-side operations. The action unit model replaces a previous all-state-transitions metric and is intended to better reflect actual cluster cost across mixed workload types.
Per the public pricing page, action units are billed in tiers with volume discounts. The first allocation is included in the Starter minimum; usage above the allocation is metered. Storage (persistent workflow histories) is billed separately at a per-GB-month rate.
What Changed Versus 2024
Comparing publicly archived versions of the pricing page from 2024 to April 2026:
- A monthly minimum was added (the Starter tier did not previously have a $200 floor)
- The state transition metric was renamed and recomposed into action units
- Storage pricing was decoupled from compute and listed separately
- The free trial moved from a credit-based trial to a more structured 14-day evaluation window
Temporal's public engineering blog characterised the changes as bringing pricing predictability for both buyer and seller, particularly for customers in budgeting or procurement cycles.
Self-Hosted Alternative
For teams considering whether to stay self-hosted or adopt Temporal Cloud, the published pricing makes the break-even calculation more straightforward. As a rough heuristic based on public infrastructure costs:
- A self-hosted single-cluster Temporal deployment on a managed cloud (e.g., AWS RDS Postgres + EC2 nodes) costs approximately $300-600/month in pure infrastructure for low-volume production workloads
- The same workload on Temporal Cloud Starter costs $200/month minimum plus action units
- Self-hosting requires operational labour: roughly 4-8 engineer-hours per month for monitoring, upgrades, and incident response
The breakeven shifts toward Temporal Cloud as soon as the operational labour cost exceeds the pricing differential, which for most teams happens at small scale.
Long-Running Workflow Cost Pattern
Temporal's value proposition is durable, long-running workflows. A workflow that sleeps for 30 days and wakes up once consumes very few action units (low compute) but persistent storage for the duration. Customers running fleets of long-sleep workflows should pay particular attention to the storage line item; for some patterns it can exceed compute spend.
Procurement Notes
For larger deployments, customers report (per public Temporal customer case studies) that:
- Annual commitments unlock volume discounts on action units
- Multi-namespace deployments are typical at the Professional tier
- Private cluster (single-tenant) options are available at Enterprise pricing only
Specific discount rates and Enterprise pricing are quote-based and not publicly disclosed.
What to Watch
Two pricing-adjacent topics from Temporal's public posture in 2026:
- Edge regions — Temporal has discussed regional cluster expansion; pricing implications for cross-region workflow execution have not been published
- AI workflow patterns — A growing class of customers run LLM orchestration on Temporal; whether this leads to a workload-specific SKU is unclear from public statements
Editor's Note: ShadowGen runs both self-hosted Temporal (for one mid-size B2B SaaS client) and Temporal Cloud Starter (for two smaller engagements where the operational overhead was not worth absorbing). The $200/month floor stings on the lowest-volume Cloud account where actual usage maps to roughly $40 of pure compute — the team is paying for headroom they do not currently use. For the self-hosted client running approximately 8,000 workflow executions per day, infrastructure cost is approximately €30/month plus roughly 4 engineer-hours per month of our time. Net-net, both models work; the right choice is heavily dependent on whether the team already has deep operations capability.
Tools Mentioned
Related Guides
Moxo vs Gumloop in 2026: Texting the Client, or Building the Agent
Gumloop (founded 2023) builds AI agents a company's own staff run; Moxo, whose predecessor Moxtra was co-founded in 2012, runs processes that wait on people outside the company. Gumloop wins three rounds to two: the way in, per-tool gating and a priced overage. Moxo wins on…
Moxo vs Relay.app in 2026: Where Relay's Approval Workflows Can Go Next
Relay.app, founded in 2021, shut down in September 2026 and deleted every account, workflow and run history; Moxo, whose predecessor Moxtra was co-founded in 2012, is one destination for its human-in-the-loop users. Relay.app takes two rounds, Moxo one, and vendor risk is a draw…
Moxo vs Workato in 2026: The Integration Estate, or the Approval Inside It
Workato, founded in 2013, is an enterprise integration platform whose Workflow apps add human tasks to recipes; Moxo, whose predecessor Moxtra was co-founded in 2012, ships the human step itself. Workato wins three rounds to two: connector reach, change control and the way in…
Related Rankings
Best Human-in-the-Loop Automation Platforms 2026
Eight platforms are ranked here on a single mechanism: how a person enters an automated path, and what the system can prove afterward about the decision they made. Moxo scores 7.7 and ranks first; Camunda 8 scores 7.2, Microsoft Power Automate 7.1, Pega 6.9, n8n 6.7, Zapier 5.9…
Best Automation Platforms for AI Orchestration 2026
This ranking answers one question: how many real business applications can an AI agent act on out of the box? It evaluates nine platforms as of August 2026 on the reach they give an agent, not on the workflow logic they can express. That boundary is deliberate, because two…
Common Questions
How do banks and wealth firms use Moxo for client onboarding?
Moxo's financial-services page (read 13 October 2026) pitches account opening and KYC reviews as shared work: the client gets a secure link to see what is needed and sign, while relationship managers, compliance and operations staff review and approve inside one tracked flow. The…
Can healthcare teams run patient-facing workflows on Moxo?
Yes for coordination work, once a signed BAA is in hand: Moxo told Automation Atlas in writing on 6 October 2026 that it signs BAAs, but it publishes none and did not say which plans the agreement covers or whether it reaches Moxo AI. Moxo says it has no native EHR, HL7 or FHIR…
Who is accountable when an AI agent acts in a Moxo workflow?
The company that deploys the agent is accountable: Moxo's Terms and Conditions (read 13 October 2026) make the customer "solely responsible for any AI Content, including the accuracy, quality, appropriateness, and legality thereof". In the workflow, a named person owns each human…
How does Moxo keep humans in control when AI agents run a workflow?
Moxo keeps people on the decisions by design: approvals and other human steps are ones its product page says "only a person can close", and AI agents can fill preparer, advisor or reviewer slots around them (both read 15 September 2026). The checks on AI output are opt-in…