NetBird
NetBird's second v0.82 candidate keeps the MySQL removal and deprecates Rosenpass.
Comparison · Infra & APIs
Hatchet vs Instatus
A side-by-side editorial comparison of Hatchet and Instatus — release velocity, themes, recent moves, and the top alternatives to consider.
Hatchet vs Instatus: at a glance
| Feature | Hatchet | Instatus |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | durable execution, serverless, task queues, rate limiting | status-page, incident-response, slack-native, monitoring |
| Last editorial update | 17h ago | 5mo ago |
| Website | Visit → | — |
What is Hatchet?
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
Hatchet's new @hatchet-dev/serverless 0.1.0 runs tasks on Cloudflare Workers, Vercel and Node. An in-engine operator delivers them by signed POST or by an invocation websocket that also carries durable sleeps, waits and child runs. Around it, the engine shipped three patches in a day: DAG replays no longer take an advisory lock, worker shutdown now waits for durable tasks, and status queries use partition pruning. The API now declares 429 with Retry-After on every authenticated call.
What is Instatus?
Instatus has grown from status pages into a Slack-native incident response platform.
After launching Instatus 2.0 in mid-2025 with monitoring and incident response added to the existing status-page core, the past two quarters have been about polishing the incident lifecycle. The January release was the biggest expansion: full /incident command set in Slack, dedicated per-incident channels, postmortems from chat, and emoji-driven incident creation. Recent months added recurring maintenance windows, third-party status-page aggregation (Statuspage), General Notices, Freshstatus migration, Zapier, Jira, WhatsApp, Resend, and Brevo integrations.
Hatchet vs Instatus: editorial side-by-side
Hatchet
6.3INFRA · APIS
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
◆ Current state
Hatchet's new @hatchet-dev/serverless 0.1.0 runs tasks on Cloudflare Workers, Vercel and Node. An in-engine operator delivers them by signed POST or by an invocation websocket that also carries durable sleeps, waits and child runs. Around it, the engine shipped three patches in a day: DAG replays no longer take an advisory lock, worker shutdown now waits for durable tasks, and status queries use partition pruning. The API now declares 429 with Retry-After on every authenticated call.
◆ Where it's heading
Until now, running Hatchet meant running long-lived workers. The serverless package removes that requirement, so durable execution can run where JavaScript teams already deploy. The engine work points the same way: rate limits declared in the spec, safer worker acks, cheaper status queries. Patch cadence is still very high, often several engine tags a day, and much of it fixes durable-task edge cases.
◆ Prediction
Expect quick 0.1.x serverless releases as early users hit edge cases on each platform, and possibly matching Python handlers. More engine patches on durable-task shutdown and replay are likely.
Instatus
0.0INFRA · APIS
Instatus has grown from status pages into a Slack-native incident response platform.
◆ Current state
After launching Instatus 2.0 in mid-2025 with monitoring and incident response added to the existing status-page core, the past two quarters have been about polishing the incident lifecycle. The January release was the biggest expansion: full /incident command set in Slack, dedicated per-incident channels, postmortems from chat, and emoji-driven incident creation. Recent months added recurring maintenance windows, third-party status-page aggregation (Statuspage), General Notices, Freshstatus migration, Zapier, Jira, WhatsApp, Resend, and Brevo integrations.
◆ Where it's heading
The arc is clear: Instatus is going head-to-head with Atlassian's Statuspage and Better Stack on a single integrated stack — monitoring, incident response, public communication. The Slack-native push is the real differentiator; incident commanders rarely want to leave Slack. Migration tools (Freshstatus) and third-party aggregation (Statuspage import) point at land-and-expand against incumbents.
◆ Prediction
Expect on-call and scheduling integrations next, expanded migration tooling for other status-page incumbents (Better Stack, Status.io), AI-powered incident summarization and postmortems, and broader monitoring coverage — likely synthetic and browser checks.
Alternatives to Hatchet and Instatus
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Hatchet or Instatus.
GitHub
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
incident.io
incident.io's agent now runs your team's own tools, with a human approval before any change.
Apache Airflow
Airflow 3.4 reaches its first release candidate, a week after the 10-20 provider wave.
Redocly
Redocly's reunite.agent gets per-duty cron schedules, rules and source repos.
Jackett
Jackett ships a daily build to keep hundreds of torrent indexers working as sites move and close.
See all Hatchet alternatives → · See all Instatus alternatives →
Recent activity from Hatchet and Instatus
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 22h agoHatchetHatchet v0.115.0: contributor list update, no product notes
- 1d agoHatchetHatchet v0.114.15 fixes migration deadlocks
- 1d agoHatchetHatchet v0.114.14 builds its own continuous aggregates
- 1d agoHatchetHatchet v0.114.13 quiets noisy DAG operator errors
- 1d agoHatchetPython SDK 1.43.2 parses 429 rate-limit errors
- 1d agoHatchetHatchet v0.114.12 adds a Concurrency dashboard page
- 7mo agoInstatusRecurring maintenance windows and Statuspage aggregation
- 8mo agoInstatusPersistent General Notices on status pages
- 9mo agoInstatusFreshstatus migration import; Slack incident-channel toggle
- 10mo agoInstatusSlack-native incident response: /incident commands and per-incident channels ⚡
- 11mo agoInstatusZapier integration, OR conditions, Workspaces API
- 0y agoInstatusJira Service Management, WhatsApp alerts, Resend, Brevo
Frequently asked questions
What is the difference between Hatchet and Instatus?
They serve adjacent needs but don't currently overlap on shipped themes. Hatchet is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Hatchet better than Instatus?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Hatchet is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Hatchet?
Top Hatchet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Hatchet alternatives" section above for the current picks, or visit /alternatives/hatchet for the full list with editorial commentary on each.
What are the best alternatives to Instatus?
Top Instatus alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Instatus alternatives" section above for the current picks, or visit /alternatives/instatus for the full list with editorial commentary on each.