For two years we told small teams to skip Temporal. The 2026 SDK and the new self-hosted single-binary mode changed the math. Tool Tuesday #1 opens our weekly tool deep-dive series with the workflow engine that finally earns its complexity.
What it is, in one paragraph
Temporal is a workflow engine: you write business logic as plain code, and it guarantees that long-running, multi-step processes survive crashes, retries, deploys, and time. Think Airflow for transactional logic, not data pipelines.
What changed in 2026
- Single-binary self-host. A single command starts a usable Temporal server with embedded SQLite for dev. Production swap-in is a config flag.
- Improved TypeScript and Python SDKs. The serialization rules now match what your team will write naturally - fewer "do not capture closures" footguns.
- Cloud pricing tiers below $50 a month for low-throughput hobby and small-business loads.
When it earns its place
Pick Temporal when you have at least one of these signals: workflows that span hours-to-days, retries that must respect business state (not just HTTP), or a team that has already wired three different "I will fix it after coffee" cron tabs.
When to skip it
Skip Temporal if all your jobs finish in under 60 seconds, or if your scheduler needs are "every five minutes, run this script". A pg-boss queue plus a cron will save you a month.
A starter workflow you can ship today
- Self-host the single binary on a $5 VPS. SQLite is fine to start.
- Wire one high-value workflow first - usually a multi-step onboarding or a refund flow.
- Use activities for anything that talks to the network. Keep workflow code deterministic.
- Add a single dashboard widget for stuck workflows. The "stuck count" metric is your single best alert.
Next week
Tool Tuesday #2 looks at Inngest, the closest cousin to Temporal in 2026, and where it wins.