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 immudb and Auth0 — 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(*).
Auth0 is making AI agents first-class identities, not borrowed user accounts
Three of the six most recent releases are about who or what is acting on whose behalf. Agents as Principal gives every agent its own identifier, credentials, and audit trail instead of letting it hide behind a shared client; Token Vault Privileged Worker lets an unattended agent pull a user's third-party tokens with no active session; Session Delegation extends Custom Token Exchange from API calls to full browser sessions with an RFC 8693 act claim. The rest of the window is B2B plumbing — org-scoped roles, Google Workspace group sync going GA, Enterprise Connect — plus dashboard search work.
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.
Three of the six most recent releases are about who or what is acting on whose behalf. Agents as Principal gives every agent its own identifier, credentials, and audit trail instead of letting it hide behind a shared client; Token Vault Privileged Worker lets an unattended agent pull a user's third-party tokens with no active session; Session Delegation extends Custom Token Exchange from API calls to full browser sessions with an RFC 8693 act claim. The rest of the window is B2B plumbing — org-scoped roles, Google Workspace group sync going GA, Enterprise Connect — plus dashboard search work.
Auth0 is building out a delegation model where the acting party and the subject stay separately identifiable through every hop, and then applying it to agents, support staff, and background workers in turn. Most of this ships as Early Access gated behind an account team, which suggests the primitives are landing faster than the productization. Alongside it, Enterprise Connect points at a second motion: sitting on top of a customer's existing SAML or OIDC server rather than replacing it.
Expect the Early Access agent features to consolidate into a single documented agent-identity surface and start moving toward GA, with the delegation chain extended to more token types.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with 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.
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.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with Auth0.
Eight CVEs in one August batch — ClamAV's parser surface is the whole story.
Infisical is growing past secrets management into PAM, PKI and an agent credential proxy.
WorkOS is making agents first-class principals and taking custody of the tokens they act with.
Render swaps static keys for federated identity and opens its control plane to coding agents.
Tailnets become API-provisioned resources while Tailscale hardens SSH and thins the control plane.
Retool is turning its app builder into a branched, multi-threaded agent workspace.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Auth0 is currently shipping more aggressively (velocity 10.0 vs 0.0), with 2 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. Auth0 is currently shipping more aggressively (velocity 10.0 vs 0.0), with 2 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 Auth0 alternatives in DevOps are ranked by recent ship velocity. Browse the "Auth0 alternatives" section above for the current picks, or visit /alternatives/auth0 for the full list with editorial commentary on each.