Platform overview
How METAFILES is built, secured, stored and scaled, for prospects, partners and technical reviewers.
These pages describe the platform under METAFILES: how a site is put together, how it keeps organisations apart, where their files are stored, how it is secured and what happens when something fails. They are written for prospects, MSP partners and the technical people who review a platform before trusting it with their data.
The short version
- The engine is the product. DMSVault's own storage engine, written in Rust, sits between every portal and the disks. It deduplicates, compresses, versions and encrypts every file with the organisation's own key, and it enforces quotas, read-only mode, WORM, legal hold and ransomware protection on every write.
- Three copies of everything. On the site's own storage, the engine's data is kept by a Ceph cluster that stores three copies on three storage servers, on encrypted disks.
- Every tier is paired or tripled. Two app servers, two office servers, three storage servers, with addresses that move automatically when a server fails.
- Each organisation stands alone. Its own key, storage space, database, cache and portal, and an isolation check before it is handed over.
- A control plane that builds and watches. New organisations and machine actions are carried out from signed, verified releases, and only after a person asked for them.
Pages
| Page | What it covers |
|---|---|
| Architecture | The servers and their roles, and how a file, a document edit and a call travel through the site |
| Security | The protection at each layer: edge, access, control plane, encryption, isolation, MSP controls, ransomware and WORM |
| Tenant isolation | What each organisation has of its own, and how isolation is proven on every build |
| Storage | Per-organisation storage targets: the site's storage, Amazon S3, S3-compatible services or the customer's own server |
| Scaling and high availability | What happens when a server fails, and how the site grows |
New here? Start with How it fits together for a lighter tour.
ArchitectureThe servers of a METAFILES site, what runs on each, and how files, document edits and calls travel through it.
SecurityHow METAFILES protects data at every layer, from the encrypted edge to per-organisation keys, isolation, server-side MSP controls, ransomware protection and WORM.
Tenant isolationWhat each organisation has of its own, how the isolation check proves it on every build, and which shared services are handled with extra care.
StorageWhere an organisation's files live, from the site's own three-copy storage to Amazon S3, S3-compatible services or the customer's own server, always encrypted by the engine.
Scaling and high availabilityWhat happens when a server of a METAFILES site fails, what is automatic today, and how a site grows.