Manufacturing plane
ENI6MA Foundry
Available for evaluationFoundry (the minting appliance that manufactures per-identity circuit binaries in cohorts; the ENI6MA equivalent of a certificate authority, but for one-shot identities instead of long-lived X.509 certs) is where identity gets manufactured. It compiles identity into a compiled twin (the per-identity binary a workload runs to prove itself, produced by the Foundry minting appliance), packages twins as cohort zips, and hands them to Control for activation. It is licensed separately from the Gate subscription and runs air-gapped for sovereign estates that cannot let identity material leave the network.
Foundry minting
Air-gapped minting appliance producing cohort binaries and twin circuits
Twin circuits / cohort
Twin entangled circuits from one cohort mint batch
Why Foundry exists
For an investor or security architect who wants the plain-language story.
The moat under ENI6MA is not only the cryptographic mechanism, it is also the supply chain that produces the identities. Foundry is that supply chain. It is the ENI6MA equivalent of a certificate authority, except that instead of issuing a long-lived X.509 certificate that can be exfiltrated and reused, it stamps out per-identity circuit binaries whose configuration and entropy are compiled inside the artifact itself. Revocation becomes a state change in Control, not a rotation campaign across every workload.
What Foundry produces
ENI6MA Foundry mints cohort zips of per-identity circuit binaries for activation through Control.ShippingDEMO-MINT + E6-MINTING/ENGINE, OpenAPI 1.5.0, seven circuit variants.
Foundry is licensed as a minting appliance and can run air-gapped for sovereign deployments.ValidatedFoundry appliance packaging and Sovereign pricing model.
- An OpenAPI 1.5.0 minting surface with seven circuit variants, so a buyer can tune the shape of the compiled twin to the workload that runs it.
- Cohort zip output for batch identity issuance, so an estate can mint a fleet of workloads in one operation instead of one call at a time.
- Identity that is compiled into the binary itself; a circuit (a compiled cryptographic identity that carries its own configuration, entropy, and policy inside the binary itself, so identity travels with the artifact rather than sitting in a vault of transferable secrets) does not sit in a vault of transferable secrets waiting to be stolen.
- DEMO-MINT and E6-MINTING/ENGINE as the evaluation path today, so a customer can watch the minting pipeline before it goes into their build.
How Foundry fits the four planes
Four authorization planes
Read top-to-bottom through Foundry (mint twins), Control (registry and ledger), Gate (request boundary), and Verify (adversary harness). Each band is a different ops job that ships the same proof family. Takeaway: the product stack separates integrity tooling from the empty-channel authorization thesis.
Foundry manufactures identities and hands them to Control (the control plane: a registry of active identities plus the durable nonce ledger; conceptually the token-issuer, revocation registry, and audit log for one-shot proofs combined). Control activates a handle (the stable identifier for an identity or workload; deactivating a handle in Control is how revocation happens as a single state change) and can revoke it later with one state change. Gate consults Control on each request and enforces at the boundary. Foundry is licensed as an appliance, because it is infrastructure for the estate that mints, not a per-endpoint subscription.
Foundry is licensed separately from Gate subscription tiers.Design targetManufacturing plane licensed as appliance infrastructure.
Deployment shape and integration
- Runs as a minting appliance inside the estate that produces identities, on-prem or in a controlled cloud environment.
- Supports air-gapped operation for sovereign tiers, so minted material never has to traverse a public network to reach Control.
- Emits a manifest (a manifest is the metadata record for a minted binary: hash, size, timestamps, and self-validation state) for every produced twin, so build systems and auditors can track what was minted, when, and against which policy.
- Handoff to Control is a cohort import; from there Control owns activation and revocation of each handle in the cohort.
Evaluation
- Available under evaluation engagements ahead of general availability, so a design partner can see the full pipeline before signing a licence.
- The Sovereign tier pairs a Foundry licence with self-hosted Control and air-gapped operation, for estates that cannot let identity material touch the internet.
- Deeper minting walkthroughs will live under Developers once that section lands.
Ready to protect an endpoint?
Foundry is licensed separately from the Gate subscription. Pricing is contact-led for Enterprise and Sovereign tiers.