Bebra LabsA deep dive into version history
Version history sounds simple: keep old copies. At scale it's anything but. Here's how we store a year of history for 38 PB of live data without multiplying the storage bill.
Content-addressed chunks
Every version of every file is a manifest of chunk hashes. Identical chunks — across versions, files, even workspaces — are stored once. A typical document edited daily for a year adds only a few megabytes of new chunks.
Restore flow
Restoring reassembles the manifest and downloads the chunks. Because most chunks already exist on the restoring device, restores are usually faster than the original download.
What we don't do
We don't silently prune versions inside your retention window, and we don't count versions against your quota. Retention is a promise: 90 days on Solo, 365 on Team, unlimited on Business.