NetBird
NetBird's second v0.82 candidate keeps the MySQL removal and deprecates Rosenpass.
A side-by-side editorial comparison of Hatchet and Okta — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Okta is documenting Cross App Access into every federation shape it supports
Okta's developer channel is running two threads at once. The dominant one is Cross App Access — the Identity Assertion Authorization Grant that lets an application or agent reach a third-party API on behalf of a user by exchanging tokens from an existing SSO trust. Since XAA was introduced in April, the output has been a systematic matrix of adoption guides: SAML requesting apps, SAML resource apps, and now the OIDC requesting and resource sides, plus listing XAA connections on the Okta Integration Network. The second thread is SDK and tutorial work, of which the Angular SDK going fully standalone is the substantive item.
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.
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.
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.
Okta's developer channel is running two threads at once. The dominant one is Cross App Access — the Identity Assertion Authorization Grant that lets an application or agent reach a third-party API on behalf of a user by exchanging tokens from an existing SSO trust. Since XAA was introduced in April, the output has been a systematic matrix of adoption guides: SAML requesting apps, SAML resource apps, and now the OIDC requesting and resource sides, plus listing XAA connections on the Okta Integration Network. The second thread is SDK and tutorial work, of which the Angular SDK going fully standalone is the substantive item.
This is a feed of developer-education posts rather than release notes, so it reads cadence rather than shipping — but the shape of the education is itself the signal. Okta is not adding new XAA capability; it is removing every remaining excuse not to adopt it, one federation topology at a time, so that neither a SAML shop nor an OIDC shop has to migrate first. The Angular SDK release points the same direction from the client side, dropping NgModule for standalone providers and function guards so the SDK matches how current Angular applications are actually written.
With OIDC and SAML now covered on both the requesting and resource sides, the remaining gaps in the matrix are framework SDKs and the agent runtimes themselves — expect XAA walkthroughs for more languages and agent frameworks in the vein of the earlier C# MCP post, rather than a new grant type.
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 Okta.
NetBird's second v0.82 candidate keeps the MySQL removal and deprecates Rosenpass.
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
incident.io's agent now runs your team's own tools, with a human approval before any change.
Airflow 3.4 reaches its first release candidate, a week after the 10-20 provider wave.
Redocly's reunite.agent gets per-duty cron schedules, rules and source repos.
Jackett ships a daily build to keep hundreds of torrent indexers working as sites move and close.
See all Hatchet alternatives → · See all Okta alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Hatchet is currently shipping more aggressively (velocity 6.3 vs 5.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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Hatchet is currently shipping more aggressively (velocity 6.3 vs 5.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.
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.
Top Okta alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Okta alternatives" section above for the current picks, or visit /alternatives/okta for the full list with editorial commentary on each.