Records that outlive the systems they came from
Coming soonSeven years from now the server is gone, the vendor changed, and a regulator wants the 2026 records. Vault holds them: locked at enrollment, searchable the whole term, and destroyed with a certificate when the term ends.
Compliance retention is not a longer backup
Backup exists to bring a system back. Retention exists to answer a question years after the system is gone. Using one for the other is how MSPs end up paying to store everything forever, and still cannot produce the one record that was asked for.
Retention tied to a subscription you might cancel
If the archive dies when the backup contract lapses, it was never a compliance answer.
Storage that quietly compounds
Keeping everything forever because deleting anything is scary turns into a bill nobody can defend.
Deletion with no proof
When a retention period ends, saying the data is gone is not the same as showing that it is.
A separate custody lifecycle, on purpose
Locked when it goes in
Moving records into Vault is an explicit, audited operation with a stated term. Once enrolled, no console action, administrator, or attacker shortens it. The lock is the product.
Standalone by design
Vault accepts records from Microsoft 365 Backup, BCDR, File Backup, or an external source, and holds them under its own subscription. Cancel everything else and the archive still stands until its date.
Search, export, legal hold
Archives stay usable for the whole term: search the cohort, export exactly what a request demands, and place a hold that outranks the schedule when litigation arrives.
Certified destruction
When the term ends, destruction is deliberate and documented, closing with a signed certificate that outlives the data it certifies. Your client files the certificate, not a screenshot.
Prepaid and predictable
Fixed terms bought up front, priced as an archive rather than as storage that grows every month. You quote the retention obligation once and it stays quoted.
Your region, on the record
Data residency is a named selection confirmed before the first record lands, not a footnote in a subprocessor list. The region you choose is the region it stays in.
Three steps to a retention answer you can defend
Define
Name the cohort and the obligation behind it: the contracts, the statutory mail, the regulated records, and the years they owe.
Enroll
Move the records in. The term locks, the region is confirmed, and the operation lands in the audit trail.
Answer
Search and export whenever the question comes, then close the term with a certificate when it expires.
The request always arrives after the system is gone
Nobody asks for a seven-year-old record while the server is still humming. They ask during an audit, a lawsuit, or a dispute, when the answer is either in an archive built for this or nowhere at all.
What we commit to
- An enrolled term cannot be shortened by us, by you, or by anyone who steals a session.
- Vault holds its records without requiring any other EnterProtect subscription.
- Every destruction closes with a signed certificate that outlives the data.