Updated

Temporal

Durable execution platform that runs workflows as code, persisting their state so they survive crashes and retry failed steps automatically.

35 makers' products we track use Temporal. For background jobs & cron it's the most chosen of 9 options: 35 of the 81 makers' products we know the background jobs & cron of (43%). 20 open-source projects also declare it in their code. What makers like most: Durable workflows survive retries, timeouts, crashes and deploys, replacing fragile stacks of queues, timers and cron jobs. Their most common complaint: It adds a real step up in app complexity and cognitive overhead, and some teams migrated off happier.

Open sourceSelf-hostableFree tierPaid from $50 per 1M actions

Profile checked

Works with AI agents:llms.txt
Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

How makers use Temporal

Makers' products we track use Temporal for background jobs & cron (35), most often alongside Amazon Web Services (40%), OpenAI API (37%), Next.js (29%).

What Temporal is used for

Background Jobs & Cron · Durable workflow engine →Long-running, multi-step workflows — payments, onboarding, AI agent loops — whose state must survive crashes and deploys, in Go, Java, Python, TypeScript and more.Trade-off: You run worker processes, plus the Temporal server or Temporal Cloud billed per action; workflow code must be deterministic.
Temporal35Trigger.dev23Inngest16RabbitMQ3Dagster3Makers' products on each, for background jobs & cron

Temporal vs the alternatives makers chose

For background jobs & cron, 35 of the 81 makers' products we know the choice of picked Temporal (43%), the most of 9 options.

OptionMakers' productsFree forAt 10,000 usersOpen source
Temporal35 43%~1,800 users$5.50/mo · Developer (pay as you go)Yes
Trigger.dev23 28%~20,000 users$0/mo · FreeYesCompare →
Inngest16 20%~5,000 users$99/mo · ProYesCompare →
Dagster3 4%——Yes
RabbitMQ3 4%——Yes
Upstash2 2%~10,000 users$1.00/mo · Pay as you goNo

For background jobs & cron: how many of the 81 makers' products we know the background jobs & cron of chose each option, and what each costs at 10,000 users.

Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for.

Often paired with

Share of the 35 makers' products on Temporal that show this choice.

Markets that build with it most

Product Hunt markets where Temporal is in far more of the stacks we know than across every market (1%).

When to use Temporal, and when not

Pick Temporal if

Something else fits better if

  • You deploy to serverless hosting and have tasks that run for minutes: Trigger.dev.
  • One user action kicks off several steps with waits between them: Inngest.
  • You only need a scheduled call or a delayed HTTP request on serverless: Upstash.
  • You already run a Node server and want a free queue next to it, on Redis or Postgres: BullMQ.
From each decision's guide, written from what makers' products chose and why.

Temporal is an engine for code that has to finish even when servers crash, networks drop or a step takes days. You write a long-running process, such as an order flow, a sign-up sequence or an AI agent loop, as an ordinary function, and Temporal keeps it going to completion.

More about Temporal

There are two halves. The Temporal Service (an open-source Go server plus a database) records an append-only event history for every workflow run. Your Workers, which you host, run your code using one of the SDKs: Go, Java, TypeScript, Python, .NET, PHP or Ruby. After a failure, a worker replays the history to rebuild the workflow's state. That is why workflow code must be deterministic: calls to APIs, LLMs or databases go into separate "activities", which are retried on their own.

What a small team gets: retries and timeouts declared rather than hand-written, timers and signals that can wait for months, a web UI to inspect any run and its history, and a single-binary dev server (temporal server start-dev) for local work. You either run the service yourself on Postgres, MySQL or Cassandra, or use Temporal Cloud, which is offered in many AWS and Google Cloud regions.

The main cost is the programming model. Changing a workflow while old runs are still in flight requires versioning, and each run's history is capped (51,200 events or 50 MB), so very long loops need "continue-as-new". Self-hosting means operating a database and, for heavy search, Elasticsearch.

How Temporal itself is built

9 tools, from its own code, website and Product Hunt page.

Temporal pros and cons

What makers like most: Durable workflows survive retries, timeouts, crashes and deploys, replacing fragile stacks of queues, timers and cron jobs. Their most common complaint: It adds a real step up in app complexity and cognitive overhead, and some teams migrated off happier.

Pros

  • Durable workflows survive retries, timeouts, crashes and deploys, replacing fragile stacks of queues, timers and cron jobs. PHPH 2PH 3HN
  • Retries and compensating actions are handled by the platform, so application code describes business logic rather than failure handling. HNHN 2HN 3PH
  • It is mature and battle-tested, reliably finishing workflows that sleep for months. HNHN 2HN 3PH
  • The server is MIT-licensed and ships its own queue, persistence and UI, so self-hosters only manage workers. HNHN 2HN 3
Product Hunt review tags
fault tolerant8
workflow orchestration7
complex workflow management6
reliable execution5
scalable5
durable execution4

Cons and watch-outs

  • It adds a real step up in app complexity and cognitive overhead, and some teams migrated off happier. HNHN 2HN 3
  • Running it highly available in-house takes dedicated on-call engineers, which pushes teams to the paid cloud. HN
  • Heavy venture funding makes some users wary of vendor lock-in. HNHN 2

Themes that recur in makers' words and Hacker News comments, each linked to what it summarises, with how Product Hunt tags its reviews.

5.0★ from 28 reviews on Product Hunt ↗

What Hacker News says about Temporal

On Hacker News, 25% of comments about Temporal recommend it and 16% criticize it: net praise +9%, the best liked of 4 tools HN discusses for background jobs & cron. Commenters chose it 1.9× as often per month in 2026 as in 2025.

By year

YearComments choosing it, per monthNet praise
20230.5+38%
20240.8+12%
20251.90%
2026 (8 mo)3.6+6%

In their words

  • “I have used Temporal in the past, works really good” HN, May 2026
  • “I see this as Temporal surfacing inherent complexity of the domain in a way that forces the developer to consider it” HN, May 2026
  • “Have worked in a codebase using Temporal, and is pretty much a nightmare.” HN, May 2026

Hacker News comments January 2023 to August 2026 that name Temporal in a sentence like "I use" or "we moved to", Claude read a sample of 95 and the counts scale it to all of them; net praise is comments recommending it minus comments criticizing it, as a share of all comments about it. How it's counted, and how HN compares with makers.

Reliability and open issues

Temporal's status page posted 23 incidents in the last 90 days, 3 major; the most wanted open issue on GitHub has 75 👍.

Incidents on its status page

23 in the last 90 days, 3 major · 50+ in the last yearFrom its own status page, 2026-10-19. Vendors decide what they post; one page can cover several products.

Most wanted on GitHub

Open on 2026-10-04 in temporalio/temporal, with activity in the last year — issues and feature requests by 👍.

Who switches

Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general.

Moving to Temporal
Temporal

Who uses it

35 makers' products, each linked to the source that shows it, and 20 open-source projects that declare it in their code. The best known on Product Hunt: Velo (2,622 followers), Descript (1,702 followers), Slashy (1,259 followers), Atlas (911 followers), Flexprice (856 followers).

The maker says so 22Subprocessor list 9Job posting 6Declared in code 21How evidence is collected →
Postiz
PostizSocial media scheduling and analytics tool for planning, AI-assisted drafting, and auto-…

“We could not make this without Temporal super system for workflows”

Background Jobs & CronMaker says so +1 · source ↗
Slashy
SlashyAI email client that triages the inbox and drafts replies in your voice, connected to ca…

“We chose Temporal because email automations, reminders, and background jobs need to survive retries, delays, and service interruptions. Durable workflows give us a much stronger foundation than stitching together fragile queues and cron jobs.”

Background Jobs & CronMaker says so +1 · source ↗
Flexprice
FlexpriceUsage-based pricing and billing for developers

“The orchestration engine behind delayed events like trial expiries and billing reminders.”

Background Jobs & CronMaker says so +1 · source ↗
RunLLM
RunLLMAI that doesn’t just respond—it resolves

“It powers our multi-step workflows across agent actions. Temporal gives us durability, visibility, and precise control. Battle-tested orchestration with strong developer UX.”

Background Jobs & CronMaker says so · source ↗
Central
CentralPayroll, benefits and compliance for US startups, automating filings such as state regis…

“Temporal is like React for asynchronous and scheduled tasks. It lets us build complex workflows with confidence and resilience, making sure they work perfectly every time.”

Background Jobs & CronMaker says so · source ↗
Velo
VeloAI video infrastructure to explain, train, and sell faster

“We chose Temporal because it provides a reliable foundation for long-running tasks.”

Background Jobs & CronMaker says so · source ↗
Breyta.ai
Breyta.aiInstantly synthesize multiple files of unstructured data

“We’ve been using Temporal.io and value its reliability and flexibility. Writing our pipelines in code gives us control over our orchestration and lets us tailor workflows to our needs. Instead of rigid structures, Temporal.io allows us to innovate while keeping processes smooth. It’s a solid tool for automating operations and scaling our applications”

Background Jobs & CronMaker says so · source ↗
Hoplite
HopliteEffortlessly deploy cloud software factories.

“Temporal gave us incredibly good reliability and cold/warm start times - we're able to start threads in well under a second thanks to it and Modal.”

Background Jobs & CronMaker says so · source ↗
Offloop
OffloopA shared workspace where people and AI agents get work done

“Offloop lets people and Agents hand work back and forth, and some of that work can run for a long time. Temporal makes those runs durable, so retries, timeouts, and deploys do not erase progress or force us to rebuild the orchestration ourselves.”

Background Jobs & CronMaker says so · source ↗
Finyuus
FinyuusA code-first language for durable, governed AI workflows

“Durable runtimes are highly necessary for apps like this. Temporal was the natural choice here.”

Background Jobs & CronMaker says so · source ↗
Slicker
SlickerRecover payment failures and maximize subscription revenue

“Reliable execution of tasks is the backbone of many of the solutions we offer and Temporal is a great enabler for this.”

Background Jobs & CronMaker says so · source ↗
Julep AI
Julep AIAutomate Browser Tasks with AI Workflows

“We use Temporal under the hood. They enable us to manage complex, large-scale workflows with reliability and efficiency. Their platform's automatic task retries and robust observability tools have been instrumental in scaling our operations seamlessly.”

Background Jobs & CronMaker says so · source ↗
Roark
RoarkTest, monitor, and improve your voice agents

“As a team building complex workflows in voice AI, Roark wouldn’t exist without Temporal. It gave us the reliability of a distributed system without drowning in glue code. Temporal turned what used to be a mess of retries, timers, and state machines into something we can trust to run at scale.”

Background Jobs & CronMaker says so · source ↗
DeepTagger
DeepTaggerFrom Documents to Structured Data with Interactive Labelling

“Amazing for tagging async jobs and querying their status. Very dev-friendly in standalone mode, and very powerful in production mode.”

Background Jobs & CronMaker says so · source ↗
Hyta
HytaAI training network to connect and share insights

“Temporal gave us the most reliable way to run long-lived workflows with built-in retries, state, and observability, without reinventing orchestration ourselves.”

Background Jobs & CronMaker says so · source ↗
DitLead
DitLeadLinkedin and email outreach, sales automation and engagement

“Temporal is the backbone of our infrastructure at DitLead allowing us to build resilient workflow that automate outreach campaign.”

Background Jobs & CronMaker says so · source ↗
waoowaoo
waoowaoo首家工业级全流程 AI 影视生产平台。Industry-first professional AI Agent platform for controllable film &…Background Jobs & CronIn its code · source ↗
tsed
tsed:triangular_ruler: Ts.ED is a Node.js and TypeScript framework on top of Express to writ…Background Jobs & CronIn its code · source ↗

Open source: a project that declares Temporal as a dependency in its public code — verifiable, but not necessarily a live product.

Alternatives to Temporal

All alternatives by situation →

Questions makers ask about Temporal

Is Temporal good for production?

35 makers' products we track run on it. Its own status page posted 23 incidents in the last 90 days, 3 of them major; vendors decide what they post there, so this doesn't compare across tools. The watch-out makers raise most: It adds a real step up in app complexity and cognitive overhead, and some teams migrated off happier.

What is Temporal used for?

Durable execution platform that runs workflows as code, persisting their state so they survive crashes and retry failed steps automatically. Makers' products we track use it for background jobs & cron (35).

What are the pros and cons of Temporal?

Pros makers name: Durable workflows survive retries, timeouts, crashes and deploys, replacing fragile stacks of queues, timers and cron jobs. Retries and compensating actions are handled by the platform, so application code describes business logic rather than failure handling. It is mature and battle-tested, reliably finishing workflows that sleep for months. Cons: It adds a real step up in app complexity and cognitive overhead, and some teams migrated off happier. Running it highly available in-house takes dedicated on-call engineers, which pushes teams to the paid cloud. Heavy venture funding makes some users wary of vendor lock-in.

What are the alternatives to Temporal?

For background jobs & cron, the other options makers' products we track chose most are Trigger.dev (23), Inngest (16), Dagster (3), RabbitMQ (3), Upstash (2). Open source or self-hostable among them: Trigger.dev, Inngest, Dagster, RabbitMQ. Each alternative, with the situation it fits, is on the Temporal alternatives page.

How much does Temporal cost per month?

At 10,000 users, Temporal costs $5.50 a month on the cheapest plan that fits (Developer (pay as you go)), from its pricing page.

When should you use Temporal?

A process runs for days or months and must pick up where it left off after a crash (background jobs & cron). Something else fits better if: you deploy to serverless hosting and have tasks that run for minutes, pick Trigger.dev; one user action kicks off several steps with waits between them, pick Inngest.

Does Temporal Cloud run my code?

No. Temporal Cloud only runs the Temporal Server; your Workers and application code run in your own containers or VMs, wherever you host them. source ↗

Which languages can I write workflows in?

Temporal has SDKs for Go, Java, TypeScript, Python, .NET, PHP and Ruby, each with its own developer guide. source ↗

Why must workflow code be deterministic?

Temporal rebuilds a workflow's state by replaying its event history, so the code must issue the same calls in the same order every time. Anything non-deterministic, such as API calls, LLM requests or database queries, belongs in activities, which run outside replay and are retried automatically. source ↗

What do I need to self-host it?

The only required dependency is a persistence database; Cassandra, PostgreSQL and MySQL are tested for production, while SQLite is for development and testing only. For local work, temporal server start-dev starts a complete service with the web UI in one binary. source ↗

Which regions does Temporal Cloud run in?

You create each namespace in a chosen AWS or Google Cloud region, including locations in North America, South America, Europe and Asia Pacific. Temporal recommends picking the region closest to your workers. source ↗

Can Temporal Cloud read my workflow data?

Not if you enable client-side encryption. The Data Converter encrypts payloads on your workers before they reach Temporal Cloud, and a Codec Server you run decrypts them for the web UI without sharing keys. Temporal states it is SOC 2 Type 2 certified and compliant with GDPR and HIPAA. source ↗

What uptime does Temporal Cloud guarantee?

Standard namespaces have a 99.9% contractual guarantee and namespaces using the High Availability feature have 99.99%, measured per namespace. source ↗

Is there a limit on how long a workflow can run?

There is no time limit, but each run's event history is capped at 51,200 events or 50 MB, with warnings starting at 10,240 events or 10 MB. Long-lived workflows hand their state to a new run with fresh history using continue-as-new. source ↗

Is Temporal free?

Yes — there is a free tier a small product can run on; paid use starts at $50 per 1M actions. source ↗

Is Temporal open source or self-hostable?

Open source, and you can self-host it. source ↗

Can AI coding agents work with Temporal?

It serves an llms.txt docs index.

Who uses Temporal?

35 makers' products we track, each with a source, and 20 open-source projects declare it in their code. The best known of them on Product Hunt: Velo (2,622 followers), Descript (1,702 followers), Slashy (1,259 followers), Atlas (911 followers), Flexprice (856 followers). source ↗