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
Activepieces
No-code workflow automation with self-hosting and AI-powered features
Workflow AutomationAutomatisch
Open-source Zapier alternative
Workflow AutomationBardeen
AI-powered browser automation via Chrome extension
Workflow AutomationCalendly
Scheduling automation platform for booking meetings without email back-and-forth, with CRM integrations and routing forms for lead qualification.
Workflow AutomationRelated Guides
Migrating 23 Make Scenarios to Self-Hosted n8n: a 3-Week Breakdown
Anonymized retrospective of a DTC ecommerce brand migrating 23 Make scenarios to a self-hosted n8n instance over three weeks. Tooling cost dropped from $348/month on Make Teams to roughly $12/month on a Hetzner VPS, but credential and webhook recreation consumed about 40% of total project time.
Trigger.dev vs Inngest 2026: OSS Durable Runners Compared
Trigger.dev (2022, London) is a fully Apache 2.0 durable runner with task-based authoring, machine-size selection, and first-class self-host. Inngest (2021, San Francisco) is a developer-first event-driven step platform with an open-source dev server and a managed cloud (50K step runs/month free, $20/month Hobby). This 2026 comparison covers license, programming model, pricing, observability, and self-host options.
Inngest vs Temporal 2026: Durable Functions vs Durable Workflows
Inngest (2021, San Francisco) is a developer-first durable functions platform with TypeScript and Python SDKs, 50,000 step runs/month free, and Hobby pricing from $20/month. Temporal (2019) is the heavyweight durable workflow engine with seven-language SDK coverage, Cassandra-backed scale, and Cloud pricing from roughly $200/month at low volume or $2.5-4.5K/month self-host. This 2026 comparison covers programming model, pricing, scale ceiling, and operational footprint.
Related Rankings
Best Durable Workflow Engines for Production in 2026
A ranked list of the best durable workflow engines for production deployments in 2026. Durable workflow engines persist execution state to a database so that long-running workflows survive process restarts, deployments, and infrastructure failures. The ranking covers Temporal, Prefect, Apache Airflow, Camunda, Windmill, and n8n. Tools were evaluated on production reliability, developer experience, scalability, open-source health, and documentation quality. The shortlist intentionally mixes code-first engines (Temporal, Prefect, Airflow) with hybrid visual platforms (Camunda, Windmill, n8n) to reflect how production teams actually choose workflow engines in 2026.
Best No-Code Automation Platforms in 2026
A ranked list of no-code automation platforms in 2026. The ranking covers visual workflow builders that allow non-engineering teams to connect SaaS apps, route data, and add conditional logic without writing code. Entries cover proprietary cloud platforms (Zapier, Make, Pipedream, IFTTT) and open-source visual builders (n8n, Activepieces). Scoring reflects integration breadth, pricing accessibility, visual editor ease, reliability and error handling, and self-hosting availability.
Common Questions
What are the best automation tools for solo founders in 2026?
Solo founders in 2026 get the most value from Zapier or Make (broad SaaS glue), n8n self-hosted (free, unlimited runs), Pipedream (generous free tier with code steps), Notion automations, and Lindy or Relay.app (AI agents for inbox and meetings). Free tiers cover most pre-revenue workflows.
What are the best automation tools for finance and AP teams in 2026?
Finance and AP teams in 2026 most often combine UiPath or Power Automate (RPA for legacy ERPs and invoice extraction), Workato (audit-friendly iPaaS), and Zapier or Make (lightweight task automation) alongside built-in tools such as NetSuite SuiteFlow. Selection depends on ERP, audit requirements, and invoice volume.
What are the best AI-native automation tools in 2026?
The leading AI-native automation tools in 2026 are Lindy and Relevance AI (agent builders), Gumloop (visual agent workflows), Relay.app (human-in-the-loop AI workflows), Bardeen (browser AI agents), and CrewAI (multi-agent code framework). "AI-native" here means the LLM is the orchestrator, not a step inside a traditional workflow.
What are the best workflow automation tools for technical writers in 2026?
Technical writers in 2026 typically combine Mintlify or ReadMe (docs-as-code platforms), n8n or Zapier (publishing automation), GitHub Actions (CI for docs), and Notion or Coda (drafting and review). The strongest setups treat docs as code with an automation layer for screenshots, link checks, and changelog publishing.