GitHub
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
Comparison · DevOps
GeoServer vs Manticore Search
A side-by-side editorial comparison of GeoServer and Manticore Search — release velocity, themes, recent moves, and the top alternatives to consider.
GeoServer vs Manticore Search: at a glance
What is GeoServer?
GeoServer patches three branches at once, with the new work reserved for the 3.0 line
Three releases landed within about an hour of each other — 2.27.6, 2.28.5 and 3.0.1 — the coordinated multi-branch pattern this project uses for maintenance. The shared payload is a set of security-adjacent fixes: a GeoFence SQL query missing its spatial filter when only CLIP applies, wrong CRS axis order when clipping WFS 2.0.0 features, and the XXE vulnerability in features-templating backported to the oldest branch. Only 3.0.1 carries new capability: a Keycloak role service and security-aware GeoWebCache tile caching.
What is Manticore Search?
Manticore 31.0.7 undoes a 2x COUNT(DISTINCT) slowdown its own collation fix caused.
Manticore Search's 31.x tags so far are fixes rather than features. 31.0.3 and 31.0.4 were CI and packaging work; 31.0.7 restores string COUNT(DISTINCT) speed after the 29.18.5 collation fix made it 2x slower (1.1 s to 2.4 s on the logs10m benchmark) by calling tolower() per byte. A lookup table replaces the call without changing hash values, so secondary indexes and histograms stay compatible.
GeoServer vs Manticore Search: editorial side-by-side
GeoServer
5.0DEVOPS
GeoServer patches three branches at once, with the new work reserved for the 3.0 line
◆ Current state
Three releases landed within about an hour of each other — 2.27.6, 2.28.5 and 3.0.1 — the coordinated multi-branch pattern this project uses for maintenance. The shared payload is a set of security-adjacent fixes: a GeoFence SQL query missing its spatial filter when only CLIP applies, wrong CRS axis order when clipping WFS 2.0.0 features, and the XXE vulnerability in features-templating backported to the oldest branch. Only 3.0.1 carries new capability: a Keycloak role service and security-aware GeoWebCache tile caching.
◆ Where it's heading
The branch split is doing what it is supposed to. The 2.x lines get fixes and nothing else, while the 3.0 line — which broke the monolith into extensions — is where authentication and cache-security work now lands. The recurring theme across all three is access control at the data layer: GeoFence filtering, secured feature sources, and now tile caching that respects security rather than serving from an unaware cache.
◆ Prediction
Expect the next coordinated round to follow the same shape, with 3.0.2 taking further security-aware caching and identity-provider work while the 2.x branches receive only the shared fixes.
Manticore Search
5.0DEVOPS
Manticore 31.0.7 undoes a 2x COUNT(DISTINCT) slowdown its own collation fix caused.
◆ Current state
Manticore Search's 31.x tags so far are fixes rather than features. 31.0.3 and 31.0.4 were CI and packaging work; 31.0.7 restores string COUNT(DISTINCT) speed after the 29.18.5 collation fix made it 2x slower (1.1 s to 2.4 s on the logs10m benchmark) by calling tolower() per byte. A lookup table replaces the call without changing hash values, so secondary indexes and histograms stay compatible.
◆ Where it's heading
October has been correctness work on string handling (range filters, collation-aware COUNT(DISTINCT)) followed by fixing the performance cost of those fixes. The 31.x line still appears in the feed without notes on what features justified the major version.
◆ Prediction
Expect more 31.0.x patches in this vein. What new capability defines 31.x remains unclear from these entries.
Alternatives to GeoServer and Manticore Search
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 GeoServer or Manticore Search.
CodeRabbit
CodeRabbit moves its review status to a GitHub check run and keeps Deep Scan coverage fresh.
Apache Arrow Rust
Arrow Rust 60.1.0 ships, redacting Parquet encryption keys and adding read-ahead planning.
Zed
Zed 1.26 adds Pyrefly for Python and debugs WebAssembly from the JavaScript debugger.
Sanity
Sanity's MCP server now advertises itself to agents through a server card and llms.txt.
Kubernetes
Kubernetes moves conformance from the cluster to the workloads running on it.
See all GeoServer alternatives → · See all Manticore Search alternatives →
Recent activity from GeoServer and Manticore Search
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoManticore Search31.0.7: string COUNT(DISTINCT) 2x slowdown fixed
- 5d agoManticore Search31.0.4: CI fix for bundled Debian dependencies
- 5d agoManticore Search31.0.3: Test Kit pinned to Executor 1.4.6
- 8d agoManticore Search29.18.7: Manticore Buddy sidecar bumped to 4.4.8
- 9d agoManticore Search29.18.6: crash dumps now name the operation and table
- 9d agoManticore SearchFix: COUNT(DISTINCT) on strings now respects session collation
- 2mo agoGeoServer2.27.6 backports the XXE fix and workspace style persistence
- 2mo agoGeoServer2.28.5 fixes GeoFence spatial filtering and WFS clipping axis order
- 2mo agoGeoServer3.0.1 adds a Keycloak role service and security-aware tile caching
- 4mo agoGeoServerGeoServer 3.0 splits the core into extensions and drops H2 ⚡
- 5mo agoGeoServer2.28.4 fixes an XXE vulnerability and adds per-version service toggles
- 7mo agoGeoServer2.28.2 adds STAC security and REST ingestion for VectorMosaic
Frequently asked questions
What is the difference between GeoServer and Manticore Search?
They serve adjacent needs but don't currently overlap on shipped themes. GeoServer and Manticore Search are shipping at a similar cadence (velocity 5.0 vs 5.0, 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.
Is GeoServer better than Manticore Search?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. GeoServer and Manticore Search are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
What are the best alternatives to GeoServer?
Top GeoServer alternatives in DevOps are ranked by recent ship velocity. Browse the "GeoServer alternatives" section above for the current picks, or visit /alternatives/geoserver for the full list with editorial commentary on each.
What are the best alternatives to Manticore Search?
Top Manticore Search alternatives in DevOps are ranked by recent ship velocity. Browse the "Manticore Search alternatives" section above for the current picks, or visit /alternatives/manticoresearch for the full list with editorial commentary on each.