Sonic
Sonic is shipping tokenizer control and a dependency diet, two tags at a time.
A side-by-side editorial comparison of immudb and GravityView — release velocity, themes, recent moves, and the top alternatives to consider.
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
immudb is a tamper-evident database that recently taught itself the PostgreSQL wire protocol in earnest: pg_catalog and information_schema resolvers, PostgreSQL compatibility functions, SHOW emulation, and subquery support, enough for Django, SQLAlchemy, GORM, and ActiveRecord to introspect it. Its own verification primitives — state, row and transaction proofs, history — are now callable as SQL functions over that same wire. The follow-on 1.11.1 release adds opt-in value-level audit verification and index-only COUNT(*).
Weekly launch logs, two steady threads: accessibility in the View editor and MCP surfaces for agents.
GravityKit ships a roundup roughly every week covering GravityView and its satellite add-ons — DataTables, Maps, GravityCalendar, GravityCharts, GravityImport. GravityView 3.0 in mid-June was the anchor release: the Vantage theme, frontend bulk actions, AI-assisted View creation, and native page builder support. Since then the work has been incremental and broad rather than deep — Multiple Forms gaining union support to combine entries from several forms in one View, rich text inline editing in GravityEdit, drag-to-copy in the View editor, row headers for screen readers, 3D map starting views. Running underneath all of it is a compatibility tax: Gravity Forms 3.0 and now WordPress 7.0.
immudb is a tamper-evident database that recently taught itself the PostgreSQL wire protocol in earnest: pg_catalog and information_schema resolvers, PostgreSQL compatibility functions, SHOW emulation, and subquery support, enough for Django, SQLAlchemy, GORM, and ActiveRecord to introspect it. Its own verification primitives — state, row and transaction proofs, history — are now callable as SQL functions over that same wire. The follow-on 1.11.1 release adds opt-in value-level audit verification and index-only COUNT(*).
The direction is unmistakable: stop asking developers to adopt a bespoke API and instead present as Postgres with integrity guarantees attached. Every recent addition either removes an adoption barrier (ORM introspection, compatibility functions) or makes the integrity story operationally usable (structured audit logging, SHA-256 value re-verification during audit cycles). Sitting against that is a v2.0.0 release candidate announcing a page-based indexing redesign and multi-ledger storage that has not reached GA while the 1.11 line kept shipping — the rearchitecture is announced, not delivered.
Expect continued PostgreSQL surface-filling on the 1.11 line, since each compatibility gap is the concrete thing blocking an ORM. What the entries do not support is a confident call on v2: the RC has been outpaced by 1.11 releases, and nothing in the changelogs indicates whether it is being finished or quietly shelved.
GravityKit ships a roundup roughly every week covering GravityView and its satellite add-ons — DataTables, Maps, GravityCalendar, GravityCharts, GravityImport. GravityView 3.0 in mid-June was the anchor release: the Vantage theme, frontend bulk actions, AI-assisted View creation, and native page builder support. Since then the work has been incremental and broad rather than deep — Multiple Forms gaining union support to combine entries from several forms in one View, rich text inline editing in GravityEdit, drag-to-copy in the View editor, row headers for screen readers, 3D map starting views. Running underneath all of it is a compatibility tax: Gravity Forms 3.0 and now WordPress 7.0.
Two threads run consistently through the weekly logs. Accessibility is being treated as product work rather than a checkbox — screen-reader row headers, editor a11y upgrades — which matters for the public-sector and education sites that use Gravity Forms data displays. The other is MCP: GravityKit MCP and Block MCP keep gaining surface, with Block MCP now able to edit theme templates safely, so an agent can build and modify the presentation layer, not just read data. A third, quieter shift is visible in the data model: unions across forms mean a View is no longer bound to a single form as its source.
Expect the MCP surfaces to keep widening toward the operations an admin does by hand — View configuration and layout edits — while the weekly cadence absorbs WordPress 7.0 compatibility across the add-on suite the way it has been absorbing Gravity Forms 3.0.
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 immudb or GravityView.
Sonic is shipping tokenizer control and a dependency diet, two tags at a time.
Zalando's Postgres Operator finally shipped v2 — and had to reissue it within a day.
A graph database spending its releases on query-language parity and traversal speed.
Manticore tags a GitHub release per commit, so the real news is one entry in five.
PostgreSQL 19 support lands, and pgBackRest stops letting you run most commands as root.
Two patch lines, every release published twice, and no feature news since v24.0.0.
See all immudb alternatives → · See all GravityView alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. GravityView is currently shipping more aggressively (velocity 5.0 vs 0.0), 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. GravityView is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 immudb alternatives in DevOps are ranked by recent ship velocity. Browse the "immudb alternatives" section above for the current picks, or visit /alternatives/immudb for the full list with editorial commentary on each.
Top GravityView alternatives in DevOps are ranked by recent ship velocity. Browse the "GravityView alternatives" section above for the current picks, or visit /alternatives/gravityview for the full list with editorial commentary on each.