Temporal Cloud review

Temporal Cloud is the hosted version of the Temporal Service: a durable workflow orchestration service that sits behind application code. Developers write business logic as Workflows and failure-prone operations as Activities using Temporal's native SDKs. The service persists workflow state and provides task queues, signals, timers, retries, and execution visibility. When an Activity or a connected service fails, the workflow can recover, replay, or pause rather than losing its recorded progress.

That makes Temporal a control plane for long-running application processes, not a general-purpose database or a drop-in job queue. It is aimed at flows such as order processing, financial transactions, infrastructure deployment, and AI pipelines, where steps may span services or run for days or longer. Teams can use Temporal Cloud or host the open-source Temporal Service themselves. Cloud removes the need to operate that service, while application code still needs to be structured around Temporal Workflows and Activities.

The core integration surface is Temporal's native SDKs: business logic is written as Workflows, with failure-prone functions modeled as Activities. The homepage says teams can use programming languages they already use, but does not name the languages. Before adopting it, confirm that Temporal provides an SDK for your language and check the vendor docs for the client and service interaction details your deployment needs.

The programming model includes workflow state persistence, automatic Activity retries, task queues, signals, and timers. Temporal also provides visibility into the state of workflow executions. These features shape how application code handles retries and long-running work; they are not just settings on an external scheduler. The homepage links to documentation, a demo, and a Code Exchange, but does not identify a CLI, REST API, or specific third-party integrations. Teams should verify current SDK versions, supported language features, and operational guidance in the Temporal docs before committing to a stack.

Temporal Cloud has no free plan. The listed Pay-As-You-Go rate is $50 per million actions, with no monthly base fee, plus $0.042/GBhr for active storage and $0.00105/GBhr for retained storage. New customers can get $150 in credits for 90 days. The open-source project is a separate self-hosting option, not a free Cloud tier.

For higher volume, self-service Volume Discounts go down to $25 per million actions; larger discounts are available via a commit. Business Support costs the greater of $500 per month or 10% of usage and includes 2.5M actions, 2.5 GB active storage, 100 GB retained storage, and a 2-hour P0 SLA during business hours. Enterprise and Mission Critical pricing is custom; its listed package includes 10M actions, 10 GB active storage, and 400 GB retained storage. Storage is billed by usage, and support or SCIM can add cost. Annual billing is not listed.

Temporal says its open-source project is MIT-licensed and can be hosted in your own environment. Temporal Cloud is the managed hosting path for the Temporal Service; the vendor says it does not see your code. Self-hosting avoids the Cloud service bill, but your team takes on the infrastructure and operations required to run the service.

Using the open-source project gives you an alternative to remaining on Temporal Cloud, though moving a production deployment will involve operating a Temporal Service and validating your workflows and SDK setup there. Temporal's homepage does not describe data export formats or a migration process. Ask the vendor what workflow history and execution data can be exported, how long it is retained, and what is required to move an existing Cloud deployment. The MIT license applies to the open-source project; it does not remove the need to plan a migration.

The production case is durable state and automatic retries for workflows that span unreliable services or run for long periods. Before depending on it, confirm how action usage is metered for your workloads, how active and retained storage will grow, and what throughput or rate limits apply. The listed plans describe action and storage allowances, but production teams should ask Temporal about limits and behavior beyond those allowances. Also verify the security, compliance, retention, and recovery requirements for your workload with the vendor.

A Temporal community Reddit post describes keeping encryption keys with the customer while Temporal sees ciphertext, outbound-only workers, access controls, and private connectivity options including AWS PrivateLink and GCP PSC. Treat those as vendor-posted claims to validate against current documentation and your plan. A separate Reddit thread asks whether Temporal Cloud is suitable for privacy and security; it does not provide user reports or a recommendation. The available Reddit discussion is too limited to establish broad customer sentiment.