Veldris
Midgard · the enclosure · core platform

The enclosure holds.

Midgard is the defended trust boundary everything else stands on: identity, the object fabric, storage, compute, governance and post-quantum cryptography, deployed on your hardware, from a single node to a cluster, fully air-gapped if you choose.

§ 1 · Capabilities

Six services, one boundary

Identity

People, services and devices carry verifiable identities inside the enclosure. Every action is attributable; nothing acts anonymously.

Object fabric

Data lives as typed objects with lineage, not loose files. Every object knows where it came from, what produced it, and who may touch it.

Storage

Objects are sealed at rest with AES-256-GCM under ML-KEM-wrapped keys. Storage scales from one disk to a distributed cluster.

Compute

Pipelines, agents and applications run as governed workloads on your nodes. No core function requires an outbound call.

Governance

Policy is declared once and enforced everywhere: access, retention, purpose. Every decision the platform makes is logged and inspectable.

Post-quantum crypto

ML-KEM-768 (NIST FIPS 203) key encapsulation by default. The cryptography assumes the computers of the 2040s, not the 1990s.

§ 2 · The Seal

Sealing is a verb here

The Seal action is Midgard's oldest lineage: the post-quantum sealing work built at Kryotech, protecting 400,000+ Vox Messenger users worldwide, survives inside the enclosure as a first-class operation.

Seal an object and it is encrypted under keys only you hold, its lineage is signed, and its provenance travels with it. Unsealing is an audited event, never a silent read.

$ midgard keygen --kem ml-kem-768
public key written: 1184 bytes · ml-kem-768.pub

$ midgard seal vessel-1188 --key ml-kem-768.pub
sealed · aes-256-gcm · lineage signed
provenance: § feed-atlantic-raw → forge/tx-2214
§ 3 · Deployment

Runs where you say it runs

PropertySpecification
FootprintSingle node to multi-node cluster, on your hardware or your private cloud.
ConnectivityFully air-gapped operation supported. Zero outbound calls required for any core function.
Encryption at restAES-256-GCM under ML-KEM-768-wrapped keys (NIST FIPS 203) · ML-KEM-1024 optional
AuditSigned, append-only lineage for every object and every action.
DeliveryReproducible builds, signed SBOM per release, shipped through Bifrost, including as offline bundles.
LicenceOpen-source core under an OSI licence. Inspect it, fork it, continue it.
§ 4 · The products

What stands on it

Next

Your data. Your models. Your keys. Our problem to make that easy.