MAQPNA

Sovereignty · Agentic AI that never leaves home

Sovereign AI for agents, in your jurisdiction.

Sovereign AI means your agents, their data and their records stay under your law and your control. Your infrastructure. No calls home. No internet required.

Three questions, one answer: you

  • Whose law applies?

    Only your clusters. A SovereigntyPolicy pins the jurisdiction.

  • Who can run it?

    No vendor control plane, licence server or telemetry.

  • Who can read the data?

    Confidential VMs, attested identities, signing keys you hold.

What sovereign AI means for agents

Sovereign AI is more than where the model runs.

Most talk of sovereign AI is about models and compute: whose GPUs, in which country. An agent adds a second question. It acts. It calls tools, reads records, moves data and spends money, and each of those actions needs a rule, sometimes a person, and a record that stays in your jurisdiction.

MAQPNA is the sovereign AI layer for agent actions. It runs on your clusters, pins sessions to a jurisdiction, allows only the registries and egress hosts you list, keeps signing keys in your custody, and writes every decision to a ledger you hold. Pair it with local models on the Kosa8 Labs stack, or route to the models you already use.

Running fully disconnected? Read air-gapped and on-prem AI agents.

Sovereignty policy

One sovereignty policy for every session.

enforce rejects non-compliant sessions. audit records them.

  • Jurisdiction
  • Registries
  • Egress
  • Attestation
  • Key custody
sovereigntypolicy.yaml
kind: SovereigntyPolicy
metadata: { name: default }
spec:
  jurisdiction: "EU"
  allowedRegistries: ["registry.eu.internal:5000/"]
  allowedEgressHosts: ["*.tools.eu.internal"]
  requireAttestationFor: ["confidential"]
  keyCustody: file             # pkcs11 and kms: planned
  telemetry: "off"
  enforcement: enforce         # enforce | audit

Attestation-gated identity

No evidence, no identity, no tool access.

  1. 01

    Inject

    The operator adds the attest agent to tier-2 sandboxes.

  2. 02

    Collect

    It gathers an SEV-SNP or TDX report bound to a nonce.

  3. 03

    Appraise

    A Confidential Containers Trustee checks your reference values.

  4. 04

    Release

    Only then does the broker mint the session identity.

Operational control

Your keys. Your network. Your records.

  • Customer-held keys

    Your own signing keys, from a file or Secret you create. PKCS#11 HSM and in-country KMS backends are planned.

  • Zero phone-home

    Only the egress you configure, enforced.

  • Air-gapped install

    One signed bundle: images, chart, SBOMs.

  • Immutable evidence

    Hash-chained, shipped to in-country WORM.

What we don't claim

No certifications, and installing MAQPNA does not make a system compliant. Sovereign AI depends on where you run it, who operates it and who holds the keys.

Plan a sovereign deployment.

Tell us where your agents must run and who must hold the keys.

More install options
curl -fsSL https://maqpna.com/install.sh | sh