Elasticsearch
Elastic moves to 9.5 and takes cross-project search GA on Serverless.
A side-by-side editorial comparison of AWS and Jaeger — release velocity, themes, recent moves, and the top alternatives to consider.
AWS brings its OpenAI models into GovCloud on the same controls as every other Bedrock model.
The late-October run is led by GovCloud. OpenAI GPT-5.6 (Terra and Luna) reaches the bedrock-runtime endpoint there with Cross-Region Inference, Daybreak Red arrives in GovCloud (US-East) for enrolled customers, and Kiro web search lands in GovCloud with admin off-switches. The rest is operator detail: CloudFront viewer ISP and post-quantum TLS headers, optional minor version upgrades on RDS for Oracle options, and draft saving in Amazon Connect Customer.
Jaeger folds its MCP server into the query service and drops Elasticsearch 6
Jaeger's 2.x line is releasing roughly monthly, and two threads dominate. The storage layer is being modernised and pruned — Elasticsearch 6 support removed, rotation and index-cleaner feature gates promoted to beta, ClickHouse gaining TLS and analyzer fixes, configurable max trace duration. The other thread is the query surface: a lightweight trace-summaries endpoint added in 2.19 then given a native Elasticsearch implementation in 2.20, and the MCP extension merged into the query extension.
The late-October run is led by GovCloud. OpenAI GPT-5.6 (Terra and Luna) reaches the bedrock-runtime endpoint there with Cross-Region Inference, Daybreak Red arrives in GovCloud (US-East) for enrolled customers, and Kiro web search lands in GovCloud with admin off-switches. The rest is operator detail: CloudFront viewer ISP and post-quantum TLS headers, optional minor version upgrades on RDS for Oracle options, and draft saving in Amazon Connect Customer.
The through-line is making third-party models behave like native AWS services. On bedrock-runtime, OpenAI usage shows up in Bedrock invocation logs, CloudWatch metrics and Cost Explorer, which is what regulated buyers need before approving a model. The same pattern shows on the agent side, where Kiro's web tools ship with organization-level and per-agent controls.
Expect more GovCloud parity notices for models and agent tools already available in commercial regions. The entries do not show which model is next.
Jaeger's 2.x line is releasing roughly monthly, and two threads dominate. The storage layer is being modernised and pruned — Elasticsearch 6 support removed, rotation and index-cleaner feature gates promoted to beta, ClickHouse gaining TLS and analyzer fixes, configurable max trace duration. The other thread is the query surface: a lightweight trace-summaries endpoint added in 2.19 then given a native Elasticsearch implementation in 2.20, and the MCP extension merged into the query extension.
Jaeger is treating machine consumption of traces as a first-class query path rather than an add-on. Merging jaegermcp into jaegerquery means the MCP surface ships wherever query ships, and trace summaries give both the UI and any agent a cheap way to scan results before pulling full traces. On storage, the direction is fewer supported backends maintained better, with ClickHouse steadily gaining parity.
Expect the trace-summaries path to become the default for search across storage backends, and further ClickHouse feature work as the Elasticsearch surface is trimmed rather than extended.
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 AWS or Jaeger.
Elastic moves to 9.5 and takes cross-project search GA on Serverless.
Dub adds AI application screening as its partner program controls keep getting finer.
LogRocket's tracked feed is still its editorial blog, so product moves stay out of view.
Bitbucket fills out Agentic Pipelines with test agents, MCP access and Merge Queue APIs.
GitLab Orbit goes GA, betting that agent quality depends on lifecycle context, not on the model.
Jackett ships a daily build to keep hundreds of torrent indexers working as sites move and close.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. AWS is currently shipping more aggressively (velocity 5.0 vs 3.8), 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. AWS is currently shipping more aggressively (velocity 5.0 vs 3.8), 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 AWS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "AWS alternatives" section above for the current picks, or visit /alternatives/aws for the full list with editorial commentary on each.
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.