Temporal alternatives
Every queues and background jobs provider this site tracks, ordered by iScore — the same peers Temporal's own score is measured against. The line under each name is where its sourced facts differ from Temporal's; where a full comparison exists, the row links to it.
- Amazon SQSvs TemporalFree tier: Yes vs No · Kind of free offer: Free tier vs Free credit
- Trigger.devvs TemporalFree tier: Yes vs No · Kind of free offer: Free tier vs Free credit
- Google Cloud Pub/Subvs TemporalFree tier: Yes vs No · Kind of free offer: Free tier vs Free credit
- Upstash QStashFree tier: Yes vs No · Kind of free offer: Free tier vs Free credit
- Cloudflare Queuesvs TemporalFree tier: Yes vs No · Kind of free offer: Free tier vs Free credit
- Hatchetvs TemporalFree tier: Yes vs No · Kind of free offer: Free tier vs Free credit
- Zeplovs TemporalFree tier: Yes vs No · Kind of free offer: Free tier vs Free credit
- Inngestvs TemporalFree tier: Yes vs No · Kind of free offer: Free tier vs Free credit
- Azure Queue Storagevs TemporalPricing model: Per region and per redundancy, metered on operations and on stored data; LRS, ZRS, GRS an…
Where Temporal stands against these 9
Temporal's own sourced figures, placed among the alternatives above that document the same thing in the same unit. A rank here is one criterion, not a verdict; the iScore above weighs all of them.
- Free tier
- No. 8 of the 9 alternatives that document it have one: Amazon SQS, Cloudflare Queues, Google Cloud Pub/Sub, Hatchet, Inngest, Upstash QStash and 2 more.
- Regions
- 20 regions for Temporal Cloud Namespaces: 14 AWS regions and 6 Google Cloud regions, each with a PrivateLink…2nd highest of the 4 that document it. Highest: Amazon SQS — 34 commercial AWS Regions plus 2 AWS GovCloud (US) Regions listed in the SQS service endpoints table.
- Uptime SLA
- 99.9% on the pay-as-you-go Temporal Cloud plan (no base fee), with 99.99% High Availability optionsJoint 2nd highest of the 4 that document it. Highest: Google Cloud Pub/Sub — 99.95% or better for Pub/Sub.
- Maximum message size
- 2 MB maximum payload per request (each Workflow/Activity argument or return value); 4 MB per Event History…4th highest of the 9 that document it. Highest: Inngest — 4 MiB per step-returned payload; 32 MiB total function run state; 10 MiB hard cap per event batch.
- Maximum delay
- Timers (durable sleeps) may run up to 100 years in Temporal CloudHighest of the 5 that document it. Next: Inngest — Step sleeps up to 1 year on paid plans; the free plan supports sleeps up to 7 days.
A rank whose 80% interval overlaps its neighbour's is an ordering, not a finding; the intervals are on each provider's page and in /scores.json.
