The lock is applied by the vault, not by the application
Archivia has no power to seal or unseal anything: the object store applies the retention on write, without being asked. Removing the application does not remove the lock.
Archivia archives your company mailboxes and locks every message for the retention you choose. Once written, an email can no longer be altered or deleted before its term — not by an employee, not by an administrator, not by us.
Live within one business day. Cancel at any time.
object-lock • retain-until 2036-09-04Plenty of tools call "archiving" a bin that never gets emptied. The difference shows the day someone genuinely wants a message gone.
Archivia has no power to seal or unseal anything: the object store applies the retention on write, without being asked. Removing the application does not remove the lock.
Your instance credentials are scoped to your storage alone, and do not permit deletion there. A compromised instance cannot destroy your archives — at worst it stops adding to them.
In compliance mode, even the account that administers the storage cannot shorten a retention before its term. That is the property we looked for when choosing the engine, and the one we verified before anything else.

An archive you cannot extract anything from is worth nothing the day a lawyer, an auditor or an employee asks to see.
Microsoft 365, Google Workspace and IMAP. Synchronisation runs on its own; you connect the mailbox once.
Across message bodies and attachment contents — PDFs, office documents, images passed through OCR.
You set the term. It applies as each message is written, and runs to its end without intervention.
A message or a selection exports in an open format, with what is needed to say where it came from.
Most SaaS products put every customer in the same database, separated by a column. One badly written query is then enough to cross the partition.
With Archivia, subscribing creates your instance: your application, your database, your storage, your network. Nothing is shared with another customer, and the separation does not depend on a query being correct — it is carried by the infrastructure.
Payment is handled by Stripe; we never see your card.
Within one business day. You receive its address and a first administrator account.
Microsoft 365, Google Workspace or IMAP. Archiving starts and runs on its own.
You export your archives before the instance closes. Whatever is under retention stays under retention until its term: that is the price of immutability, and we would rather say so beforehand.
We operate the infrastructure, so technical access exists — claiming otherwise would be false. What bounds it is named, logged access, and the fact that your instance is separate from every other.
Your archives sit in an S3-compatible object store, in an open format. They do not need our application to be read — which is exactly why the lock is applied by the storage.
If it has already been archived, it stays in the archive. That is the whole point: the mailbox is a working tool, the archive is a record.
The price is shown at checkout, on Stripe, before any commitment. For large volumes or dedicated infrastructure, write to us.
Open an account, we build your instance, you connect your first mailbox.