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
How to Deploy Temporal Self-Hosted on a Single Server in 2026
A step-by-step tutorial for self-hosting the open-source Temporal Server on a single Linux server using Docker Compose. Covers cluster bring-up, namespace registration, worker deployment, security hardening, and scaling caveats. Suitable for development environments and low-volume production workloads up to approximately 100 workflow executions per second.
How to Set Up Claude Code with VS Code in 2026
A step-by-step tutorial for installing Claude Code, the official Anthropic CLI, and wiring it into Visual Studio Code via the Claude Code extension. Covers npm install, authentication, extension configuration, per-project permissions, and the most common errors encountered during setup.
How to Self-Host n8n with PostgreSQL in 2026
A step-by-step tutorial for self-hosting n8n with PostgreSQL on a single Linux server using Docker Compose. Covers .env configuration, encryption keys, TLS via Caddy, persistence and backup strategy, queue mode for higher throughput, and the most common operational errors encountered during deployment.
Related Rankings
Best Open-Source Workflow Engines for Engineers in 2026
A ranked list of the best open-source workflow engines for engineers in 2026. This ranking evaluates code-first workflow orchestration platforms that engineers can self-host, extend, and embed inside existing software stacks. The ranking differs from the broader Best Open-Source Automation 2026 list by focusing specifically on workflow engines intended for developers: platforms that prioritize SDK coverage, durable execution, scalability, and operational controls over visual SaaS-connector automation. It includes durable execution engines (Temporal), data and task orchestrators (Apache Airflow, Prefect), low-code workflow builders with strong self-host stories (n8n, Windmill, Activepieces), and historical agent-based tools (Huginn).
Best Automation Tools for Healthcare in 2026
A ranked list of the best automation tools for healthcare organisations in 2026. This ranking evaluates platforms across HIPAA readiness, audit logging, PHI handling, on-premise or private-cloud deployment options, and integration with clinical and administrative systems. The ranking includes enterprise RPA (UiPath, Automation Anywhere), Microsoft-native automation (Power Automate), general-purpose workflow automation (Zapier on Business tier, Make, n8n self-hosted), and enterprise iPaaS (Boomi). Each entry is evaluated against the specific compliance, data-residency, and clinical-integration requirements that distinguish healthcare from other industries.
Common Questions
What is a Story in Tines?
A Story in Tines is a single automation workflow built as a directed graph of Actions. Stories are the Tines equivalent of a Zap in Zapier or a Playbook in traditional SOAR products, composed of six Action types: HTTP Request, Send Email, IMAP, Trigger, Event Transform, and Webhook.
Tines vs Splunk SOAR: Which security automation platform in 2026?
Tines is a no-code, SIEM-agnostic SaaS SOAR platform starting around $35,000/year; Splunk SOAR (now Cisco-owned after 2024) is a Python-based SOAR with 350+ prebuilt apps and deeper Splunk SIEM integration, typically priced higher. The choice depends on SIEM commitment and authoring preference.
Can you use Tines for SOAR automation?
Yes. Tines is a no-code security automation platform built for SOAR use cases, with production deployments at Canva, McKesson, and Databricks as of April 2026. Security teams use Tines Stories to automate phishing triage, SIEM alert enrichment, IOC lookups, and endpoint isolation.
What does Temporal cost when self-hosted?
Self-hosted Temporal is free under the MIT license; the only cost is the infrastructure to run Temporal Server, its persistence layer (Cassandra or PostgreSQL), and optional Elasticsearch for advanced visibility. A small production deployment typically costs $400-$900/month on AWS or GCP as of April 2026.