One enclosure. Four products.
Every Veldris product runs inside the Midgard enclosure and inherits its guarantees: post-quantum sealing, signed lineage, local inference, zero required outbound calls. Each is independently useful. Together they compound.
The enclosure
Midgard is the core platform: identity, the object fabric, storage, compute, governance and post-quantum cryptography inside one defended trust boundary. It is the part our competitors call the substrate, and the part they will not show you.
Standing on it
Forge · data operations
Forge shapes. Pipelines are declared, versioned and replayable; every transform records its inputs, its code hash and its outputs. Nothing derived loses its lineage.
competes with Palantir FoundryForge →Mimir · local agentic AI
Mimir remembers. Every inference runs on your hardware, under keys only you hold, on GLM 5.2. First token in under 800 ms, or none at all.
competes with Palantir AIPMimir →Bifrost · continuous delivery
Bifrost carries. Signed releases travel from build to enclosure with the SBOM attached; nothing deploys that cannot prove where it came from, including across an air gap.
competes with Palantir ApolloBifrost →Heimdall · operational fusion
Heimdall watches. Live feeds fuse into one operational picture where every object on the map traces to its source, connected or disconnected.
competes with Maven Smart SystemHeimdall →If you know their stack
| They sell | We publish | The difference |
|---|---|---|
| Foundry substrate · Ontology | Midgard | Open source, self-hosted, post-quantum sealed, air-gap native. |
| Foundry | Forge | Declared, replayable pipelines with signed lineage on every object. |
| AIP | Mimir | Local inference only. Models pinned by hash. No cloud, ever. |
| Apollo | Bifrost | Reproducible builds, signed SBOM per release, offline delivery bundles. |
| Maven | Heimdall | Every fused object carries provenance you can open and read. |
Each stands alone. Together they compound.