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 Apache TomEE and FusionAuth — release velocity, themes, recent moves, and the top alternatives to consider.
A Jakarta EE server whose changelog is mostly dependabot — until EE11 moved to main
TomEE ships a steady stream of 10.1.x and 10.2.0 patch releases whose release notes are dominated by dependency bumps and regenerated BOMs, with one or two real TOMEE- ticket fixes buried in each. The genuinely new thing is 11.0.0-M1, the first milestone of the next major line, created when Jakarta EE 11 work moved onto the main branch. The 10.x line continues in parallel as the stable target.
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.
TomEE ships a steady stream of 10.1.x and 10.2.0 patch releases whose release notes are dominated by dependency bumps and regenerated BOMs, with one or two real TOMEE- ticket fixes buried in each. The genuinely new thing is 11.0.0-M1, the first milestone of the next major line, created when Jakarta EE 11 work moved onto the main branch. The 10.x line continues in parallel as the stable target.
The project is running the classic app-server two-track pattern: keep 10.x boring and current on its dependency surface, while the EE11 rearchitecture accumulates on main behind milestone tags. Nearly all visible energy goes into staying aligned with Tomcat, ActiveMQ, Hibernate, Jackson and MicroProfile versions — which for a server whose value is spec compliance is the actual product work, not a distraction from it.
Expect further 11.0.0 milestones with EE11 certification as the gate, while 10.1.x/10.2.x continue absorbing upstream dependency updates and isolated ticket fixes.
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.
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 Apache TomEE or FusionAuth.
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 Apache TomEE alternatives → · See all FusionAuth alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Apache TomEE and FusionAuth are shipping at a similar cadence (velocity 2.5 vs 2.5, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Apache TomEE and FusionAuth are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Apache TomEE alternatives in DevOps are ranked by recent ship velocity. Browse the "Apache TomEE alternatives" section above for the current picks, or visit /alternatives/apache-tomee for the full list with editorial commentary on each.
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.