Comparison · Self-hosted vs Self-hosted

Dispatch vs Temporal

Temporal is $25/mo (Cloud Starter). Dispatch is a self-hosted alternative at $0.99/mo. Here's when each makes sense.

Try Dispatch Free Dispatch overview
DispatchTemporal
HostingSelf-hosted, your infraOSS requires Cassandra/Postgres, Elasticsearch, and multiple services
Data locationYour server, your diskYour server (if self-hosted)
Free tier100 tasks/moPaid only
Pro pricing$0.99/mo$25/mo (Cloud Starter)
DependenciesNone (single binary + SQLite)Docker, Postgres, etc.
Setup time~30 seconds15-30 minutes (self-host)
DashboardBuilt-in at /uiWeb UI
LicenseBSL 1.1Open source
When to use Dispatch

Pick Dispatch when you want simplicity and ownership.

Dispatch is a single Go binary with embedded SQLite. Install it with one command, and you are running in under a minute. Your data stays on your server.

curl -fsSL https://stockyard.dev/dispatch/install.sh | sh
Install Dispatch Dispatch docs

Temporal makes sense when you need more.

Temporal is the most powerful workflow orchestration platform available. If you need durable execution with replay and versioning, Temporal is in a class of its own. If you need simple task routing and dispatch without a distributed system, Dispatch handles the basics.
Making the decision

Before choosing between Dispatch and Temporal, consider what happens when you need to leave. Temporal exports vary in completeness — some fields, some history, some metadata may not come with you. Dispatch stores everything in a single SQLite file. Leaving means copying that file. This is not a hypothetical concern: the average team changes tools every 18 to 24 months.

Dispatch runs as a single static binary with an embedded SQLite database. There is no application server, no cache layer, no background worker. One process handles HTTP requests and reads from and writes to the database file directly. This simplicity is the entire point — fewer moving parts means fewer things that can break at 2 AM.

Temporal can be self-hosted, but the experience differs significantly from Dispatch. OSS requires Cassandra/Postgres, Elasticsearch, and multiple services With Dispatch, self-hosting means downloading one file and running it. The gap in operational complexity matters most for small teams without dedicated DevOps staff.

Switching from Temporal

Switching from Temporal to Dispatch is straightforward for most teams. Export your data from Temporal (most services offer CSV or JSON export), then POST each record to Dispatch's API. A migration script that reads the export and writes to /api/ endpoints typically takes less than 50 lines of code. The reverse migration is equally simple — Dispatch's SQLite database is a standard file you can query with any SQLite client.

FAQ
Is Dispatch a Temporal alternative?
Temporal handles durable workflow orchestration. Dispatch routes tasks to workers. Temporal is far more capable; Dispatch is far simpler.
Does Dispatch support durable execution?
No. Dispatch routes tasks with retry. For durable execution with replay, Temporal is necessary.
Related

Dispatch overview

Get started

Self-hosted task router in 30 seconds.

Single binary. Free to start. $0.99/mo for Pro.

Install Dispatch All 150 tools for $29/mo →