A separate instance
Your own environment instead of a place in the shared service. Where it runs — with us, in your cloud, or in your own building — is part of the scope.
Larger organisations
Vaultivo is built as a shared service for smaller businesses. If your organisation needs its own instance, or your archive has to satisfy a named standard, we scope that with you before anything is built. This page says what stands today — and what does not.
Today
These five hold for every account, down to the smallest. They are where a conversation starts, not what it produces.
What you upload or send in is never overwritten. Conversions made for reading are additional files beside it.
Every file gets its checksum as it arrives, and it stays with the document. A nightly run reads stored originals again and compares them against it — as a rolling window that takes the least recently checked first, not a pass over the whole archive. Whatever it finds lands in your own activity trail, and an object it could not read is counted separately from one that did not match.
Privileged access is logged, and log entries can be neither changed nor deleted — the database refuses both. Opening your own document records nothing.
Every archived original is backed up outside our main provider.
Alongside the usual ZIP, you can have your archive as a BagIt package, carrying checksums, provenance and retention dates in a PREMIS file inside it. It is a second format rather than a replacement — and it is a statement about the file that any archival system can check, not a certification: there is none to hold for OAIS, for us or for anyone else.
All five hold whether or not a dedicated instance is ever built. The features page covers them in detail.
Up for discussion
One item is open, and it is not built. Two others stood here once and now sit above under “Today”: the rechecked fingerprints and the archival package. What comes of the one that remains is settled in that conversation, not before it.
Your own environment instead of a place in the shared service. Where it runs — with us, in your cloud, or in your own building — is part of the scope.
That single item is a conversation and not an offer: what it covers, where it runs, and whether it happens at all stands at the end of the discussion rather than at its start.
Limits
Two things you would find out in a vendor review anyway. They belong here instead.
We hold no ISO 27001, no GoBD attestation and no certification as revisionssicher. If one of those is a precondition for you rather than a goal, we are not the right fit today.
Our terms promise no particular availability and no particular response time, and we set no formal recovery-time target — deliberately, because we would rather commit to nothing than to a figure the architecture cannot hold.
If either is a precondition for you, put it in your first message. It saves us both a call.
First message
Four answers are enough for an honest first reply. You do not need a requirements document.
Name it the way it is named where you work. This is the most important of the four — we want your word for it, not ours confirmed back.
Operated by us, in your own cloud, in your data centre — or still open. “Still open” is a useful answer.
Roughly how many documents a year, and the retention period you are working to.
A timeframe — and whether a budget exists for it.