Pricing - Temporal Cloud
Temporal Cloud is a consumption-based service; you pay only for what you need when you need it. Our pricing derives from your use of actions, storage, and support. Pricing is flexible, transparent, and predictable, so you know your costs and never pay for unused capacity.
This page introduces the elements of Temporal Cloud pricing—actions, storage, and support—so that you can estimate costs for your implementation. To gain a reliable estimate, contact our team.
What is an Action?
Actions are the fundamental consumption pricing unit in Temporal Cloud. An Action in Temporal occurs as part of an execution of your Workflow. Each time you execute a Temporal Workflow (a Workflow Execution), the associated Actions are collected and ultimately represent the state and progress of your Temporal Application.
Actions are collected and billed monthly for each Namespace. The base rate is $25 per one million Actions per month (across all Namespaces), and you are billed only for the prorated amount of Actions you use. If you use fewer than one million Actions per month, your bill for Actions will be less than $25 for that month.
| Actions per month | Cost per 1M (USD) |
|---|---|
| Any number | $25.00 (prorated) |
Alternatively, Temporal also offers a credit system. Credits provide an additional discount schedule for both billable Actions and storage. Credits do not expire. The following table outlines cost estimates for the credits system. Please reach out to the team if you are interested in this option.
| Actions (Per Million Actions per Namespace) | Cost (USD) |
|---|---|
| Up to 300M | $23.25 |
| Over 300M up to 1.5B | $18.80 |
| Over 1.5B up to 7.5B | $14.10 |
| Over 7.5B up to 30B | $10.50 |
| Over 30B up to 150B | $7.90 |
| Over 150B | $5.90 |
The following operations result in Actions:
Workflows
- Workflow started. Occurs via client start, client Signal-With-Start, Continue-As-New, or Child Workflow start. If a Workflow start fails, an Action is not recorded.
- Workflow reset. Occurs when a Workflow is reset. (Actions that occur before a Reset are counted even if they are no longer visible in Event History.)
- Timer started.
Includes implicit Timers that are started by a Temporal SDK when timeouts are set, such as
AwaitWithTimeoutin Go orconditionin TypeScript. - Search Attribute upsert requested.
Occurs after a Workflow starts and invokes
UpsertSearchAttributes. - Signal sent. Includes sending a Signal from a client or from within a Workflow to another Workflow.
- Query received. Queries aren't recorded in Event History. An operation such as viewing the call stack in the Temporal Cloud UI results in a Query.
- Side Effect recorded. For a mutable Side Effect, an Action occurs only when the value changes. (Be aware that some SDKs don't support Side Effects.)
- NEW: Workflow Update. [Workflow Updates] is a primitive that combines a Signal and Query together for a single Action.
Child Workflows
- The parent Workflow spawning a Child Workflow results in one Action.
- Execution of the Child Workflow results in one Action.
Activities
- Activity started or retried. Occurs each time an Activity is started or retried.
- Local Activity started. Each Local Activity associated with one Workflow Task will count as one Action. (Note: Each additional Workflow Task heartbeat after counts as an additional Action. Also, Local Activities retried following a Workflow Task heartbeat will count as one Action.
- Activity Heartbeat recorded. A Heartbeat call from Activity code counts as an Action only if it reaches the Temporal Server. Temporal SDKs throttle Activity Heartbeats. The default throttle is 80% of the Heartbeat Timeout. Heartbeats don't apply to Local Activities.
Schedules
Schedules allows you to "schedule" a Workflow to start at a particular time. Each execution of a Schedule will accrue three actions:
- Schedule Start. Will account for two actions
- Workflow started. One action to start the target workflow
Export
Workflow History Export allows you to export closed Workflow Histories to a cloud storage sink of your choice.
- Workflow exported. Each Workflow exported accrues a single action.
Reach out to our team to get more information or to help size your number of Actions.
What are the Temporal Cloud storage prices?
An execution of a particular Workflow could exist for a few seconds, a day, month, or even forever. Temporal collects the Event History during this time and dispatches work when necessary. In this context, a Workflow Execution has only two states, open (active) or closed.
Storage costs are measured in gigabyte-hours (GBh) and include charges for active Workflows, active storage, and the long-term, "retained" storage of Event Histories of closed Workflows. These are measured per Namespace.
Active storage is a measure of the amount of storage used to store active Workflows.
When the execution of a Workflow ends, Temporal Cloud stores Event History for a defined Retention Period, for historical use. This is retained storage. Typical uses include compliance, debugging, workload refresh, and business analytics. Both kinds of storage have fixed costs.
| Storage | Cost per GBh (USD) |
|---|---|
| Retained | $0.00042 |
| Active | $0.042 |
If you purchase Temporal Cloud credits (as outlined earlier), active storage costs are tiered and measured in gigabyte-hours.
| Active Storage (Per GB Hour Per Namespace) | Cost (USD) |
|---|---|
| Up to 7,000 | $0.039 |
| Over 7,000 up to 30,000 | $0.031 |
| Over 30,000 up to 90,000 | $0.023 |
| Over 90,000 up to 400,000 | $0.018 |
| Over 400,000 up to 1,500,000 | $0.013 |
| Over 1,500,000 | $0.010 |
What kind of support do I get with Temporal Cloud?
When signing up for Temporal Cloud, select a support plan—either Basic or Premium—and gain access to our support organization, which includes developer success engineers and solution architects. Our experts assist with a range of work streams, from Workflow design reviews to setting up observability, and from troubleshooting support to maintaining an agreed-upon set of SLAs.
The Temporal Developer Success team brings a deep knowledge of how Temporal works and how you can optimize your deployment. This team is comprised of engineers who know Temporal inside and out, and continue to contribute to its development.
They also investigate your Workflows to optimize their environments and possibly reduce costs associated with Actions and storage. They ensure your instance is performance tuned and help with other ongoing maintenance, like upgrades of the Temporal software and maintenance of the platform.
If an issue occurs, the team provides support through our support portal, community forum, and (with Premium support) a dedicated Slack channel. Temporal offers two levels of support defined by their availability and SLAs.
| Basic | Premium | |
|---|---|---|
| Response times | P0: 1 business hour P1: 4 business hours P2: 1 business day P3: 2 business days | P0: 30 minutes P1: 1 business hour P2: 4 business hours P3: 1 business day |
| Pricing (per month) | Greater of $200 or 10% of monthly usage | Greater of $2,000 or 10% of monthly usage |
Business Hours: 05:00-17:00 Mon-Fri US Pacific Time. For P0 issues, coverage is 24×7.
Priority definitions
- P0 - Critical (Production impacted)
- The Temporal Cloud service is unavailable or degraded with a significant impact.
- P1 - High (Production issue)
- An issue related to production workloads running on the Temporal Cloud service, or a significant project is blocked.
- P2 - Normal (General issues)
- General Temporal Cloud service or other issues where there is no production impact, or a workaround exists to mitigate the impact.
- P3 - Low (General guidance)
- Questions or an issue with the Temporal Cloud service that is not impacting system availability or functionality.
What is the price for SSO and SAML?
We offer single sign-on (SSO) integration using SAML at a monthly fixed fee based on the number of users registered in Temporal Cloud:
| Users | Cost per month |
|---|---|
| 0 to 25 | $200 |
| 26 to 50 | $300 |
| 51+ | $500 |
How to estimate costs
Temporal Cloud employs a consumption-based pricing model that's based on storage and execution, factors that vary from one Workflow to the next. You can estimate the cost of a specific Workflow by running it at a low volume and then using its storage and compute measurements to project your production-scale cost. Our team is happy to help you estimate the cost for your specific workloads.
Pricing FAQ
What’s the minimum cost to run Temporal Cloud?
The Temporal Cloud service is consumption based. You pay only for what you need with no minimum. Basic support has a minimum monthly fee of $200 per month.
How do I pay for Temporal Cloud?
Temporal sends a monthly bill based on your consumption. You can pay this bill with a credit card, ACH, wire transfer, or Temporal Credits.
Can I purchase Temporal Cloud through my Amazon, Azure, or Google Cloud Platform marketplace?
You can purchase Temporal Cloud credits in the AWS Marketplace. To learn more about our private offer on the AWS Marketplace, contact our team at sales@temporal.io.
Do you offer any discounts for startups?
Yes. If you're part of a startup that has raised $30 million or less in funding and is not a current Temporal Cloud customer, you can apply for free Temporal Cloud credits. To learn more and apply, see Temporal Cloud for Startups.