Zero-exposure transfer
Studies move source-to-destination over short-lived, scoped, single-purpose signed URLs. The payload is never parked in systems that don't need it; the application layer sees only opaque identifiers.
Aegis is built so that every claim it makes (encrypted, delivered, metered, destroyed) is independently verifiable. This page summarizes the architecture; a public security overview covers the security model in full, and the complete technical specification is available under NDA.
Studies move source-to-destination over short-lived, scoped, single-purpose signed URLs. The payload is never parked in systems that don't need it; the application layer sees only opaque identifiers.
AES-256 envelope encryption at rest with a per-study key destroyed on expiry, TLS 1.2+ in transit, SHA-256 integrity verified end to end. Sent equals received, to the byte.
Delivery is measured and reconciled independently of both sender and receiver, never from self-reported volumes, so both parties can trust the bill.
Every authorization, access, delivery, and destruction is written to an append-only, SHA-256 hash-chained log, so altering any single record breaks the chain. Periodically the chain's root hash (and only that hash) is anchored to the Bitcoin blockchain via OpenTimestamps, producing strong, independently verifiable evidence that the log existed and was not altered after a point in time.
You can verify the receipt yourself with any OpenTimestamps client. No trust in Aegis required.
Open the live audit console (synthetic data, no login): anchor the root to Bitcoin, download the .ots receipt, then simulate tampering and watch the hash chain break. This is the running system, not a mockup.
On arrival each study is sealed with its own per-study key (AES-256), scoped to a single authorized recipient.
Release carries an auto-destruct window and a view policy; downloads and exports are blocked; every access is metered and logged.
At the window's end, or on demand, the payload is destroyed and the disposal recorded in the anchored audit.
Anchoring is often misunderstood, so here is exactly what it is, and what it is not.
No. Only the single SHA-256 root hash of the audit log is anchored. No PHI, no metadata, and no patient identifiers ever touch the chain. A hash is a one-way fingerprint — it cannot be reversed back into the underlying data.
No. OpenTimestamps uses the Bitcoin blockchain purely as a public timestamp notary. There is no token, no wallet, no payment, and no exposure to cryptocurrency price or volatility — only a verifiable record that a specific hash existed at a point in time.
A timestamp is only meaningful if the notary cannot be coerced, colluded with, or quietly rewritten — including by Aegis itself. Bitcoin is the most widely replicated, independently verifiable public ledger, so a proof anchored there can be checked by anyone, indefinitely, without trusting us.
That your audit log existed in exactly its current form at a point in time and has not been altered since. Combined with the hash chain, any edit to any past record becomes mathematically detectable by a third party.
A public security overview is available to everyone. The complete specification (metering reconciliation, key management, threat model, and audit anchoring) is available to qualified organizations under NDA.