QuestDB
QuestDB 10.0 collapses ingest and egress into one binary protocol, then aims at agent-run notebooks.
A side-by-side editorial comparison of Convex and immudb — release velocity, themes, recent moves, and the top alternatives to consider.
Convex raised $57M on the argument that agents need a backend built for them.
The feed is thin on releases and heavy on company milestones. A $57M Series B led by Insight Partners is the newest item, pitched around developers and their agents writing software together and needing a backend that keeps up. The substantive product news remains April's Convex for Enterprise, which added the compliance and scale posture the platform previously lacked; since then the feed carries a conference announcement and open-source recaps rather than shipped capability.
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(*).
The feed is thin on releases and heavy on company milestones. A $57M Series B led by Insight Partners is the newest item, pitched around developers and their agents writing software together and needing a backend that keeps up. The substantive product news remains April's Convex for Enterprise, which added the compliance and scale posture the platform previously lacked; since then the feed carries a conference announcement and open-source recaps rather than shipped capability.
Convex is funding and positioning ahead of shipping. The enterprise release established the upmarket motion and the funding narrative attaches it to agent-written code, but nothing in the visible window shows the agent-facing product surface that framing implies. Whether that framing is real or aspirational is not something this feed answers yet.
With the round announced around agent workloads, the next substantive release is most likely on that surface, though the entries here give no detail on what form it takes.
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.
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 Convex or immudb.
QuestDB 10.0 collapses ingest and egress into one binary protocol, then aims at agent-run notebooks.
Angular's 22.x prerelease train is grinding through correctness, not shipping new features.
SurveyJS keeps a notes-free v1 line alive while v3 grinds through theming in beta.
Auth0 is making AI agents first-class identities, not borrowed user accounts
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.
See all Convex alternatives → · See all immudb alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Convex is currently shipping more aggressively (velocity 2.5 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. Convex is currently shipping more aggressively (velocity 2.5 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 Convex alternatives in DevOps are ranked by recent ship velocity. Browse the "Convex alternatives" section above for the current picks, or visit /alternatives/convex for the full list with editorial commentary on each.
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.