Product / Vault

Every document the firm holds, in one place that knows what they are

The Vault is a single pool for your entire document estate, described by what each document is, not by which folder it happened to land in. Search it, scope it, and run a review over any part of it.

The problem

A folder makes you choose one truth about a document

A single agreement is evidence in a matter, a contract of a particular kind, a document from a particular year, and possibly privileged. A folder structure forces you to pick one of those and file under it. Everything else about the document becomes something a person has to remember.

So the same instrument sits in three places under three names. The executed copy is in one folder, the draft in another, a scan of the signed version in a third. Nobody is confident which is current. When a question arrives (what did we agree with them on liability), the honest answer is that somebody will have to go and look.

That is not a filing problem. It is the reason a routine question takes two days.

How it works

Tags, not folders

In the Vault a document carries every description that is true of it at once. It belongs to a matter, it is a particular kind of instrument, it came from a particular year and a particular source, and it may be flagged privileged or poorly scanned. None of those exclude the others.

You narrow by picking descriptions, and every count updates as you go, so you can see what a filter will leave you before you commit to it. Select what remains and you can tag it, export it, or run a review over it.

01

Nothing is organised by where it sat.

Import from a network drive, a DMS, an email archive or a disc from the client; the folder structure is kept as tags rather than as hierarchy. What a document is survives the move. Where it used to live does not constrain you.

02

Versions collapse into the instrument.

A draft, the executed copy and a scan of the signed original are one entry with a version stack behind it, not three competing search results. You see the instrument; the versions are there when you want them.

03

Counts tell you the truth before you click.

Every facet carries its number against your current filter. If narrowing to one matter leaves four documents, you know before you narrow.

Intake

Nothing enters until you have seen what happened to it

Point the Vault at a folder and it reads every file before any of it is indexed: content hashes to remove exact duplicates, version clustering to collapse near-identical instruments, validation to find what cannot be read, OCR queued for scans below the text threshold, and tags derived from each file.

Then it stops and shows you the arithmetic. Nothing is indexed until you accept that. And the files held out are listed rather than quietly dropped, so the record of what was not taken in is as complete as the record of what was.

Intake · awaiting your acceptanceAn example intake
0files read from 214 folders
− 0exact duplicates removed, identical content hash
− 0near-duplicate versions clustered into their originals
− 0zero-byte, encrypted or unreadable, held out and listed
0documents enter the Vault
View 88 held outAccept and index

The ethical wall

The wall travels with the document, not the folder

Access in the Vault is governed by the matter a document belongs to. A lawyer sees the matters they are assigned to and nothing else, wherever that file physically came from, whoever uploaded it, whatever it is named.

That distinction matters more than it sounds. A permission set on a folder protects documents that happen to be in that folder on that day. A permission carried by the document protects it after somebody moves it, copies it, or imports a second set that overlaps the first.

And because every view is recorded against the person who made it, the wall is something you can evidence rather than assert. When a client or a regulator asks who had sight of what, the answer is a record.

Audit · Side letter, payment termsExample data
Matter · CS(COMM) 412/2025Privileged
WhenWhoAction
17 Jun · 10:42A. Mehta · assignedViewed
17 Jun · 11:05OrionExtracted 6 facts, returned for review
18 Jun · 09:13R. Iyer · assignedTagged “payment terms”
18 Jun · 16:30K. Singh · not on matterAccess refused · logged

For in-house teams

You already have the documents. You do not have the estate.

The contracts exist. They are in a shared drive, in a contract management system somebody configured in 2019, in the inbox of whoever negotiated them, and in a spreadsheet that was accurate when it was made.

What you lack is a single view that can answer a question about all of them at once: which agreements name this counterparty, which sit with that group entity, what we signed in the year under audit. The Vault gives you that without a migration project and without forcing a taxonomy on documents that have already been filed four different ways.

And because it holds the whole estate rather than one matter at a time, it is the thing a review runs over. You stop assembling a corpus by hand every time a question comes up.

For law firms

One pool, and walls you can prove

A firm’s problem is the opposite of a client’s: not that documents are scattered, but that they must be kept apart. The Vault holds every matter in one searchable pool while making the separation between them structural rather than procedural.

A lawyer sees their matters. Access is scoped by the tag the document carries, so it survives re-filing and re-import. Every view is logged against the person who made it, which turns a conflicts position from a policy you describe into a record you can produce.

Precedent works the other way. A firm library sits alongside the matters, visible to everyone, so the drafting you have already paid for is findable, rather than living in the folder of whoever wrote it.

FAQ

Questions about the Vault

Do we have to reorganise our files first?

No. Point it at what you have. The folder structure is read and kept as tags; nothing needs renaming or moving beforehand.

What happens to duplicates?

Exact copies are removed on content hash. Near-identical versions (a draft, the executed copy, a scan) are collapsed into one entry with a version stack. Nothing is deleted; it stops being three separate search results.

What about documents it cannot read?

They are held out of the index and listed, not guessed at. Scans below the text threshold go into an OCR queue. You see both counts before anything is indexed.

Can a lawyer see a matter they are not on?

No, and the attempt is logged. Access follows the document’s matter tag rather than its location.

Where is the data held?

In India. Customer data is hosted in the AWS Mumbai region and encrypted with AES-256 at rest and in transit. For organisations that need it, Xcelro can also be deployed air-gapped.

Now ask them something

The Vault holds the documents. Bulk Review reads them.

Bulk Review turns any part of the Vault into a table you can read: one row per document, one column per question, every answer sourced.

See Bulk Review →

Try it on your own documents

Start with what you already have

We can run an intake against a sample of your own documents and show you the reconciliation before anything is committed, including the files it could not read. That tends to be a more useful test than a demonstration on ours.