Tines
Tines lets admins grant each product area separately without splitting teams.
Comparison · DevOps
pgBackRest vs Rivet
A side-by-side editorial comparison of pgBackRest and Rivet — release velocity, themes, recent moves, and the top alternatives to consider.
pgBackRest vs Rivet: at a glance
| Feature | pgBackRest | Rivet |
|---|---|---|
| Sector | DevOps | DevOps |
| Velocity score | 5.0 | 7.5 |
| Sparks · 30d | 0 | 3 |
| Top themes | postgresql, backup, data-integrity, object storage | actors, ai agents, sqlite, forking |
| Last editorial update | 12d ago | 2d ago |
| Website | Visit → | — |
What is pgBackRest?
pgBackRest 2.60 now stops a restore when a page checksum is bad
pgBackRest 2.60.0, released October 18, changes a default: restore now errors and stops if a restored file has an invalid page checksum, leaving the cluster unable to start until the restore is rerun, and expire refuses to proceed if the oldest retained backup would contain checksum errors. Setting checksum-page-error=n returns to warnings. The release also adds GCS Workload Identity Federation and prefetch for object-store reads. Two weeks earlier 2.59.3 fixed a bug that could generate weak encryption subkeys and salts when system random data failed.
What is Rivet?
Rivet Actors can now fork in 20 ms, SQLite database included, without copying data.
Rivet builds infrastructure for long-lived actors and AI agents: BYOC, OpenTelemetry tracing, actor-scoped JWTs and agentOS Hosted VMs. The 3.0 Preview made Rivet a single stateless binary on S3, and the Rust SDK reached general availability on 6 November. On 11 November Rivet added actor forking: a fork starts in 20 ms with the original actor's state and SQLite database and costs nothing until it writes.
pgBackRest vs Rivet: editorial side-by-side
pgBackRest
5.0DEVOPS
pgBackRest 2.60 now stops a restore when a page checksum is bad
◆ Current state
pgBackRest 2.60.0, released October 18, changes a default: restore now errors and stops if a restored file has an invalid page checksum, leaving the cluster unable to start until the restore is rerun, and expire refuses to proceed if the oldest retained backup would contain checksum errors. Setting checksum-page-error=n returns to warnings. The release also adds GCS Workload Identity Federation and prefetch for object-store reads. Two weeks earlier 2.59.3 fixed a bug that could generate weak encryption subkeys and salts when system random data failed.
◆ Where it's heading
The project is moving from reporting corruption to refusing to continue past it, a stricter stance that fits the root restriction in 2.59.0. Cloud identity continues too, with GCS joining the Azure and S3 work. Underneath, the code generation, documentation tools and test harness have moved from C and Perl to Python, and a documented release schedule and new website show the project formalizing how it runs.
◆ Prediction
Patches tracking PostgreSQL 19 should continue, as 2.59.2 did with 19beta4. Now that restore can fail on checksums, expect follow-up fixes or guidance for clusters where existing backups contain them.
Rivet
7.5DEVOPS
Rivet Actors can now fork in 20 ms, SQLite database included, without copying data.
◆ Current state
Rivet builds infrastructure for long-lived actors and AI agents: BYOC, OpenTelemetry tracing, actor-scoped JWTs and agentOS Hosted VMs. The 3.0 Preview made Rivet a single stateless binary on S3, and the Rust SDK reached general availability on 6 November. On 11 November Rivet added actor forking: a fork starts in 20 ms with the original actor's state and SQLite database and costs nothing until it writes.
◆ Where it's heading
Rivet keeps turning its S3-backed storage engine into features for agent workloads. Copy-on-write forking follows from the 3.0 storage design and gives agents a cheap way to branch a session, try something and discard it. The SDK and auth work of the past two months points to Rivet positioning actors as the runtime for agent backends.
◆ Prediction
Forking is likely to show up next in agentOS and the Pi integrations as a way to branch agent runs; the entries do not say when 3.0 leaves preview.
Alternatives to pgBackRest and Rivet
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 Rivet.
Appsmith
Appsmith 2.7 makes its MCP agent ask before deleting widgets and blocks stale edits.
Apache Arrow Rust
Arrow Rust cuts release candidates on three older lines at once.
Sanity
Sanity's MCP server now explains failed validations and stops skipping them.
GitHub
GitHub sets a December 8 cutoff for ARM32 Actions runners and opens AI Scan to the API.
Manticore Search
Manticore keeps patching 31.x, now fixing a FREEZE crash and a DocID ordering bug.
See all pgBackRest alternatives → · See all Rivet alternatives →
Recent activity from pgBackRest and Rivet
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoRivetIntroducing OpenOrange: Run Cloudflare Workers Anywhere ⚡
- 3d agoRivetIntroducing Actor Forking for SQLite ⚡
- 8d agoRivetRust SDK for Rivet Actors Is Now Generally Available
- 19d agoRivetIntroducing Rivet 3.0 Preview ⚡
- 27d agopgBackRestv2.60.0: Page Checksum Errors and Object Store Prefetch
- 1mo agoRivetIntroducing agentOS 0.4 & Hosted VMs
- 1mo agoRivetIntroducing Pi Durable for Rivet
- 1mo agopgBackRestv2.59.3: Weak Encryption Subkey Bug
- 1mo agopgBackRestv2.59.2: PostgreSQL 19beta4 Support
- 2mo agopgBackRestv2.59.1: PostgreSQL 19beta3 Support
- 3mo agopgBackRestv2.59.0: PostgreSQL 19 Support
- 9mo agopgBackRestv2.58.0: Object Storage Improvements
Frequently asked questions
What is the difference between pgBackRest and Rivet?
They serve adjacent needs but don't currently overlap on shipped themes. Rivet is currently shipping more aggressively (velocity 7.5 vs 5.0), with 3 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.
Is pgBackRest better than Rivet?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Rivet is currently shipping more aggressively (velocity 7.5 vs 5.0), with 3 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.
What are the best alternatives to pgBackRest?
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.
What are the best alternatives to Rivet?
Top Rivet alternatives in DevOps are ranked by recent ship velocity. Browse the "Rivet alternatives" section above for the current picks, or visit /alternatives/rivet for the full list with editorial commentary on each.