Infrastructure / Continuum
Running fleetKeep your data available. Keep your choice of infrastructure.
A distributed record foundation designed to span cloud providers and on-premises systems, keep records recoverable through node failures, and let applications grow without tying their data to one provider.
The record foundation / Continuum
Keep records within reach.
Even as infrastructure changes.
Continuum is designed to span multiple clouds and on-premises systems at the same time. Records remain recoverable while enough independent archives are reachable and the access services are available. You choose the reconstruction threshold.
Plan for a provider to disappear.
Place archives across separate failure domains. With a k-of-n threshold, any k intact shares can reconstruct an already distributed record, so the loss of up to n minus k archives need not mean losing the record.
Move at your own pace.
The mesh is designed to accommodate new nodes and changing storage placement. That opens a path to gradual migration between providers and your own premises as costs and requirements change.
Build on the records you keep.
Sentinel, Prism and Pulse bring clinical workflows to this foundation. Folio applies it to documents and publishing, with a planned role as True North's archive.
One share cannot rebuild the record.
In this example, taking a single archive's stored share does not give an attacker enough material to reconstruct the record.
Reconstruction has its own gate.
The normal read path checks authorization before returning a record. Plaintext exists at reconstruction and in authorized applications.
Placement matters.
Separate providers and credentials reduce shared failure paths. The configured threshold determines how many archives can be lost.
Illustration of an already distributed record, not live infrastructure or a cryptographic simulation. The access gate shown is the service's read path: an attacker who obtains enough raw shares is a different threat. Availability also depends on the network, identity and reconstruction services.
Why I built it
A hospital should be able to keep using its records when a provider goes down, and move infrastructure when costs or requirements change. Continuum is built around that independence. Its mesh can span cloud and on-premises nodes, with records distributed across archives and a configurable number of shares required to reconstruct them.
Engineering decisions
Split records across archive nodes with a configurable reconstruction threshold. Fewer than the required number of shares cannot reconstruct a record.
Give reconstruction a separate service identity and short-lived authorization. Node enrollment and tenant access are enforced through certificates.
Keep applications separate from the fabric. The same record layer supports clinical workflows, documents and a title-and-escrow prototype.
Design node enrollment and placement around a changing fleet. The aim is to add capacity and move storage between clouds and on-premises systems gradually, while applications retain the same record interface.
What works today
A multi-cloud fleet has been running since May 2026. Recorded demonstrations include an outage and recovery sequence that restores 4,744 synthetic admission, discharge and transfer messages byte for byte.
Current boundaries
The fleet is running; the recovery result is a controlled demonstration with synthetic data. Reads require enough intact, reachable shares plus working identity, authorization and reconstruction services. Independence depends on separating administrative access as well as node placement. Gradual migration, larger deployments and operating-cost advantages need deployment-specific validation.