Liquidsoap
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
Comparison · DevOps
FusionAuth vs Stirling-PDF
A side-by-side editorial comparison of FusionAuth and Stirling-PDF — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:self-hosted
FusionAuth vs Stirling-PDF: at a glance
What is FusionAuth?
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.
What is Stirling-PDF?
Stirling PDF is clearing the decks — six weeks of hotfixes ahead of a promised big release.
Every release in this window is corrective. 2.14.3 fixes tool operations failing on Debian 12 and Fedora 44, concurrency problems on merge, an automation bug in image removal, and crashes on 2GB PDFs, plus Linux startup and a Windows ARM64 test build. Before it, 2.14.2 patched Postgres user-data loading, 2.14.1 stopped PostHog loading before opt flags were read and fixed certificate signing, and 2.13.2 covered security fixes and desktop performance. The one feature release is 2.14.0, which added hardware token signing via PKCS#11 smart cards and OS certificate stores on desktop.
FusionAuth vs Stirling-PDF: editorial side-by-side
FusionAuth
2.5DEVOPS
FusionAuth's feed publishes version numbers; whether they carry news is a coin flip.
◆ Current state
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 it's heading
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.
◆ Prediction
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.
Stirling-PDF
5.0DEVOPS
Stirling PDF is clearing the decks — six weeks of hotfixes ahead of a promised big release.
◆ Current state
Every release in this window is corrective. 2.14.3 fixes tool operations failing on Debian 12 and Fedora 44, concurrency problems on merge, an automation bug in image removal, and crashes on 2GB PDFs, plus Linux startup and a Windows ARM64 test build. Before it, 2.14.2 patched Postgres user-data loading, 2.14.1 stopped PostHog loading before opt flags were read and fixed certificate signing, and 2.13.2 covered security fixes and desktop performance. The one feature release is 2.14.0, which added hardware token signing via PKCS#11 smart cards and OS certificate stores on desktop.
◆ Where it's heading
The project is consolidating a desktop application on top of what was a server tool, and the defect pattern shows where that hurts: platform-specific startup failures, OS certificate integration, ARM64 builds, large-file memory behaviour. Hardware token signing is the strategically interesting piece, since it moves the product toward legally meaningful signatures that a browser-only tool cannot offer. The 2.14.3 notes state a large feature release is two to three weeks out.
◆ Prediction
The changelog explicitly promises a substantial feature release in two to three weeks, and the stabilisation pattern supports that. Hardware token signing spreading beyond desktop-only is the natural extension of the 2.14.0 work.
Alternatives to FusionAuth and Stirling-PDF
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 Stirling-PDF.
Appwrite
Appwrite keeps reworking its own plumbing — Go CLI, SquashFS mounts, and an MCP layer that refreshes itself
Sanity
Sanity ships across every package at once, and the agent-facing surface moves fastest.
ESP-IDF
The 6.1 candidate arrives carrying the same notes the beta already shipped in June.
Auth0
Auth0 hands tenants a throttle on their own noisy apps
Vitest
Vitest 5 is in bug-fix mode: the second RC is almost entirely hardening
See all FusionAuth alternatives → · See all Stirling-PDF alternatives →
Recent activity from FusionAuth and Stirling-PDF
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoStirling-PDF2.14.3 fixes Debian/Fedora tool failures, concurrency and 2GB PDF crashes
- 15d agoFusionAuthFusionAuth 1.69.0 ships with no published release notes
- 1mo agoStirling-PDF2.14.2 Hotfix for certain postgres environments
- 1mo agoStirling-PDF2.14.1 Bug fixes and new 3rd party license page
- 1mo agoStirling-PDF2.14.0 Hardware token signing and shared signing
- 1mo agoFusionAuthFusionAuth 1.68.0 (Intelligent Kamfa), notes not published
- 1mo agoStirling-PDF2.13.2 Desktop performance fix, and security fixes
- 2mo agoStirling-PDF2.13.1 bug fixes for desktop upload from mobile and multitool rotations
- 2mo agoFusionAuthFusionAuth 1.67.1 patch, no notes published
- 2mo agoFusionAuthRFC 8707 OAuth resource scoping for tokens
- 3mo agoFusionAuthWebhook endpoints now require global API keys (breaking)
- 3mo agoFusionAuthBreaking: IdP linking strategy locked, tenant-key access narrowed
Frequently asked questions
What is the difference between FusionAuth and Stirling-PDF?
Both compete on the same themes — self-hosted — within DevOps. Stirling-PDF 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.
Is FusionAuth better than Stirling-PDF?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Stirling-PDF 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.
What are the best alternatives to FusionAuth?
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.
What are the best alternatives to Stirling-PDF?
Top Stirling-PDF alternatives in DevOps are ranked by recent ship velocity. Browse the "Stirling-PDF alternatives" section above for the current picks, or visit /alternatives/stirling-pdf for the full list with editorial commentary on each.