Scalar
Scalar is testing demand for hosting from inside localhost
A side-by-side editorial comparison of Jaeger and Nautobot — release velocity, themes, recent moves, and the top alternatives to consider.
Jaeger's query service learns to search individual spans, not just whole traces.
Jaeger 2.21 and 2.22 extend the 2.x storage and query rework. ClickHouse storage moved to a stable feature gate in 2.21, and the release removed v1 HTTP endpoints the UI no longer calls. In 2.22 the query service gains FindSpans with RFC 0014 pagination, Elasticsearch span search, and structured filters promoted to beta, while native Elasticsearch trace summaries go stable.
Nautobot's October releases are a permissions audit: objects users can't view kept leaking.
Nautobot's 3.2 and 2.4 lines have shipped same-day security releases every two weeks since September. v3.2.8 and v2.4.45 lead with stored XSS fixes and a long run of cases where jobs, imports and REST related-object handling accepted or revealed objects the user could not view, including other users' API tokens. v3.2.7 and v2.4.44 closed a Jinja2 sandbox escape and added timeouts for regular-expression evaluation. v3.2.6 moved SSO login to HTTP POST, breaking bookmarked SSO URLs.
Jaeger 2.21 and 2.22 extend the 2.x storage and query rework. ClickHouse storage moved to a stable feature gate in 2.21, and the release removed v1 HTTP endpoints the UI no longer calls. In 2.22 the query service gains FindSpans with RFC 0014 pagination, Elasticsearch span search, and structured filters promoted to beta, while native Elasticsearch trace summaries go stable.
The earlier trace-summaries work made search cheaper; span search changes what can be asked. Pagination and structured filters give both the UI and MCP clients a way to query without pulling whole traces. MCP keeps getting practical limits and input checks, and search_traces no longer needs a service name on backends that declare support for that.
Expect span search to spread beyond Elasticsearch and memory storage, and structured filters to move from beta to stable as other gates have. Further removal of v1 surface is likely, since 2.21 already started it.
Nautobot's 3.2 and 2.4 lines have shipped same-day security releases every two weeks since September. v3.2.8 and v2.4.45 lead with stored XSS fixes and a long run of cases where jobs, imports and REST related-object handling accepted or revealed objects the user could not view, including other users' API tokens. v3.2.7 and v2.4.44 closed a Jinja2 sandbox escape and added timeouts for regular-expression evaluation. v3.2.6 moved SSO login to HTTP POST, breaking bookmarked SSO URLs.
Permissions were already the sustained theme in August, and the work has moved from Saved Views to the general paths every App relies on. New helpers such as restrict_queryset() and mock_wsgi_request() in the apps API, plus the fixes in WritableNestedSerializer, hand the same checks to App developers. The number of advisories per release points to a systematic review rather than a single report.
Expect App authors to be pointed at those helpers, and further advisories in the same object-visibility class in the next paired releases. v3.2.8's warning that Pillow 13 cannot run on Python 3.10 makes that version's support the likely next removal.
Other Infra & APIs 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 Jaeger or Nautobot.
Scalar is testing demand for hosting from inside localhost
Incus 7.6 fixes 18 security issues, eight critical, and adds SR-IOV NIC live migration
DNSimple's Erlang DNS stack now handles 14% more queries per second, with no C involved
Doppler adds keyless syncs and agent-facing secrets as on-prem settles in
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
Algolia's Agent Studio opens to outside agents and starts grading its own before they ship
See all Jaeger alternatives → · See all Nautobot alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Nautobot 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Nautobot 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 Infra & APIs products to evaluate alongside.
Top Jaeger alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Jaeger alternatives" section above for the current picks, or visit /alternatives/jaeger for the full list with editorial commentary on each.
Top Nautobot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Nautobot alternatives" section above for the current picks, or visit /alternatives/nautobot for the full list with editorial commentary on each.