immudb
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
A side-by-side editorial comparison of pgBackRest and Gravity Forms — release velocity, themes, recent moves, and the top alternatives to consider.
PostgreSQL 19 support lands, and pgBackRest stops letting you run most commands as root.
2.59.0 in July added PostgreSQL 19 support and changed a long-standing default: only the restore command may run as root now, with anything else requiring an explicit allow-root. The same release ships a pregenerated distribution tarball so packagers no longer need the code-generation toolchain, and picks up an optional libsystemd dependency. Before it, 2.58.0 concentrated on object storage — HTTP support for S3, GCS and Azure, Azure managed identities, experimental S3 EKS pod identity, and configurable TLS cipher suites.
Gravity Forms 3.0 makes accessible forms the default, while the add-on fleet ships on its own clock.
Gravity Forms is a WordPress form builder whose 3.0 release put accessibility settings on by default for every new form and reworked international phone collection with better formatting and validation. Around that core release, the feed is dominated by independently versioned add-ons — Dropbox, Trello, Conversational Forms, Gravity Flow Checklists — each announced as its own release notice. Most of those notices carry a version number and a one-line description rather than a substantive change list.
2.59.0 in July added PostgreSQL 19 support and changed a long-standing default: only the restore command may run as root now, with anything else requiring an explicit allow-root. The same release ships a pregenerated distribution tarball so packagers no longer need the code-generation toolchain, and picks up an optional libsystemd dependency. Before it, 2.58.0 concentrated on object storage — HTTP support for S3, GCS and Azure, Azure managed identities, experimental S3 EKS pod identity, and configurable TLS cipher suites.
Two currents run through this window. The first is keeping pace with PostgreSQL itself, where support arrives experimentally a release early — PostgreSQL 18 in 2.55.0, 19 in 2.59.0 — so the backup tool is ready before the database is. The second is a steady move toward cloud-native identity and away from ambient privilege: managed identities and pod identity replace stored keys, and the root restriction narrows what a compromised invocation can reach.
Given the pattern of adding experimental support one PostgreSQL cycle ahead and hardening defaults as the release lands, the next release is likely to promote PostgreSQL 19 support out of its initial state. The notes do not say whether allow-root will be deprecated further.
Gravity Forms is a WordPress form builder whose 3.0 release put accessibility settings on by default for every new form and reworked international phone collection with better formatting and validation. Around that core release, the feed is dominated by independently versioned add-ons — Dropbox, Trello, Conversational Forms, Gravity Flow Checklists — each announced as its own release notice. Most of those notices carry a version number and a one-line description rather than a substantive change list.
The product's centre of gravity is the 3.0 line, where the meaningful decisions are being made about defaults rather than options: accessibility that is on unless someone turns it off, phone handling that validates rather than accepting anything. The add-on ecosystem ships continuously alongside it and mostly maintains integration surface with third-party services. Reading direction from this feed means separating the 3.0 posts from the release-notice stream around them.
Expect the 3.0 series to keep converting former opt-in settings into defaults, since that is the pattern both 3.0 posts share. The add-on notices give too little detail to predict anything about that track.
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 pgBackRest or Gravity Forms.
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
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.
Two patch lines, every release published twice, and no feature news since v24.0.0.
See all pgBackRest alternatives → · See all Gravity Forms alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Gravity Forms is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. Gravity Forms is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 pgBackRest alternatives in DevOps are ranked by recent ship velocity. Browse the "pgBackRest alternatives" section above for the current picks, or visit /alternatives/pgbackrest for the full list with editorial commentary on each.
Top Gravity Forms alternatives in DevOps are ranked by recent ship velocity. Browse the "Gravity Forms alternatives" section above for the current picks, or visit /alternatives/gravity-forms for the full list with editorial commentary on each.