Temporal Cloud review

Temporal Cloud is a hosted service for running durable workflows: application processes that save their state and can resume after failures. Instead of relying on a chain of fragile calls to finish a long-running task, developers define workflow logic and activities; Temporal manages execution and recovery. The feature list includes automatic retries when APIs fail or networks time out, plus task queues, signals, and timers for coordinating work.

The service also provides visibility into the exact state of workflow executions. Developers can write business logic using Temporal’s native SDKs in programming languages they already use. Teams that do not want the hosted service can host the open-source Temporal Service themselves.

The practical distinction is ownership: Temporal Cloud hosts the service, while your team builds the workflows and activities. It is developer infrastructure, not a visual marketing automation tool. Pricing is usage-based, with published rates per million actions and separate active and retained storage charges.

The main strength is failure recovery built into workflow execution. According to the feature list, Temporal persists workflow state so executions can recover, replay, or pause. Activities retry when an API fails or a network times out. That gives teams a way to coordinate work that may take time or encounter transient errors without treating every interruption as a reason to start over.

The controls are useful for workflows that need more than a simple sequence of steps. Task queues, signals, and timers let teams coordinate execution, and the service shows the state of individual workflow executions. Native SDKs let developers express business logic in programming languages they already use, rather than requiring a separate workflow language, according to the product description.

There is also a meaningful hosting choice. Teams can use Temporal Cloud or host the open-source Temporal Service themselves. Cloud pricing lists a Pay-As-You-Go option with no base monthly fee, while higher-volume teams can access self-service rates down to $25 per million actions. A 90-day trial with $150 in credits is listed, alongside a free plan; the published pricing details do not specify what the free plan includes.

The bill is not just a monthly subscription. The pricing page lists Pay-As-You-Go at $50 per million actions, plus $0.042 per GB-hour of active storage and $0.00105 per GB-hour of retained storage. The plan has no base monthly fee, but usage is billed as incurred. Volume discounts can bring the self-service action rate down to $25 per million; larger discounts require a commitment. The pricing details do not define an action, so estimate your workload before treating the per-million rate as a budget.

Support adds another cost tier. Business Support is listed at $500 per month or 10% of usage, whichever is greater, and includes 2.5 million actions, 2.5 GB of active storage, 100 GB of retained storage, and a two-hour P0 SLA during business hours. Enterprise and Mission Critical pricing is custom. Their listed allocations are 10 million actions, 10 GB active storage, and 400 GB retained storage; Enterprise has a 30-minute P0 SLA 24/7, while Mission Critical lists 15 minutes and a dedicated platform architect. Developer support costs 10% of usage; SCIM is an add-on with no published price. No annual billing is listed.

Temporal Cloud lists a free plan and a 90-day trial with $150 in credits, but the free plan’s limits are not published on the vendor's site. Pay-As-You-Go is billed as incurred, with no base monthly fee, at $50 per million actions. Volume Discounts list self-service rates down to $25 per million actions; larger discounts require a commitment. That is half the Pay-As-You-Go action rate, but it is not a $25 monthly subscription.

Storage is extra: $0.042/GB-hour for active storage and $0.00105/GB-hour for retained storage. Business Support costs $500 per month or 10% of usage, whichever is greater, and includes 2.5 million actions plus stated storage allowances. Enterprise and Mission Critical are custom-priced, so the jump to those plans is not public. Developer support costs 10% of usage; SCIM is an add-on with no listed price. No annual billing is listed.

Moving to Temporal Cloud is not just changing a billing account if your application depends on Temporal’s workflow model: teams write business logic with native SDKs, and workflows persist state and can resume after failures. The published materials do not publish a migration guide, import/export tooling, or a supported way to move running executions, so treat workflow-state portability as an open question. Teams can host the open-source Temporal Service themselves, but that does not establish that Cloud data or in-flight executions can be exported intact.

The likely switching cost is engineering work to adapt or operate the service and validate workflows, rather than replacing a no-code automation recipe. That is an assessment based on the product model, not a published migration estimate. We were not given Reddit posts to substantiate why users leave, so we can’t attribute churn reasons to Reddit. Before committing, ask Temporal about export formats, retention, and migration of execution history—particularly if storage needs are hard to predict.