The Storage service is versioned file/object storage - supporting live replication to a remote OwnCDN instance.
Instead of overwriting a previous version of a file / object, OwnCDN can create a new version for each update (including deletions).
This means that it is possible to restore individual files to a previous version - including deleted files.
It is also possible to restore the whole storage service to a specific point in time. See the Command line options for details.
Live replication means that any file additions, updates, and deletions you make to files on one OwnCDN instance can be instantly synchronized to another instance. This includes versions (see above), so that restoring old versions and point in time restore also works on the replica server.
To set up replication (on the "secondary" OwnCDN instance), you first create a Replication source with the URL of the HTTP API and an API Key value from the primary OwnCDN instance. Then create a new Storage service with the "Replica" setting checked, and using the above Replication source.
Files / objects are stored in an SQLite database file in WAL mode (very performant and provides safe database recovery after a server crash).
Files / objects are stored in Brotli compressed format, for lower disk use and optimized CPU usage (each object only compressed once, rather than every request).
Large files (such as video) are automatically broken into and stored as smaller pieces to support video streaming / byte-range requests.
See UI / Edit Service - Storage for configuration options.