← Back to home
Comparison · DevOps

Nominatim vs SimpleSAMLphp

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

Nominatim vs SimpleSAMLphp: at a glance

FeatureNominatimSimpleSAMLphp
SectorDevOpsDevOps
Velocity score0.05.0
Sparks · 30d00
Top themesgeocoding, openstreetmap, python-package, postcodessaml, identity-federation, security-patches, maintenance-branches
Last editorial update2h ago4h ago
WebsiteVisit →Visit →

What is Nominatim?

The geocoder finished becoming a Python package, then got back to matching addresses

Nominatim releases a minor version every few months with fast hotfixes when an update path breaks. The 4.5-to-5.0 span was structural — becoming a pip-installable Python package, then removing the PHP frontend, bundled osm2pgsql and cmake scripts outright. Since then the work has returned to geocoding quality: a pattern-based postcode parser, building entrances in results, a restructured forward query parser, and separate processing tables for postcodes, interpolations and associatedStreet relations.

Read the full Nominatim trajectory →

What is SimpleSAMLphp?

SimpleSAMLphp advances two maintenance branches in lockstep, security patches first.

SimpleSAMLphp is maintaining the 2.4 and 2.5 lines in parallel and patching both from the same fixes. Six releases since late May split into two security releases — the 2.4.6/2.5.1 pair on 29 May and 2.5.3 on 10 August — and four bugfix releases. Release bodies carry only download links and SHA256 checksums, so the substance sits in the linked changelog rather than the feed itself.

Read the full SimpleSAMLphp trajectory →

Nominatim vs SimpleSAMLphp: editorial side-by-side

N
Nominatim
DEVOPS
0.0

The geocoder finished becoming a Python package, then got back to matching addresses

◆ Current state

Nominatim releases a minor version every few months with fast hotfixes when an update path breaks. The 4.5-to-5.0 span was structural — becoming a pip-installable Python package, then removing the PHP frontend, bundled osm2pgsql and cmake scripts outright. Since then the work has returned to geocoding quality: a pattern-based postcode parser, building entrances in results, a restructured forward query parser, and separate processing tables for postcodes, interpolations and associatedStreet relations.

◆ Where it's heading

With the packaging migration finished, the project is optimizing the two things operators actually feel — how fast a search resolves and whether continuous OSM updates keep flowing. The 5.3.0 split into dedicated processing tables was explicitly about making updates faster and more reliable, and the two hotfixes that followed within a fortnight show how tightly that path is watched. Query-side work is trending toward recognizing input that is not in the database at all, as the postcode parser does.

◆ Prediction

Expect continued query-parser and update-pipeline optimization rather than new output types, since that is where every release since 5.0.0 has concentrated.

S5.0

SimpleSAMLphp advances two maintenance branches in lockstep, security patches first.

◆ Current state

SimpleSAMLphp is maintaining the 2.4 and 2.5 lines in parallel and patching both from the same fixes. Six releases since late May split into two security releases — the 2.4.6/2.5.1 pair on 29 May and 2.5.3 on 10 August — and four bugfix releases. Release bodies carry only download links and SHA256 checksums, so the substance sits in the linked changelog rather than the feed itself.

◆ Where it's heading

The dual-branch discipline is the story: every advisory lands twice, once per supported line, which is what a SAML library embedded in long-lived identity deployments has to do for operators who cannot jump minor versions on demand. The May advisories touched HTTP-Artifact resolution and SP-Proxy setups bridging IdPs of differing trust levels — federation's sharp edges rather than everyday login flows. No feature work is visible in this window; 2.5.0 in March was the last minor.

◆ Prediction

Expect both branches to keep advancing together, with 2.4 receiving anything 2.5 gets on the security side. The feed offers no signal on when a 2.6 line might open.

Alternatives to Nominatim 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 Nominatim or SimpleSAMLphp.

See all Nominatim alternatives → · See all SimpleSAMLphp alternatives →

Recent activity from Nominatim and SimpleSAMLphp

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

  1. 8h agoSimpleSAMLphpSecurity release on the 2.5 branch
  2. 19h agoSimpleSAMLphpBugfix release on the 2.4 maintenance branch
  3. 1mo agoSimpleSAMLphpBugfix release on the 2.4 branch
  4. 2mo agoSimpleSAMLphpBugfix release on the 2.5 branch
  5. 2mo agoSimpleSAMLphpBugfix release on the 2.4 branch
  6. 2mo agoSimpleSAMLphpThree advisories fixed across HTTP-Artifact and SP-Proxy paths
  7. 3mo agoNominatim5.3.2 fixes a non-null constraint error during updates
  8. 4mo agoNominatim5.3.1 restores usable update speed for associatedStreet relations
  9. 4mo agoNominatim5.3.0 gives postcodes and interpolations their own processing tables
  10. 9mo agoNominatim5.2.0 returns building entrances and cuts SQL round-trips
  11. 1y agoNominatim5.1.0 recognizes postcodes that aren't in the OSM data
  12. 1y agoNominatim5.0.0 removes the PHP frontend, bundled osm2pgsql and cmake

Frequently asked questions

What is the difference between Nominatim and SimpleSAMLphp?

They serve adjacent needs but don't currently overlap on shipped themes. SimpleSAMLphp is currently shipping more aggressively (velocity 5.0 vs 0.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.

Is Nominatim 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 0.0), 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 Nominatim?

Top Nominatim alternatives in DevOps are ranked by recent ship velocity. Browse the "Nominatim alternatives" section above for the current picks, or visit /alternatives/nominatim 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.