immudb
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
Comparison · DevOps
NebulaGraph vs Heroku
A side-by-side editorial comparison of NebulaGraph and Heroku — release velocity, themes, recent moves, and the top alternatives to consider.
NebulaGraph vs Heroku: at a glance
What is NebulaGraph?
A graph database spending its releases on query-language parity and traversal speed.
NebulaGraph is a distributed graph database whose recent releases read as steady engine work rather than repositioning. The v3.x line has been filling in query-language gaps — shortest-path variants, INNER JOIN, UDFs, richer rounding and JSON handling — while the bulk of each changelog goes to traversal performance, RocksDB tuning, and Raft/leader-balance stability. Nothing in the entries points at a managed service, an AI/vector story, or a pricing change.
What is Heroku?
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.
NebulaGraph vs Heroku: editorial side-by-side
NebulaGraph
5.0DEVOPS
A graph database spending its releases on query-language parity and traversal speed.
◆ Current state
NebulaGraph is a distributed graph database whose recent releases read as steady engine work rather than repositioning. The v3.x line has been filling in query-language gaps — shortest-path variants, INNER JOIN, UDFs, richer rounding and JSON handling — while the bulk of each changelog goes to traversal performance, RocksDB tuning, and Raft/leader-balance stability. Nothing in the entries points at a managed service, an AI/vector story, or a pricing change.
◆ Where it's heading
The arc is convergence on what users of established graph databases already expect: more of Cypher-like expressiveness, fewer sharp edges under concurrency. Successive releases stack pushdown optimizations (LIMIT into SHORTEST PATH, filters into property fetches) and shave latency in the Meta service, which suggests the pressure is coming from large-deployment operators rather than new-feature demand. Stability items — statement-count limits, plan-tree depth caps, leader-lease fixes — are the recurring theme.
◆ Prediction
Expect the next release to continue the same pattern: another batch of MATCH/GO planner optimizations and one or two query-language additions, rather than a new product surface. The entries give no signal about a v4 line or a hosted offering.
Heroku
5.0DEVOPSINFRA · APIS
Runtime bumps fill the changelog; the managed Postgres line is where Heroku actually moves.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to NebulaGraph and Heroku
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 NebulaGraph or Heroku.
Sonic
Sonic is shipping tokenizer control and a dependency diet, two tags at a time.
Postgres Operator
Zalando's Postgres Operator finally shipped v2 — and had to reissue it within a day.
Manticore Search
Manticore tags a GitHub release per commit, so the real news is one entry in five.
pgBackRest
PostgreSQL 19 support lands, and pgBackRest stops letting you run most commands as root.
Vitess
Two patch lines, every release published twice, and no feature news since v24.0.0.
See all NebulaGraph alternatives → · See all Heroku alternatives →
Recent activity from NebulaGraph and Heroku
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoHerokuPostgres 18 GA and Postgres 15 deprecation; Python 3.14.7 and 3.13.15
- 23d agoHeroku.NET SDK updates across the 8.0, 9.0 and 10.0 lines
- 24d agoHerokuPostgres 18 enters beta; sbt 2 supported for Scala apps
- 25d agoHerokuHeroku-22, Heroku-24 and Heroku-26 stacks updated
- 28d agoHerokuPython buildpacks updated to Pipenv 2026.6.2 and uv 0.11.28
- 29d agoHerokuNode.js 26.5.0 now available
- 29d agoNebulaGraphSingle shortest path, INNER JOIN, and LIMIT pushdown land
- 29d agoNebulaGraphFull-text index overhaul plus parallel RocksDB startup
- 1mo agoNebulaGraphUDF support and a parallel traversal executor
- 3y agoNebulaGraphCrash fixes in parameter encoding and list functions
- 3y agoNebulaGraphSession killing and a memory tracker for tighter resource control
- 3y agoNebulaGraphPattern predicates in WHERE and CLEAR SPACE arrive
Frequently asked questions
What is the difference between NebulaGraph and Heroku?
They serve adjacent needs but don't currently overlap on shipped themes. NebulaGraph and Heroku 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.
Is NebulaGraph better than Heroku?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NebulaGraph and Heroku 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.
What are the best alternatives to NebulaGraph?
Top NebulaGraph alternatives in DevOps are ranked by recent ship velocity. Browse the "NebulaGraph alternatives" section above for the current picks, or visit /alternatives/nebulagraph for the full list with editorial commentary on each.
What are the best alternatives to Heroku?
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.