Durable Workflow Orchestration
Temporal Cloud on AWS Marketplace: how does billing work and can we use marketplace procurement?
6 min read
Quick Answer: Yes. You can buy Temporal Cloud through AWS Marketplace, have all usage billed on your AWS invoice, and leverage your existing AWS procurement, PO, and committed spend programs—while still paying only for what you use.
Frequently Asked Questions
How does billing work for Temporal Cloud on AWS Marketplace?
Short Answer: Temporal Cloud usage is metered and billed by AWS Marketplace, then appears on your standard AWS bill, just like other Marketplace SaaS products.
Expanded Explanation:
When you subscribe to Temporal Cloud via AWS Marketplace, AWS becomes the billing channel. Temporal records your usage (for example, Workflow executions and related actions) and reports that usage to AWS Marketplace. AWS then aggregates those charges with the rest of your AWS services, so your finance team sees a single AWS invoice instead of a separate Temporal invoice.
You still get the same managed Temporal Service—“Reliable, scalable, serverless Temporal in 11+ regions”—but procurement, payment, and invoice flow are handled by AWS. This lets you align Temporal Cloud spend with AWS budgets, cost centers, and committed spend agreements, without changing how your developers use Temporal.
Key Takeaways:
- Temporal Cloud usage is metered and billed through AWS Marketplace as a SaaS subscription.
- All charges show up on your existing AWS invoice, consolidating payments under your AWS account.
How do we purchase Temporal Cloud through AWS Marketplace and enable marketplace procurement?
Short Answer: Subscribe to Temporal Cloud directly from its AWS Marketplace listing, complete the SaaS configuration, and link it to your Temporal Cloud account—your procurement then runs entirely through AWS.
Expanded Explanation:
The process is similar to other Marketplace SaaS products. Your organization’s AWS administrator (with Marketplace permissions) finds the Temporal Cloud listing in AWS Marketplace, reviews pricing terms, and clicks to subscribe. AWS will guide you through a brief configuration step to connect the Marketplace subscription to your Temporal Cloud tenant or to a new Temporal Cloud signup.
Once that connection is established, all future Temporal Cloud usage is billed via AWS Marketplace. You can then use your normal marketplace procurement workflows—POs, internal approvals, and budget controls—without negotiating a new standalone vendor onboarding path.
Steps:
- Log into AWS with an account that has AWS Marketplace purchasing permissions.
- Find the Temporal Cloud listing in AWS Marketplace, review terms, and click “Subscribe” or “Continue to Subscribe.”
- Complete the SaaS configuration to link the subscription to your Temporal Cloud organization or new account, then start using Temporal Cloud as usual.
What’s the difference between buying Temporal Cloud directly vs. via AWS Marketplace?
Short Answer: Direct purchase means Temporal bills you; Marketplace purchase means AWS bills you—but the Temporal Cloud product, reliability, and Durable Execution capabilities are the same.
Expanded Explanation:
Without AWS Marketplace, you contract and pay Temporal directly. You receive invoices from Temporal and your vendor onboarding, security review, and approvals run through your standard new-vendor process.
With AWS Marketplace, Temporal Cloud becomes a line item on your AWS bill. AWS handles invoicing and payment collection; Temporal continues to operate the managed service. Your engineering experience—SDKs, Workflows, Activities, retries, timers, Web UI, and regions—remains unchanged. The main differences are who invoices you and how spend flows through your internal procurement and budgeting process.
Comparison Snapshot:
- Option A: Direct from Temporal:
Separate agreement and invoicing with Temporal; useful if you prefer direct vendor relationships or non-AWS payment flows. - Option B: Via AWS Marketplace:
Temporal Cloud usage is consolidated on your AWS invoice and can count toward AWS committed spend (per your AWS agreement). - Best for:
Teams that want to leverage existing AWS procurement, committed spend, and single-vendor billing, while giving developers the same Temporal Cloud experience.
How do we actually implement Temporal Cloud once we’ve subscribed through AWS Marketplace?
Short Answer: After subscribing, you create or connect a Temporal Cloud account, configure Namespaces and Workers, and point your applications to the Temporal Cloud endpoint—AWS Marketplace only changes the billing path, not how you integrate.
Expanded Explanation:
Marketplace procurement is just the entry point. Implementing Temporal Cloud still follows the same pattern: you define Workflows and Activities in code, deploy Workers in your environment, and let the Temporal Service in the cloud coordinate execution. Either way, Temporal never runs your code; your Workers stay in your own infrastructure and talk outbound to Temporal Cloud over secure connections.
Timeline and effort depend on how much orchestration logic you’re replacing. Many teams start by migrating a single critical flow—like order fulfillment, money movement, CI/CD rollbacks, or an AI training pipeline—then expand as they see the benefits of durable execution, automatic retries, and full visibility via the Temporal Web UI.
What You Need:
- An active Temporal Cloud account linked to your AWS Marketplace subscription and configured Namespaces.
- Application code with Temporal SDKs (Go, Java, TypeScript, Python, or .NET), Workers running in your environment, and connectivity to the Temporal Cloud endpoint.
Can we use AWS committed spend, budgets, and approvals when buying Temporal Cloud via Marketplace?
Short Answer: In most cases, yes—Temporal Cloud charges through AWS Marketplace can be treated like other AWS Marketplace SaaS spend and may count toward your AWS committed spend, depending on your AWS agreement.
Expanded Explanation:
The main reason many enterprises want Marketplace-based procurement is to align new services with existing AWS financial constructs. Because Temporal Cloud appears on your AWS bill, it can typically be routed through the same cost centers, approval chains, and budget controls you already use for AWS services and Marketplace vendors.
Whether Temporal Cloud usage counts toward your EDP/committed spend is governed by your specific AWS contract. Many customers negotiate Marketplace usage as qualifying spend with AWS, so Temporal Cloud effectively helps them utilize their commitments while giving developers a Durable Execution platform that eliminates orphaned processes and manual recovery work.
Why It Matters:
- You can adopt Temporal Cloud without creating a new standalone vendor path, which simplifies legal, finance, and procurement.
- You can often apply existing AWS committed spend and budgeting practices to Temporal Cloud, aligning reliability improvements with your broader cloud-spend strategy.
Quick Recap
You can absolutely use AWS Marketplace to buy Temporal Cloud. The Temporal Service you get is the same Durable Execution engine—Workflows, Activities, retries, timers, signals, schedules, and full Web UI visibility—but the billing path changes: AWS Marketplace meters your usage, consolidates it on your AWS invoice, and lets you apply existing procurement, approvals, and often committed spend programs. Your Workers still run in your own environment, Temporal never sees your code, and your developers gain a reliable backbone for long-running, failure-resilient workflows without fighting a separate vendor process.