Durable Workflow Orchestration
How do I sign up for Temporal Cloud and apply the $1,000 credits trial?
7 min read
Most teams discover Temporal Cloud when they’re tired of babysitting their own infrastructure and just want Durable Execution that’s “on” in a few clicks. The good news: signing up is simple, and the $1,000 in free credits are applied as part of that flow—no sales call or custom contract required.
Quick Answer: You sign up for Temporal Cloud from the Temporal website or AWS Marketplace, create an account with your work email (or Google/Microsoft), and the $1,000 credits trial is automatically applied to your new Cloud account for the first 90 days.
Frequently Asked Questions
How do I sign up for Temporal Cloud and get the $1,000 credits trial?
Short Answer: Go to Temporal Cloud, click “Sign up for Cloud,” create an account (Google, Microsoft, or work email), and your $1,000 in credits are applied automatically to your new Cloud organization for a 90‑day trial.
Expanded Explanation:
Temporal Cloud is the managed Temporal Service: reliable, scalable, serverless Temporal in 11+ regions, run and supported by the creators of the project. To get the $1,000 credits trial, you don’t need a promo code. When you create a new Temporal Cloud account through the standard sign‑up flow, the trial is attached to that account by default, giving you a no‑risk period to run real Workflows in production‑grade infrastructure.
During the trial, you pay nothing until you exceed the included credits or the 90‑day window. You keep full control over where your Workers run and how they connect to the Service; Temporal Cloud hosts only the Temporal Service, not your code.
Key Takeaways:
- Sign up via the Temporal Cloud page using Google, Microsoft, or a work email.
- The $1,000 credits and 90‑day trial are automatically attached to new Cloud accounts—no separate activation needed.
What are the exact steps to sign up for Temporal Cloud and apply the trial credits?
Short Answer: Sign up from the Temporal Cloud page, create your organization and account, choose your region(s), and start creating namespaces; the $1,000 free credits are applied to that organization as part of the onboarding flow.
Expanded Explanation:
The sign‑up process is designed to get you from “curious” to “running a Workflow in the cloud” in minutes, without forcing you to think about infrastructure. You bring your code and Workers; Temporal runs the Service. The trial credits ride along with that first organization you create.
A typical flow looks like this: discover Temporal Cloud on temporal.io, click “Sign up for Cloud,” authenticate, name your organization, pick a region, and create a namespace. From there, you point your Workers at the Cloud endpoint and start running Workflows. All usage during the trial is billed against the $1,000 credits.
Steps:
- Go to Temporal Cloud
Navigate to the Temporal website and choose “Sign up for Cloud” or follow the “Try Free with AWS” link if you prefer AWS Marketplace. - Create your account
Sign up using Google, Microsoft, or your work email. This creates a Temporal Cloud user and prompts you to create or join an organization. - Create your organization and namespace
Name your organization, choose your region(s), and create your first namespace. Your $1,000 credits trial is applied to this organization automatically for the first 90 days.
What’s the difference between signing up directly and via AWS Marketplace?
Short Answer: Both paths give you Temporal Cloud and access to the $1,000 credits trial; the main difference is where the billing shows up—direct with Temporal or through your AWS bill.
Expanded Explanation:
When you sign up directly on temporal.io, you create a Temporal Cloud account billed by Temporal. When you start from AWS Marketplace, Temporal Cloud usage appears on your AWS invoice. In both cases, you still connect from your Workers to the Temporal Service over a unidirectional, encrypted channel, and we still never see your code.
The choice is mostly about procurement and billing preferences. Some teams prefer AWS Marketplace to leverage existing budget and approvals; others want a direct relationship with Temporal. The Durable Execution primitives, reliability guarantees, and trial experience are the same.
Comparison Snapshot:
- Option A: Direct sign‑up on temporal.io
- Billing is handled directly by Temporal.
- Ideal if you want a direct vendor relationship and Temporal‑native account management.
- Option B: AWS Marketplace
- Billing flows through your AWS bill.
- Ideal if your org prefers AWS Marketplace procurement and consolidated billing.
- Best for:
- If you’re unsure, start with direct sign‑up; you can still align with your internal billing processes later.
How do I actually start using my Temporal Cloud trial after sign‑up?
Short Answer: After sign‑up, create a namespace, point your SDK Workers at the Cloud endpoint, and run your first Workflow; all execution in that account automatically consumes from the $1,000 credits.
Expanded Explanation:
The trial is not a sandbox with artificial limits—it’s the real Temporal Cloud. Once your account and namespace exist, you install an SDK (Go, Java, TypeScript, Python, or .NET), run Workers in your environment, and configure them to talk to your Temporal Cloud namespace. The Temporal Service in the cloud coordinates Workflow execution; your code never runs on Temporal’s infrastructure.
Expect the same Durable Execution behavior you’d get self‑hosting: Workflows capture event history, Activities get retries and timeouts, and you can inspect and replay executions via the Temporal Web UI. The difference is that you don’t manage the Service, the persistence layer, or the scaling profile.
What You Need:
- A Temporal SDK Worker running in your environment
- Go, Java, TypeScript, Python, or .NET, configured to connect to your Cloud namespace.
- Cloud connection details and credentials
- Namespace name and Cloud endpoint from the Cloud console, plus auth configuration (e.g., TLS/credentials) provided during onboarding.
How should I use the $1,000 credits trial strategically?
Short Answer: Use the trial to validate real workloads—migrate a meaningful Workflow, test reliability under failure, and benchmark developer experience—so you know exactly what value you’re getting before you pay.
Expanded Explanation:
The trial is meant for more than “hello world.” You have $1,000 in credits and up to 90 days—enough to move at least one serious, failure‑prone process into Temporal Cloud and prove that Durable Execution removes entire classes of operational pain.
This is your window to stop building state machines, stop sprinkling retry logic across services, and see what it feels like when order fulfillment, money movements, or AI pipelines keep running through crashes, timeouts, and deploys without manual recovery. Use Temporal Web UI to inspect, replay, and rewind workflows; that visibility is often the turning point where teams decide to standardize on Temporal.
Why It Matters:
- You de‑risk adoption with production‑grade infrastructure and no infra management.
- You evaluate Temporal itself, not your ability to operate a Temporal cluster—Cloud handles the Service so you can focus on code.
- You get a clear ROI signal before committing spend.
- Fewer orphaned processes, less on‑call toil, and faster feature delivery can all be measured as you run real workloads during the trial.
Quick Recap
To sign up for Temporal Cloud and apply the $1,000 credits trial, start from the Temporal Cloud sign‑up page (or AWS Marketplace), create your account and organization, and your credits are automatically attached for the first 90 days. From there, create a namespace, point your SDK Workers at the Cloud endpoint, and run real Workflows that survive crashes, timeouts, and outages without losing progress. You get the full Durable Execution experience—Workflows, Activities, retries, timers, and rich Web UI visibility—without managing the Temporal Service yourself.