Pernee indexes what your firm already stores — SharePoint, OneDrive, Drive, Outlook, Gmail, Teams — without moving any of it. Each time a document changes, the previous state is kept rather than replaced, so last year's workpaper is still there to compare against this year's.
In development. The vault's schema and access rules are built. Discovery and sync are the next phase, so this is what Vault will do rather than what it does today.
None of these are settings. They are properties of how the store is built, which is why they hold whatever anyone does to it later.
The bytes stay in the system that owns them. What Pernee holds is where a document is, what it is, and when it was last seen — so there is no second copy of your client files to secure, sync or explain to a reviewer.
When a document's content hash moves, Pernee files a new version beside the old one instead of replacing it. “Why did we change the apportionment method in 2024?” is a question about a difference across time, and answering it needs both years present at once.
When nothing attributes a file to a client, it stays unresolved and admin-visible rather than being assigned to a plausible one. Probabilistic matches queue for a person to confirm; they are never committed as truth on their own.
Every version records both when your firm changed the document and when Pernee observed the change. They are different facts and they can be years apart on anything captured retroactively, so the vault keeps them in separate columns and never substitutes one for the other.
Exactly one version of a document is current at any moment, guaranteed by a database constraint rather than by convention. A writer that tries to append out of order fails instead of quietly leaving two.
Content outlives the engagement that produced it, because that persistence is the memory. Purging is always a deliberate act with a retention class behind it — and a document under legal hold cannot be given a purge date at all.
A K-1 belongs to the partnership that issued it and to the individual who received it. The vault records both links, with the role each client plays, rather than forcing a document to pick one owner.
Nothing is migrated and nothing is moved. A document is indexed where it sits, and opening it takes you back to the system that owns it.
Works with the tools your firm already runs
Microsoft Teams
SharePoint
OneDrive
Outlook
Dropbox
Google Drive
Gmail
QuickBooks
Salesforce
Slack
PowerPointWe are GDPR compliant, with strict access controls on data synced from your connected tools.
Data is encrypted in transit today, and integration credentials are never stored in plaintext.
Working toward SOC 2 and ISO 27001 certification, with estimated completion before end of 2026.
Designed for teams who need control, consistency, and measurable impact across every demo touchpoint.
Request a demo