Durable Workflow Orchestration
How do I sign up for Temporal Cloud and apply the $1,000 credits trial?
7 min read
What if you could try Temporal Cloud, run real workloads, and only pay once you’re convinced it should sit in the middle of your architecture? That’s exactly what the $1,000 credits trial is for: you get a full Temporal Cloud account, not a toy sandbox, with enough runway to build and validate durable, failure-resilient Workflows in production-like conditions.
Quick Answer: You sign up for Temporal Cloud through the Temporal website (or AWS Marketplace), create an organization, and the $1,000 free credits are automatically applied to your new Cloud account for the first 90 days of usage.
Frequently Asked Questions
How do I sign up for Temporal Cloud and activate the $1,000 credits?
Short Answer: Go to temporal.io, click “Sign up for Cloud,” create your account (via Google, Microsoft, or work email), and the $1,000 credits automatically attach to your new Temporal Cloud organization for a 90‑day trial.
Expanded Explanation:
Temporal Cloud is the managed, serverless way to run the Temporal Service without managing any of the underlying infrastructure. When you create a new Temporal Cloud organization via the Temporal site, your account is provisioned with a time‑boxed, usage‑based trial: $1,000 in free credits valid for the first 90 days. There’s no separate coupon code or sales call needed—credits are tied to new Cloud signups.
You can connect from your own Workers (Go, Java, TypeScript, Python, .NET) to Temporal Cloud using the SDK of your choice. You keep your code and Workers in your environment; Temporal Cloud only runs the Service that coordinates Workflow execution and stores execution histories. Either way, we never see your code.
Key Takeaways:
- Sign up from the Temporal site or AWS Marketplace, create an organization, and the trial credits apply automatically.
- You get the full Temporal Cloud experience—multi‑region, managed Temporal Service—not a reduced “demo” cluster.
What are the exact steps to sign up and start using the $1,000 trial credits?
Short Answer: Create a Temporal Cloud account, set up your first Namespace, connect a Worker using an SDK, and start running Workflows—the $1,000 credits automatically cover your usage during the trial window.
Expanded Explanation:
The signup flow is intentionally lightweight so you can move quickly from “click” to “first Workflow execution.” You choose how you authenticate (Google, Microsoft, or work email), then Temporal Cloud provisions your organization and lets you create one or more Namespaces—logical containers for your Workflows. From there, you point your Worker code at the Cloud endpoint instead of localhost and start running real Workflows backed by durable execution.
Under the hood, Temporal Cloud runs the Temporal Service in 11+ regions, handles storage, scaling, failover, and upgrades, and exposes secure endpoints. You pay only for what you use, and during the trial, that usage is offset by the included credits. If you decide it’s not right for you, you can stop using the service without any lock‑in.
Steps:
-
Go to Temporal Cloud signup
Visit https://temporal.io and click “Sign up for Cloud” (or use “Try Free with AWS” if you prefer the AWS Marketplace route). -
Create your Temporal Cloud account
Choose Sign up with Google, Sign up with Microsoft, or use a work email. This creates your Temporal Cloud organization and activates your $1,000 credits for the next 90 days. -
Create a Namespace and connect a Worker
From the Cloud console, create a Namespace. Then use the SDK of your choice (Go, Java, TypeScript, Python, .NET) to configure your Worker to talk to your Temporal Cloud Namespace endpoint and start running Workflows and Activities.
What’s the difference between Temporal Cloud with credits vs. self‑hosting Temporal?
Short Answer: Temporal Cloud gives you a fully managed, serverless Temporal Service with $1,000 in trial credits; self‑hosting gives you full control over infrastructure but also full responsibility for running and operating the Temporal Service yourself.
Expanded Explanation:
Without Temporal Cloud, you can deploy the open‑source Temporal Service on your own Kubernetes clusters or infrastructure. You control everything: cluster sizing, backups, upgrades, scaling, security posture, and incident response. That’s a good fit if you already maintain large distributed systems and want Temporal to live inside that operational model.
With Temporal Cloud, you offload all of that to the team that built Temporal and its predecessors (Amazon SWF, Azure Durable Task Framework, Uber Cadence). Cloud gives you “Reliable, scalable, serverless Temporal in 11+ regions” out of the box. You still run your Workers and code in your own environment, but you don’t manage the Control Plane. During the trial, you can exercise real workloads and see how it behaves before committing.
Comparison Snapshot:
- Temporal Cloud: Fully managed Temporal Service, 11+ regions, pay‑for‑usage with $1,000 in trial credits, no infra to run or upgrade.
- Self‑Hosted Temporal: Open‑source, MIT‑licensed, run entirely on your own infra, full control but full ops responsibility (upgrades, scaling, storage, failover).
- Best for:
- Cloud: teams that want to stop running stateful control planes and focus on Workflows and business logic.
- Self‑hosted: teams with strict in‑house infra policies or existing platforms built to run and operate complex distributed systems.
How do I actually use Temporal Cloud during the trial—what does implementation look like?
Short Answer: You point your application’s Workers at a Temporal Cloud Namespace, implement your Workflows and Activities in code, and let Cloud handle durability, retries, and state so executions always complete—even across crashes and outages.
Expanded Explanation:
Implementation starts on your side, in code. You use one of the native SDKs (Go, Java, TypeScript, Python, .NET) to define Workflows and Activities as regular functions. Temporal Cloud acts as the authoritative source of truth for execution state: every event is recorded in a durable history, and deterministic replay lets Workflow code recover from any crash by reconstructing its state.
During the trial, you can safely test real patterns: money movement, order fulfillment, CI/CD rollbacks, human approvals, AI pipelines. You can simulate failures—kill Workers, drop network connections, restart services—and watch Workflows pick up exactly where they left off without you writing any custom recovery logic.
What You Need:
-
An application environment for Workers
A runtime where your Worker processes run (Kubernetes, VMs, containers, or even a laptop for development). This is where your business logic lives; Temporal Cloud never runs your code. -
SDK configuration for Temporal Cloud
Connection details (Cloud endpoint, Namespace, credentials) configured in the SDK so your Workers can poll Cloud task queues, execute Activities, and respond to signals and timers.
How should teams use the $1,000 credits strategically to prove value?
Short Answer: Use the trial to migrate one or two failure‑prone workflows—where retries, timeouts, and orphaned processes are hurting you—so you can measure reduced incidents, faster recovery, and simpler code before rolling out broadly.
Expanded Explanation:
The $1,000 credits aren’t just about “playing” with Temporal Cloud; they’re there so you can de‑risk a real adoption decision. Pick a critical but bounded workflow where failures are painful today: maybe it’s a money‑movement pipeline, a multi‑step signup flow with external APIs, or an internal provisioning system. Implement it as a Temporal Workflow backed by Activities with policy‑based retries, heartbeats, and timeouts.
Then compare “before and after.” Without Temporal, you rely on ad‑hoc state machines, cron jobs, and manual reconciliation. When something breaks, you read logs and guess what happened. With Temporal Cloud, execution history is the source of truth: you can inspect, replay, and even rewind Workflows from the Web UI. The trial gives you enough runway to see incident rates drop and on‑call stress decline.
Why It Matters:
-
Prove reliability gains, not just feature parity.
Measure fewer orphaned processes, faster recovery from outages, and reduced manual runbooks. That’s the real point of Durable Execution. -
Showcase visibility and developer velocity.
Demonstrate how the Temporal Web UI, replayability, and declarative retries/timeouts replace custom glue code and make debugging and iteration dramatically faster.
Quick Recap
Signing up for Temporal Cloud with the $1,000 credits trial is straightforward: create a new Cloud organization from temporal.io (or via AWS Marketplace), and the credits apply automatically to your usage for the first 90 days. During that window, you can connect your own Workers, run real Workflows in production‑like conditions, and validate that Durable Execution—backed by Temporal’s event histories, replay, retries, and timers—eliminates lost progress and manual recovery work. You can compare Cloud against self‑hosting, but in both cases, your code only runs in your environment and Temporal never sees it.