Durable Workflow Orchestration
Temporal Cloud on AWS Marketplace: how does billing work and can we use marketplace procurement?
7 min read
Most teams come to AWS Marketplace for one reason: they want Temporal Cloud on their existing AWS bill, under the same procurement and approval workflows they already use for everything else. That’s exactly what the AWS Marketplace listing is designed to do—your usage-based Temporal Cloud charges simply flow through AWS, instead of a separate vendor invoice.
Quick Answer: When you subscribe to Temporal Cloud via AWS Marketplace, you still consume Temporal the same way (usage-based actions, regions, etc.), but billing and procurement run through AWS. You can use Marketplace budgets, approvals, and committed spend programs, and pay for Temporal Cloud as part of your normal AWS invoice.
Frequently Asked Questions
How does billing work for Temporal Cloud on AWS Marketplace?
Short Answer: Temporal Cloud remains usage-based; AWS Marketplace just becomes the billing and invoicing layer. Your Temporal usage rolls up into your AWS bill instead of a separate Temporal invoice.
Expanded Explanation:
Temporal Cloud charges are based on what you actually use, not on pre-allocated infrastructure. The AWS Marketplace listing preserves that model. You subscribe to Temporal Cloud via Marketplace, connect or create your Temporal Cloud account, and from that point, your metered usage (e.g., Workflow executions, Actions, regions, data durability features) is reported back to AWS and appears as a SaaS line item on your AWS invoice.
Nothing about how you design or run Workflows changes. You still run your Workers in your own environment, Temporal still coordinates execution from the managed service, and you still get “reliable, scalable, serverless Temporal in 11+ regions.” The only difference is where the bill comes from and how it’s processed internally on your side.
Key Takeaways:
- Temporal Cloud usage is metered and billed via AWS Marketplace as a SaaS subscription.
- You get a consolidated AWS invoice instead of a standalone Temporal Cloud invoice.
How do we subscribe to Temporal Cloud through AWS Marketplace?
Short Answer: You find Temporal Cloud on AWS Marketplace, subscribe, and then link that subscription to your Temporal Cloud account. After that, all eligible usage is billed through AWS.
Expanded Explanation:
Subscribing through AWS Marketplace follows the standard SaaS flow: your procurement or cloud team approves the offer in Marketplace, your account is provisioned or mapped, and billing switches to AWS. Temporal still runs the managed service; AWS just becomes the billing intermediary.
Behind the scenes, Temporal reports metered usage to AWS Marketplace. AWS aggregates it with your other services and handles the commercial operations. If you already have a Temporal Cloud account, you typically link it to the Marketplace subscription; if you’re new, you can create one as part of the onboarding flow and still take advantage of the “Get Started for Free” model (e.g., trial credits where applicable).
Steps:
- Locate the listing: Go to AWS Marketplace and search for “Temporal Cloud” (ensure you’re in the right AWS account/organization).
- Review and subscribe: Review pricing and terms, select the appropriate contract/offer, and click “Subscribe” using your normal AWS approval path.
- Link to Temporal Cloud: Follow the post-subscription instructions to either create a Temporal Cloud account or link your existing one so usage is associated with your Marketplace subscription.
What’s the difference between buying Temporal Cloud directly vs through AWS Marketplace?
Short Answer: Functionally the service is the same; the main differences are who invoices you (Temporal vs AWS), how procurement works, and how it interacts with your AWS spend commitments.
Expanded Explanation:
With Temporal Cloud, you have two commercial paths to the same Durable Execution platform:
- Direct purchase: You sign an agreement with Temporal, pay Temporal directly, and receive invoices from Temporal. This is often preferred when you want very specific commercial terms outside Marketplace, or you’re standardizing on direct SaaS contracts.
- AWS Marketplace purchase: You subscribe via Marketplace, usage-based charges show up on your AWS bill, and you can treat Temporal as part of your AWS cloud spend. This path is ideal when your organization prefers to route everything through AWS, or wants to apply AWS Enterprise Discount Program (EDP) or internal cloud budgets to Temporal usage.
The code, SLAs, reliability characteristics, and feature set are the same. Your Workers still run in your environment, the Temporal Service still coordinates execution, and “either way, we never see your code.”
Comparison Snapshot:
- Option A: Direct with Temporal
- Invoices and contracts directly with Temporal.
- Best when you want non-Marketplace terms or separate vendor management.
- Option B: Through AWS Marketplace
- Charges appear on your AWS bill and often count toward AWS commitments.
- Best when your procurement and finance teams prefer Marketplace procurement and centralized cloud spend.
- Best for: Teams that want Temporal Cloud but must use AWS Marketplace for vendor onboarding, budget control, or EDP alignment.
How do we actually use AWS Marketplace procurement with Temporal Cloud?
Short Answer: You treat Temporal Cloud like any other SaaS in AWS Marketplace: use your normal internal approval, budget, and commitment workflows, but the service you’re buying is Temporal Cloud.
Expanded Explanation:
Marketplace is a procurement layer on top of Temporal Cloud. Your existing processes (legal review, vendor risk checks, budget approvals) can attach to the Marketplace subscription instead of a new vendor onboarding process. Many enterprises already have well-defined guardrails in place for Marketplace, so adding Temporal Cloud inside those rails is far easier than adding a net-new vendor.
Temporal Cloud’s economics align well with how teams already think about cloud spend. Instead of paying for over-provisioned hardware or giant database instances just in case a long-running Workflow fails, you pay for durable execution actions that you actually use. Marketplace lets you fund that consumption out of your AWS budget, governed by the same policies your cloud team uses for other critical infrastructure.
What You Need:
- AWS Marketplace access: An AWS account with permission to subscribe to third-party SaaS via Marketplace (often managed by a central cloud or procurement team).
- Internal approval path: Your organization’s standard process for approving new Marketplace subscriptions and associating them with the right cost centers and budgets.
How does using AWS Marketplace for Temporal Cloud help our overall cloud strategy?
Short Answer: Routing Temporal Cloud through AWS Marketplace lets you consolidate spend, simplify vendor management, and align Temporal usage with your AWS growth and commitments.
Expanded Explanation:
Temporal exists to remove failure-driven toil from your architecture: stop building ad-hoc state machines, stop writing custom retries, stop debugging orphaned processes in logs. But the business side also cares about where the money goes and how predictable that spend is.
By using AWS Marketplace:
- You can often count Temporal Cloud spend toward AWS Enterprise Discount Program (EDP) or similar commitments, making Temporal part of your broader cloud efficiency and negotiation strategy.
- Finance gets one consolidated cloud bill instead of another vendor to track.
- Procurement and security teams reuse existing Marketplace vetting, rather than running a full new-vendor process.
- Engineering gets a Durable Execution platform that scales with usage, instead of provisioning over-sized infrastructure to handle worst-case workflows that run for days, weeks, or months.
The net effect: you get invincible-feeling applications—Workflows that automatically recover, replay, and resume after crashes or outages—while keeping cloud governance sane. You stop fighting failures and stop fighting procurement at the same time.
Why It Matters:
- Operational impact: Temporal cuts manual recovery, reduces lost progress, and shortens incident resolution by giving you full visibility and replay of every Workflow execution.
- Financial impact: AWS Marketplace lets you align that technical reliability with the way your organization already plans, approves, and optimizes cloud spend.
Quick Recap
Subscribing to Temporal Cloud via AWS Marketplace doesn’t change what the platform does—it still gives you Durable Execution, automatic recovery, and full Workflow visibility. It changes how you buy and account for it. Usage-based Temporal Cloud charges flow through AWS, can integrate with your Marketplace procurement workflows and AWS commitments, and show up on your consolidated cloud bill. Either way—direct or via Marketplace—your Workers run in your environment, the Temporal Service coordinates execution, and we never see your code.