NetBird
NetBird's second v0.82 candidate keeps the MySQL removal and deprecates Rosenpass.
Comparison · Infra & APIs
Hatchet vs NetBox
A side-by-side editorial comparison of Hatchet and NetBox — release velocity, themes, recent moves, and the top alternatives to consider.
Hatchet vs NetBox: at a glance
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 NetBox?
NetBox 4.7 adds cooling infrastructure modeling and replaces django-mptt with PostgreSQL ltree — a structural rewrite under the hood.
NetBox 4.7 is the most architecturally significant release in recent memory. Hierarchical models (Region, SiteGroup, Location, DeviceRole, and others) have been migrated from django-mptt to a PostgreSQL ltree column — a change that drops four MPTT columns from every affected table and breaks any plugin using low-level MPTT APIs. On the feature side, cooling infrastructure gets a full first-class data model mirroring the existing power model: CoolingSource, CoolingFeed, CoolingIntake, and CoolingOutflow map the full coolant chain from facility plant to device cold-plate. The 4.6.x line continues parallel maintenance with weekly patch releases.
Hatchet vs NetBox: 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.
NetBox
6.3INFRA · APIS
NetBox 4.7 adds cooling infrastructure modeling and replaces django-mptt with PostgreSQL ltree — a structural rewrite under the hood.
◆ Current state
NetBox 4.7 is the most architecturally significant release in recent memory. Hierarchical models (Region, SiteGroup, Location, DeviceRole, and others) have been migrated from django-mptt to a PostgreSQL ltree column — a change that drops four MPTT columns from every affected table and breaks any plugin using low-level MPTT APIs. On the feature side, cooling infrastructure gets a full first-class data model mirroring the existing power model: CoolingSource, CoolingFeed, CoolingIntake, and CoolingOutflow map the full coolant chain from facility plant to device cold-plate. The 4.6.x line continues parallel maintenance with weekly patch releases.
◆ Where it's heading
The ltree migration is a long-overdue structural cleanup — MPTT was a Django-era workaround for hierarchical data that PostgreSQL has handled natively for years. Cooling infrastructure fills the one obvious gap in NetBox's physical infrastructure modeling: power was already end-to-end; cooling wasn't. Together these suggest NetBox is pushing toward completeness as a single source of truth for data center physical plant, not just network topology. Plugin authors will need a meaningful migration effort.
◆ Prediction
The next major release will focus on stabilizing the plugin ecosystem after the ltree and email system changes. Expect more denormalized caching (the config context pre-render is a template) to reduce per-request query load as NetBox deployments scale.
Alternatives to Hatchet and NetBox
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 NetBox.
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 NetBox alternatives →
Recent activity from Hatchet and NetBox
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21h agoHatchetHatchet v0.115.0: contributor list update, no product notes
- 22h 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
- 1mo agoNetBoxNetBox v4.7.0 ⚡
- 1mo agoNetBoxNetBox v4.6.10
- 2mo agoNetBoxNetBox v4.7.0-beta2
- 2mo agoNetBoxNetBox v4.6.9
- 2mo agoNetBoxNetBox v4.7.0-beta1
- 2mo agoNetBoxNetBox v4.6.8
Frequently asked questions
What is the difference between Hatchet and NetBox?
They serve adjacent needs but don't currently overlap on shipped themes. Hatchet and NetBox are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Hatchet better than NetBox?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Hatchet and NetBox are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 NetBox?
Top NetBox alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "NetBox alternatives" section above for the current picks, or visit /alternatives/netbox for the full list with editorial commentary on each.