Froxlor
Froxlor's bugfix releases now describe their changes, and most are security fixes.
A side-by-side editorial comparison of Meilisearch and Prometheus — release velocity, themes, recent moves, and the top alternatives to consider.
Meilisearch's newest relevance controls are landing behind its Enterprise Edition.
Meilisearch shipped two stable minors in October. v1.55 lets a search request carry an inline dynamic search rule and report whether that rule's conditions matched, but only on the Enterprise Edition with the dynamicSearchRules experimental flag on, and the notes say Meilisearch Cloud will build a rule-preview UI on it. v1.56 adds a sampledCount option that estimates facet distribution without promising the full facet list, and makes indexing give up early when an embedder can't keep up or stays unavailable, honouring Retry-After headers. Prototype tags in between carry single fixes.
Prometheus 3.16 turns query cost into a setting while its smoothed selectors go stable
Prometheus is working toward 3.16, with rc.2 dated 27 October. The candidate makes Smoothed and Anchored vector selectors stable and always-on, adds experimental query cost estimation with configurable execution limits behind --enable-feature=query-cost, and brings metadata-wal-records to Agent mode. The patch tracks are moving separately: 3.15.1 and 3.13.5 both distrust two root CAs after the eMudhra key compromise and rebuild on patched Go releases.
Meilisearch shipped two stable minors in October. v1.55 lets a search request carry an inline dynamic search rule and report whether that rule's conditions matched, but only on the Enterprise Edition with the dynamicSearchRules experimental flag on, and the notes say Meilisearch Cloud will build a rule-preview UI on it. v1.56 adds a sampledCount option that estimates facet distribution without promising the full facet list, and makes indexing give up early when an embedder can't keep up or stays unavailable, honouring Retry-After headers. Prototype tags in between carry single fixes.
Two lines are running in parallel. The relevance line, dynamic search rules and their preview, is being built as an Enterprise and Cloud feature rather than part of the open core. The scale line is about indexing with external embedders: the v1.56 rate-limit and outage handling only matters to teams pushing thousands of documents through an embedding service. GitHub also shows 1.52, 1.53 and 1.54 patch releases on 1 October that this feed missed, so older lines are still being maintained alongside the new minors.
The Cloud preview UI for dynamic search rules is the stated next consumer of the v1.55 work, so watch for the dynamicSearchRules flag to lose its experimental status. Nothing in these entries says whether the feature will reach the open-source edition.
Prometheus is working toward 3.16, with rc.2 dated 27 October. The candidate makes Smoothed and Anchored vector selectors stable and always-on, adds experimental query cost estimation with configurable execution limits behind --enable-feature=query-cost, and brings metadata-wal-records to Agent mode. The patch tracks are moving separately: 3.15.1 and 3.13.5 both distrust two root CAs after the eMudhra key compromise and rebuild on patched Go releases.
The 3.16 notes spend most of their length on correctness and cost rather than new surface: TSDB out-of-order sample loss, exemplar handling in OTLP and OpenMetrics 2.0, and a long list of parser and memory reductions. Query cost limits are the one addition aimed at operators of shared servers, since a limit on execution is a control that sample counts alone never gave them. Start-timestamp handling also keeps widening, now with a per-query header and counter-reset detection on anchored and smoothed selectors, though it stays behind its feature flag.
A 3.16.0 final is the next move, given this candidate has reached rc.2. Query cost and start-timestamp handling both remain behind flags in these notes, so expect feedback on those before either becomes a default.
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 Meilisearch or Prometheus.
Froxlor's bugfix releases now describe their changes, and most are security fixes.
Nominatim 5.3.3 turns off its debug view by default because it can leak server details.
GraphHopper 11.1 is a security release, and 12.0 prerelease tags have started.
Syncope runs two IAM branches in lockstep, but ships announcements with no change detail.
RaspAP folded its Insiders-only features into the open release, then rebuilt its VPN handling.
Exoscale is filling in cloud basics: VPC, lifecycle rules and cheaper IPv6 load balancing.
See all Meilisearch alternatives → · See all Prometheus alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Meilisearch and Prometheus 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Meilisearch and Prometheus 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.
Top Meilisearch alternatives in DevOps are ranked by recent ship velocity. Browse the "Meilisearch alternatives" section above for the current picks, or visit /alternatives/meilisearch for the full list with editorial commentary on each.
Top Prometheus alternatives in DevOps are ranked by recent ship velocity. Browse the "Prometheus alternatives" section above for the current picks, or visit /alternatives/prometheus for the full list with editorial commentary on each.