Rollbar
Rollbar now runs Resolve by itself: a new error can become a fix PR with no one starting it
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 | 2 |
| Top themes | postgresql, backup, data-integrity, object storage | actors, serverless, storage engine, s3 |
| Last editorial update | 1h ago | 6d 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 3.0 Preview runs as one stateless binary on WarpDrive, with S3 as its only dependency.
Rivet has spent two months building infrastructure for long-lived actors and AI agents: BYOC in customer clouds, OpenTelemetry tracing, actor-scoped JWTs, Pi agent runtimes and agentOS Hosted VMs. On October 5 it said 3.0 would replace NATS with S3. The October 26 3.0 Preview delivers that: a new storage engine, WarpDrive, promises bottomless storage on S3 at SSD speed, and Rivet becomes a single stateless binary.
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 3.0 Preview runs as one stateless binary on WarpDrive, with S3 as its only dependency.
◆ Current state
Rivet has spent two months building infrastructure for long-lived actors and AI agents: BYOC in customer clouds, OpenTelemetry tracing, actor-scoped JWTs, Pi agent runtimes and agentOS Hosted VMs. On October 5 it said 3.0 would replace NATS with S3. The October 26 3.0 Preview delivers that: a new storage engine, WarpDrive, promises bottomless storage on S3 at SSD speed, and Rivet becomes a single stateless binary.
◆ Where it's heading
Each release removes operational burden: BYOC moved the control plane into the customer's cloud, and 3.0 reduces the self-hosted footprint to one binary plus an S3 bucket. The agent work (Pi, agentOS) sits on top as the main workload Rivet is courting.
◆ Prediction
Expect benchmarks and migration guidance for 2.x users during the preview, followed by a 3.0 GA. The entry gives no performance numbers, so the SSD-speed claim is unverified.
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.
Apache Kafka
Kafka 4.4 hardens share groups and Streams, then 4.3.2 patches two data-loss risks a day later
HashiCorp
Terraform 1.16 brings more of the infrastructure lifecycle back inside Terraform
Okta
Okta adds TypeScript to its Cross App Access guides and dates the end of Classic Engine features
Tines
Tines opens Records to AI clients and removes stored keys from its cloud credentials
Browser Use
Browser Use opens BU Ultrafast to every US plan, free tier included
See all pgBackRest alternatives → · See all Rivet alternatives →
Recent activity from pgBackRest and Rivet
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7d agoRivetIntroducing Rivet 3.0 Preview ⚡
- 14d agopgBackRestv2.60.0: Page Checksum Errors and Object Store Prefetch
- 21d agoRivetIntroducing agentOS 0.4 & Hosted VMs
- 26d agoRivetIntroducing Pi Durable for Rivet
- 28d agoRivetReplacing Our Message Broker with... S3? ⚡
- 28d agopgBackRestv2.59.3: Weak Encryption Subkey Bug
- 1mo agoRivetIntroducing Pi 1.0 for Rivet
- 1mo agopgBackRestv2.59.2: PostgreSQL 19beta4 Support
- 1mo agoRivetIntroducing JWT Authentication for Rivet Actors
- 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 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.
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 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.
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.