Atmora Tech

Operations platform

Every version, and every
person who opened it

Atmora Vault stores documents by content hash with immutable versions, disposal schedules that run from a trigger event, and legal holds that override them. When a regulator asks who had access to a file in March, the answer takes a search rather than a fortnight.

  • On-premise
  • Private cloud
  • Cloud
  • Hybrid

Overview

A content repository with retention, legal hold and an audit entry on every read.

Atmora Vault is a content repository for organisations that have to prove what happened to a document. Files are stored by content hash on a volume that can be write-once, versions are immutable, retention runs from a trigger event rather than the upload date, and every view, download, print and failed access attempt is written to the audit log with actor, timestamp and source address. Capture is built for the paper backlog: scanner, email and SFTP ingestion with OCR across English and ten Indic scripts, plus barcode separation so a 400-page batch splits into the right files without a clerk doing it by hand.

Vault is a system of record, not a collaboration tool. There is no live co-editing, and it integrates with Microsoft 365 and Google Workspace for daily authoring instead of competing with them. If what you want is shared drives with better search, Vault is heavier than the problem needs. It fits where an auditor, a regulator or opposing counsel can ask a precise question about a specific file on a specific date, and the answer has to be exact and evidenced.

2.4 s
Retrieval time on a 180 million-document repository
-91%
Physical file storage retired in year one at Aldridge Risk
100%
Reads, downloads and denied attempts captured in the audit log
7 minutes
Time to assemble a complete file for a regulator request

Modules

What ships in the box

  • Repository, versioning and content addressing
  • Capture, OCR and classification
  • Retention schedules and legal hold
  • Search, taxonomy and metadata
  • Approval workflow and signature
  • Audit, reporting and disposal certificates

Integrates with

  • Microsoft SharePoint
  • Microsoft 365
  • Google Workspace
  • SAP S/4HANA
  • ServiceNow
  • DocuSign
  • Salesforce
  • Okta

Capabilities

What it does

  • Content-addressed storage with an optional WORM tier

    Objects are stored and verified by content hash on a volume that can be write-once. A tampered file fails verification on read rather than being served quietly to the next person who asks.

  • Capture built for a paper backlog

    Bulk ingestion from scanners, email and SFTP with OCR across English and ten Indic scripts, plus barcode separation so a 400-page batch becomes the right set of individual files.

  • Retention that runs from an event

    Disposal rules count from a trigger such as contract expiry or account closure, not the upload date. Legal hold overrides disposal and is itself an auditable act with an owner and a reason.

  • Audit entries on reads, not just writes

    Views, downloads, prints and denied attempts are recorded with actor, timestamp and address. Answering who saw a document is a search across the log rather than a forensic exercise.

  • Redaction that removes rather than covers

    Redacted regions are burned out of a derived copy while the original stays under restricted access, so a shared PDF cannot be un-blacked by anyone who selects the text underneath.

  • Check-in, check-out and unambiguous versions

    Editing locks the document and records who holds the lock. Every version is retrievable with its metadata differences, and the current version is never in doubt on any screen.

  • Search across metadata and full text together

    Filters on class, counterparty, date and status combine with full-text ranking. Results respect permissions, so a restricted document never appears as a tantalising title in a hit list.

  • Approval routes attached to document class

    Contracts, invoices and personnel records follow their own approval chains with delegation, ageing escalation and a signed record of each decision taken along the way.

FAQ

Questions we get asked

Can Vault run entirely inside our data centre?

Yes, and most deployments do. It needs object storage that supports object lock for the write-once tier, PostgreSQL for metadata and a search node. No component makes outbound calls, and licence validation is offline through a signed file.

How does disposal work in practice?

Eligible records are listed for the records owner, who approves or defers each with a reason. An approved disposal deletes the object, keeps the metadata stub and generates a disposal certificate naming what went and under which retention class, which is the artefact auditors ask for.

Will people actually file documents here?

Only if filing happens where they already work, which is why capture runs from Outlook, SharePoint, scanners and a mobile camera rather than from a portal nobody opens. Adoption failures in document management are almost always about capture friction, not the repository.

Start a project

Tell us what is
breaking.

We reply within one working day, and the first call is with an engineer who would actually work on it — not an account manager. If we are not the right studio for the problem, we will say so on that call.

Start a project