Liquidsoap
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
A side-by-side editorial comparison of FusionAuth and NATS — release velocity, themes, recent moves, and the top alternatives to consider.
FusionAuth's feed publishes version numbers; whether they carry news is a coin flip.
FusionAuth releases every four to eight weeks, but the changelog entries are inconsistent: three of the last six carry nothing but an upgrade-guide link, while the ones that do have notes describe substantial standards and security work. The last documented release, 1.67.0, added RFC 8707 resource scoping so tokens issued by OAuth endpoints can be bound to specific resources. Before it, two consecutive releases tightened API key requirements — 1.65.0 for installation-wide endpoints, 1.66.0 extending the same rule to webhooks it had missed.
Two NATS trains keep shipping in lockstep, with JetStream durability the recurring subject.
The 2.14 and 2.12 lines released within a minute of each other again on August 12. 2.14.5 adds a configurable leafnode dial_timeout so high-latency remote links can exceed the one-second default, and both branches take a logger deadlock fix. The 2.12 cut also carries a JetStream fix for potential data loss when an offline node catches up from a metalayer snapshot during idempotent stream creates.
FusionAuth releases every four to eight weeks, but the changelog entries are inconsistent: three of the last six carry nothing but an upgrade-guide link, while the ones that do have notes describe substantial standards and security work. The last documented release, 1.67.0, added RFC 8707 resource scoping so tokens issued by OAuth endpoints can be bound to specific resources. Before it, two consecutive releases tightened API key requirements — 1.65.0 for installation-wide endpoints, 1.66.0 extending the same rule to webhooks it had missed.
Where the notes are readable, the direction is standards conformance and closing security defaults that were too permissive, accepting breaking changes to do it. FusionAuth has been willing to make an enabled identity provider's linking strategy immutable and to require global API keys where tenant keys used to work — changes that break running deployments in exchange for a tighter default. What cannot be read from this feed is where the last two releases fit, because they shipped without notes.
The pattern of hardening endpoint-by-endpoint suggests further scope narrowing wherever tenant-level keys still reach installation-level effects. Any read on 1.68.0 and 1.69.0 would be guesswork — the entries carry no content.
The 2.14 and 2.12 lines released within a minute of each other again on August 12. 2.14.5 adds a configurable leafnode dial_timeout so high-latency remote links can exceed the one-second default, and both branches take a logger deadlock fix. The 2.12 cut also carries a JetStream fix for potential data loss when an offline node catches up from a metalayer snapshot during idempotent stream creates.
JetStream's clustering and storage internals remain where the real work goes — Raft transport decoupling and disk concurrency limits last cycle, snapshot catch-up correctness this one. The dual-branch discipline holds: 2.12 receives current internals work, not just security fixes, which keeps the upgrade to 2.14 a choice rather than a forced march.
Expect the next pair to arrive minutes apart again with JetStream clustering fixes as the substance, and for 2.12 to keep receiving them until a stated end-of-life date appears in the upgrade guide.
Other DevOps 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 FusionAuth or NATS.
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
Appwrite keeps reworking its own plumbing — Go CLI, SquashFS mounts, and an MCP layer that refreshes itself
Sanity ships across every package at once, and the agent-facing surface moves fastest.
The 6.1 candidate arrives carrying the same notes the beta already shipped in June.
Auth0 hands tenants a throttle on their own noisy apps
Vitest 5 is in bug-fix mode: the second RC is almost entirely hardening
See all FusionAuth alternatives → · See all NATS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NATS is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. NATS is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top FusionAuth alternatives in DevOps are ranked by recent ship velocity. Browse the "FusionAuth alternatives" section above for the current picks, or visit /alternatives/fusionauth for the full list with editorial commentary on each.
Top NATS alternatives in DevOps are ranked by recent ship velocity. Browse the "NATS alternatives" section above for the current picks, or visit /alternatives/nats for the full list with editorial commentary on each.