Sanity
Sanity is making the fastest path into its platform an agent typing a CLI command.
A side-by-side editorial comparison of Heroku and Prometheus — release velocity, themes, recent moves, and the top alternatives to consider.
Runtime bumps fill the changelog; the managed Postgres line is where Heroku actually moves.
Day to day, Heroku's changelog is language-runtime upkeep: Python, Node, Ruby, Go, PHP, JRuby and .NET point releases, buildpack refreshes for Pipenv and uv, and periodic rebuilds of the Heroku-22, Heroku-24 and Heroku-26 stacks now maintained in parallel. The exception is the managed database. Postgres 18 entered beta on 14 July and reached general availability on 4 August, and Heroku deprecated Postgres 15 on the same day.
Two branches running in parallel: 3.13 LTS on security patches, 3.14 promoting experiments to stable.
Prometheus is maintaining a 3.13 LTS line and a 3.5 line with security-only releases while 3.14 develops. The LTS patches have been narrow and serious — a head-chunk cache returning samples from the wrong chunk after truncation, a SIGBUS crash when the active query tracker's disk fills, plus CVE-driven dependency bumps in golang.org/x/text and gRPC. The 3.14.0 release candidate is where the feature work sits: duration expressions on by default, first_over_time promoted out of the experimental flag, and Oracle Cloud Infrastructure service discovery added.
Day to day, Heroku's changelog is language-runtime upkeep: Python, Node, Ruby, Go, PHP, JRuby and .NET point releases, buildpack refreshes for Pipenv and uv, and periodic rebuilds of the Heroku-22, Heroku-24 and Heroku-26 stacks now maintained in parallel. The exception is the managed database. Postgres 18 entered beta on 14 July and reached general availability on 4 August, and Heroku deprecated Postgres 15 on the same day.
The platform is running two clocks at once. One is a near-daily maintenance cadence that keeps supported runtimes current and rarely changes behaviour. The other is a deliberate, publicly staged lifecycle for the data services, where a major version is walked from beta to GA and the version three releases behind is retired in the same announcement. Kafka is on the same track, with 2.8 and 3.7 deprecations and a revised version-support policy posted in late July.
Given that Postgres 15's deprecation was announced alongside 18's general availability, the next concrete step is a published end-of-life date and forced-upgrade window for Postgres 15. The runtime bumps will continue at their current weekly rhythm.
Prometheus is maintaining a 3.13 LTS line and a 3.5 line with security-only releases while 3.14 develops. The LTS patches have been narrow and serious — a head-chunk cache returning samples from the wrong chunk after truncation, a SIGBUS crash when the active query tracker's disk fills, plus CVE-driven dependency bumps in golang.org/x/text and gRPC. The 3.14.0 release candidate is where the feature work sits: duration expressions on by default, first_over_time promoted out of the experimental flag, and Oracle Cloud Infrastructure service discovery added.
PromQL is the centre of gravity. Features enter behind promql-experimental-functions or a dedicated flag, get renamed once while experimental (min/max to min_of/max_of), then graduate — first_over_time and duration expressions are the current graduates, start_timestamp the next candidate behind use-start-timestamps. The API is simultaneously being tightened, with the stats parameter deprecated ahead of rejection in the next major and credential forwarding across redirects already removed in 3.13. Service discovery keeps absorbing clouds as their APIs change, OCI added and a Hetzner label dropped in the same release.
A 3.14.0 final should follow the release candidate within weeks, carrying the duration-expression and first_over_time promotions with it.
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 Heroku or Prometheus.
Sanity is making the fastest path into its platform an agent typing a CLI command.
A week of walking back v1.52.0 while the sharding work ships on a parallel tag
The blog has become a teaching channel, with the real releases arriving as Gateway API and deprecation notices.
Vitest 5 reaches RC after a beta line that reworked config, mocking defaults, and the browser runner.
A dependency-bump treadmill interrupted by the first real accessibility push in months.
Jenkins is shrinking its own war file and rebuilding its UI, one weekly release at a time
See all Heroku 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. Heroku 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. Heroku 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 Heroku alternatives in DevOps are ranked by recent ship velocity. Browse the "Heroku alternatives" section above for the current picks, or visit /alternatives/heroku 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.