Platform
Document security and data separation
Every layer is multitenant, and every layer separates one customer from the next.
Storage
S3-compatible object storage for content, with a SHA-256 digest recorded for every version, and a dedicated database per repository for description.
Description
A canonical model of identity, subject, agent, activity, event, rights, technical and relation facets, projected into the field names your organisation already uses.
Identity
A dedicated identity realm per customer: their own identity provider, password policy, lockout rules and session limits, with tokens accepted only from registered issuers.
Processing
Two-tier ingest makes documents available in seconds while deeper analysis runs on a queue operators can inspect and retry. Stage-level caching means changing an extraction rule re-runs that stage alone.
Interfaces
A REST API covering every function of the portal, for the systems around the archive.
Security and compliance
Separation by architecture
The guarantees below follow from how the platform is built, not from settings an administrator must remember to apply.
Tenant isolation
Each repository has its own database. Customer records are never mixed in shared tables, so isolation does not depend on a query filter being correct.
Identity per customer
Each customer authenticates in their own realm against their own identity provider, with their own password and lockout policy. Tokens are accepted only from registered issuers.
Authorisation on every request
Access lists are checked on every request against the specific document, and the interface offers an action only where the same check would permit it.
Fixity and provenance
A SHA-256 digest is recorded for every stored version and reported in PREMIS export, alongside the preservation events describing what was done to the file and when.
Sensitive values masked
Fields marked as sensitive show “Restricted” to anyone without an explicit right to view them — on screen, in search results and in exports.
No access for the operator
Platform administrators who run the service have no access to your documents. The Trace Warden right is granted per repository, the warden sees unmasked data only while a case is open, and every act is audited.
See Archystream with your own documents
Tell us about your record series and we will walk you through a portal configured for them, including the description quality we measure on documents like yours.
Or write to us at [email protected]