For archives and records
Fixity you can show. Provenance to the arrival. Retention you can defend.
For archivists, records officers, museums and libraries, public bodies and small businesses: the material must outlast the people and the software that made it, and every question about it must have an answer on the record.
What you will use
- Archival copies to the standards. PDF/A-2b verified by veraPDF; FFV1/Matroska and FLAC proven by decoding; EA-PDF for email, self-checked while no independent validator exists.
- Fixity on a schedule. Four checksums at arrival; every file read back within a window and a byte budget you set; a mismatch is a notification and an audit event.
- Provenance. Every arrival recorded with its path, its times and who brought it; custodians and acquisitions named on the record with the Provenance module.
- Records. Retention schedules to a human queue, holds that freeze, dispositions with a certificate, an audit chain anchored and verifiable offline.
- Backups you can open without us. Seven kinds of destination; every snapshot carries a catalogue, a readable tree of the originals and a manifest signed with a key you keep, so a copy is proven and opened with stock tools.
- Runs where you decide. On your network, in your data centre or in a cloud you control; updated by policy, with a hold you can apply.
modules: Records, Archival copies, Provenance · every file checksummed four ways · the audit chain's verifier ships with the software
An archive that understands what it keeps.
The same archive, the same guarantees.
Thirty days with every module, no card, wherever you choose to run it. How it works · What leaves your archive