Linkerd
Linkerd keeps trading features for fewer operational surprises — 2.20 is tuning, not expansion.
A side-by-side editorial comparison of Prometheus and PlanetScale — release velocity, themes, recent moves, and the top alternatives to consider.
Prometheus has a new LTS baseline, and it tightened how credentials survive a redirect.
Prometheus is running two support lines at once: 3.5.x, which now receives security backports only, and 3.13.x, the Long Term Support release cut on July 1 that has already taken two patch releases. Recent work is dominated by hardening — secrets exposed through the /-/config endpoint in STACKIT and AzureAD paths, snappy decompression limits on remote read and write, and repeated XSS fixes in the UI. Feature work lives in the 3.12 line and earlier: new service-discovery providers, a self-metrics API endpoint, constant-time head-chunk lookup, and experimental PromQL around start timestamps and duration expressions.
PlanetScale is giving Postgres users budgets, guardrails, and a read-only door for agents.
The changelog is dominated by Postgres reaching parity with, and then past, the Vitess side of the platform. Database Traffic Control introduced resource budgets for query traffic, with warning thresholds before enforced budgets bite; storage became configurable at database creation; the vectorscale extension landed; and a new GCP region opened in Eemshaven. Query Insights gained negated search terms across both engines, and an Insights-only variant of the MCP server shipped without query execution tools.
Prometheus is running two support lines at once: 3.5.x, which now receives security backports only, and 3.13.x, the Long Term Support release cut on July 1 that has already taken two patch releases. Recent work is dominated by hardening — secrets exposed through the /-/config endpoint in STACKIT and AzureAD paths, snappy decompression limits on remote read and write, and repeated XSS fixes in the UI. Feature work lives in the 3.12 line and earlier: new service-discovery providers, a self-metrics API endpoint, constant-time head-chunk lookup, and experimental PromQL around start timestamps and duration expressions.
The security work has shifted from patching dependencies to changing default behavior — 3.13.0 stops forwarding Authorization headers, basic auth, bearer tokens, OAuth2, and configured headers when a redirect crosses hosts, which touches scraping, remote read and write, alerting, and service discovery alike. That is the project trading silent convenience for a safe default, and it is the kind of change an LTS is deliberately timed around. Alongside it, the experimental PromQL surface keeps churning: duration functions were renamed inside the RC window, and the start-timestamp family is still gated behind flags.
Expect the 3.13 line to keep taking small patch releases while 3.5.x receives security-only backports toward end of life. The experimental PromQL work — start timestamps and duration expressions — is the most likely candidate to either stabilize or get renamed again in the next minor.
The changelog is dominated by Postgres reaching parity with, and then past, the Vitess side of the platform. Database Traffic Control introduced resource budgets for query traffic, with warning thresholds before enforced budgets bite; storage became configurable at database creation; the vectorscale extension landed; and a new GCP region opened in Eemshaven. Query Insights gained negated search terms across both engines, and an Insights-only variant of the MCP server shipped without query execution tools.
PlanetScale is building the operational controls that decide whether a managed database is safe to hand to a large team. Traffic budgets, warning thresholds, storage checks before deploy requests and connection-level guardrails all address the same failure mode: one workload consuming the cluster. The Insights-only MCP variant applies that instinct to agents — give them observability and schema recommendations, withhold the ability to execute queries.
Expect Traffic Control to gain more granularity and for the Postgres offering to keep closing extension and region gaps. The scoped MCP server suggests further work on what agents are allowed to do rather than simply exposing more of the platform to them.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with Prometheus.
Linkerd keeps trading features for fewer operational surprises — 2.20 is tuning, not expansion.
Vercel is building the durable-execution layer — and just learned its model catalog isn't its own.
Supabase is closing its most-exploited default: tables stop being public unless you say so.
Auth0 is rebuilding itself as the identity layer between B2B apps, their customers, and AI agents.
Sanity is spending this month on the surfaces around the editor, not the editor itself.
GitHub is turning supply-chain defense into enforcement while Copilot grows its governance layer.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with PlanetScale.
Expo shut down its own coding agent and kept the MCP server — it wants to be the substrate.
Clerk is building auth for machines: API keys, a CLI agents can drive, per-verification pricing.
Airbyte 2.0 made the pipeline run both ways: data activation turns the warehouse into a source.
Mixpanel is pushing analytics out of its own tab — into Postgres, Slack, and now Glean's assistant.
Groq is climbing off raw inference: hosted tools and MCP connectors now sit above the chips.
Windsurf is being rebuilt as Devin's front end — the IDE now ships the agent, the CLI, and the reviewer.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Prometheus is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. Prometheus is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.
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.
Top PlanetScale alternatives in DevOps are ranked by recent ship velocity. Browse the "PlanetScale alternatives" section above for the current picks, or visit /alternatives/planetscale for the full list with editorial commentary on each.