← Back to home
Comparison · DevOps

FusionAuth vs SimpleSAMLphp

A side-by-side editorial comparison of FusionAuth and SimpleSAMLphp — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:identity

FusionAuth vs SimpleSAMLphp: at a glance

FeatureFusionAuthSimpleSAMLphp
SectorDevOpsDevOps
Velocity score2.55.0
Sparks · 30d00
Top themesidentity, oauth, self-hosted, breaking-changessaml, identity, security-releases, maintenance
Last editorial update14h ago8d ago
WebsiteVisit →Visit →

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.

Read the full FusionAuth trajectory →

What is SimpleSAMLphp?

Two maintenance branches, patched in lockstep, with release notes that say nothing but a checksum.

SimpleSAMLphp is running parallel 2.4 and 2.5 maintenance branches and patching both on the same day whenever a fix lands. The August releases are a coordinated security drop across the 2.5 line plus a 2.4 bugfix a day earlier. Release bodies carry no changelog text at all — just a download link, upgrade-notes pointer, and SHA256 checksums, so the feed tells operators when to patch but never what changed.

Read the full SimpleSAMLphp trajectory →

FusionAuth vs SimpleSAMLphp: editorial side-by-side

F2.5

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.

S5.0

Two maintenance branches, patched in lockstep, with release notes that say nothing but a checksum.

◆ Current state

SimpleSAMLphp is running parallel 2.4 and 2.5 maintenance branches and patching both on the same day whenever a fix lands. The August releases are a coordinated security drop across the 2.5 line plus a 2.4 bugfix a day earlier. Release bodies carry no changelog text at all — just a download link, upgrade-notes pointer, and SHA256 checksums, so the feed tells operators when to patch but never what changed.

◆ Where it's heading

This is pure maintenance cadence, not product development. The pattern across the last ten releases is consistent: security issues get simultaneous twin tags on both supported branches, everything else lands as branch-local bugfix points. The only release in the window that documented its own content was v2.4.6/v2.5.1 in May, which listed three GHSA advisories.

◆ Prediction

Expect the next tags to continue the twin-branch pattern — a paired 2.4.x and 2.5.x whenever an advisory lands, with content again deferred to the external changelog.

Alternatives to FusionAuth and SimpleSAMLphp

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 SimpleSAMLphp.

See all FusionAuth alternatives → · See all SimpleSAMLphp alternatives →

Recent activity from FusionAuth and SimpleSAMLphp

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 8d agoSimpleSAMLphpSecurity release on the 2.5 branch (re-tagged)
  2. 9d agoSimpleSAMLphpSecurity release on the 2.5 branch
  3. 9d agoSimpleSAMLphpBugfix release on the 2.4 maintenance branch
  4. 15d agoFusionAuthFusionAuth 1.69.0 ships with no published release notes
  5. 1mo agoSimpleSAMLphpBugfix release on the 2.4 maintenance branch
  6. 1mo agoFusionAuthFusionAuth 1.68.0 (Intelligent Kamfa), notes not published
  7. 2mo agoFusionAuthFusionAuth 1.67.1 patch, no notes published
  8. 2mo agoSimpleSAMLphpBugfix release on the 2.5 branch
  9. 2mo agoSimpleSAMLphpBugfix release on the 2.4 maintenance branch
  10. 2mo agoFusionAuthRFC 8707 OAuth resource scoping for tokens
  11. 3mo agoFusionAuthWebhook endpoints now require global API keys (breaking)
  12. 3mo agoFusionAuthBreaking: IdP linking strategy locked, tenant-key access narrowed

Frequently asked questions

What is the difference between FusionAuth and SimpleSAMLphp?

Both compete on the same themes — identity — within DevOps. SimpleSAMLphp 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 SimpleSAMLphp?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. SimpleSAMLphp 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 SimpleSAMLphp?

Top SimpleSAMLphp alternatives in DevOps are ranked by recent ship velocity. Browse the "SimpleSAMLphp alternatives" section above for the current picks, or visit /alternatives/simplesamlphp for the full list with editorial commentary on each.