Manufacturing plane
ENI6MA Foundry
Available for evaluationFoundry is the minting appliance that manufactures per-identity circuit binaries in cohorts - the manufacturing plane for Cloud and Sovereign stacks. It compiles identity into a compiled twin (the binary a workload runs to prove itself), packages twins as cohort zips, and hands them to Control for activation. Unlike a certificate authority that issues long-lived X.509 certs that can be exfiltrated and reused, Foundry stamps identity material whose configuration and entropy live inside the artifact. Licensed separately from Gate; air-gappable for estates that cannot let minting 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
- Mint
- Hand off
- Air-gap
- Cohorts
Why Foundry exists
For an investor or security architect who wants the plain-language capability description.
Gate enforces one-shot envelopes at the boundary; those envelopes have to come from somewhere. Foundry is that supply chain. It manufactures compiled cryptographic identities so each workload carries its own binding instead of sharing a vault of transferable secrets. Observable outcome: a cohort of twins ready for Control to activate, each usable to produce request-bound proofs that Gate will accept under policy. Scope: Foundry mints and packages; it does not enforce at the request edge - that is Gate - and it does not hold the durable nonce ledger - that is Control. Revocation becomes a single handle state change in Control, not a rotation campaign across every workload that once trusted a shared secret.
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 compiled into the binary: a circuit carries configuration, entropy, and policy inside the artifact rather than sitting 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.
- A per-twin manifest (hash, size, timestamps, self-validation state) so build systems and auditors can track what was minted, when, and against which policy.
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 (registry of active identities plus the durable nonce ledger). Control activates a handle (stable identifier for an identity or workload) and can revoke it later with one state change. Gate consults Control on each request and enforces the eight-stage order at the boundary. Pass+ and Codebook cover human and paper paths that consume the same one-shot primitive. Foundry is licensed as an appliance because it is estate infrastructure for minting - not a per-endpoint Gate subscription. Sovereign stacks typically pair Foundry with self-hosted Control and air-gapped operation; Cloud stacks may use managed Control with Foundry on-prem or in a controlled cloud environment.
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.
- Handoff to Control is a cohort import; from there Control owns activation and revocation of each handle in the cohort.
- Integrators wire mint outputs into their build or fleet provisioning pipeline; Gate and Pass+ consume the resulting identities at request time.
- OEM partners may use Foundry-class manufacturing under a separate encapsulation license - that track is not free Circuit Authority enrollment.
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 live under Developers as that section lands; until then, contact-led evaluations are the path.
Ready to protect an endpoint?
Foundry is licensed separately from the Gate subscription. Pricing is contact-led for Enterprise and Sovereign tiers.