MAQPNA

Data centres, neoclouds and telco clouds

Turn GPUs into governed agent cloud.

Your customers want to run agents next to the GPUs they already rent from you, but they need isolation, governance and evidence first. MAQPNA gives you a multi-tenant agent runtime to sell, with per-tenant keys, ledgers and usage, on hardware you operate.

Why capacity alone does not sell agent hosting

Raw sandboxes are a commodity. Governed, sovereign agent capacity is not.

  • No governed agent productCustomers can rent GPUs and VMs from you, but nothing that makes their agents safe to run.
  • Tenant isolationHosting many customers' agents needs hard isolation of sandboxes, keys, servers and records.
  • Billing per customerYou need metered usage per tenant (sandbox time, governed calls, model tokens) to charge for it.
  • Sovereignty as a selling pointCustomers choose a regional provider for sovereignty, and want proof, not a promise.

How MAQPNA solves it

A multi-tenant agent platform you operate

  • Tenants

    Each tenant has its own namespaces, trust domain, signing key, ledger, write-once storage prefix and quotas.

  • Usage metering

    Hourly usage per tenant: sandbox seconds, governed calls, model tokens and approvals, exportable in FOCUS.

  • Signed usage reports

    maqpna usage report writes an Ed25519-signed report that usage verify checks offline.

  • Three trust tiers

    Offer gVisor, microVM and confidential-VM tiers as products, priced by isolation level.

  • Sovereign profile

    Jurisdiction, registries and egress as policy, attestation and customer-held keys, for regulated tenants.

  • Day-2 operations

    preflight, upgrade check, backup, dr drill, keys rotate, alerts and runbooks.

Architecture

Governed agent hosting for many tenants

Each tenant's agents run in their own namespaces and sandboxes. One gateway enforces each tenant's policy, and usage is metered per tenant for your billing.

Your data centre · your GPUs · tenants isolated by namespace, key and ledger

Sandboxes

tier-0, tier-1 or tier-2, chosen per tenant

  • tenant-a/support-agent
  • tenant-b/coder
  • tenant-c/research

MAQPNA gateway

identity · policy · DLP · budgets · approval · audit

  • Allowedtenant-a: crm.get_tickettenant policy
  • Held for approvaltenant-b: git.merge_prdestructive-needs-human
  • Deniedtenant-c: tenant-a servertenant isolation

Your systems

  • modelGPU model routes
  • MCPtenant tool servers
  • usageper-tenant metering
One ledger and signing key per tenant · signed usage reports for billing
Illustrative names. You write your own policies.

Evidence

What your customers can show their auditors

Controls and evidence, mapped. Not a certification.

  • Per-tenant evidence

    each tenant's ledger is signed with its own key and can be verified by the tenant.

  • Sovereignty

    jurisdiction, registry and egress rules every session is admitted against.

  • DORA critical ICT third parties

    the ESAs designated their first critical ICT third-party providers in November 2025, mostly hyperscalers and AI providers. Per-tenant ledgers and a third-party register export give your financial-sector customers evidence for their own DORA work.

  • EU AI Act Art. 12 and 14

    record-keeping and oversight controls your customers configure; Annex III high-risk duties apply from 2 December 2027 under Regulation (EU) 2026/1744. How the EU AI Act applies to agents.

  • Roadmap, not built yet

    a white-label console and tenant self-service; ask us about timing.

FAQ

Common questions

What does MAQPNA do for data centres and clouds?

Your customers want to run agents next to the GPUs they already rent from you, but they need isolation, governance and evidence first. MAQPNA gives you a multi-tenant agent runtime to sell, with per-tenant keys, ledgers and usage, on hardware you operate.

What stops data centres and clouds from putting AI agents into production?

No governed agent product: Customers can rent GPUs and VMs from you, but nothing that makes their agents safe to run. Tenant isolation: Hosting many customers' agents needs hard isolation of sandboxes, keys, servers and records. Billing per customer: You need metered usage per tenant (sandbox time, governed calls, model tokens) to charge for it. Sovereignty as a selling point: Customers choose a regional provider for sovereignty, and want proof, not a promise.

Which controls does MAQPNA enforce?

Tenants: Each tenant has its own namespaces, trust domain, signing key, ledger, write-once storage prefix and quotas. Usage metering: Hourly usage per tenant: sandbox seconds, governed calls, model tokens and approvals, exportable in FOCUS. Signed usage reports: maqpna usage report writes an Ed25519-signed report that usage verify checks offline. Three trust tiers: Offer gVisor, microVM and confidential-VM tiers as products, priced by isolation level. Sovereign profile: Jurisdiction, registries and egress as policy, attestation and customer-held keys, for regulated tenants. Day-2 operations: preflight, upgrade check, backup, dr drill, keys rotate, alerts and runbooks.

Which regulations does it supply evidence for?

Per-tenant evidence: each tenant's ledger is signed with its own key and can be verified by the tenant. Sovereignty: jurisdiction, registry and egress rules every session is admitted against. DORA critical ICT third parties: the ESAs designated their first critical ICT third-party providers in November 2025, mostly hyperscalers and AI providers. Per-tenant ledgers and a third-party register export give your financial-sector customers evidence for their own DORA work. EU AI Act Art. 12 and 14: record-keeping and oversight controls your customers configure; Annex III high-risk duties apply from 2 December 2027 under Regulation (EU) 2026/1744. How the EU AI Act applies to agents. Roadmap, not built yet: a white-label console and tenant self-service; ask us about timing. MAQPNA supplies controls and evidence; it does not certify compliance.

Where does it run?

Each tenant's agents run in their own namespaces and sandboxes. One gateway enforces each tenant's policy, and usage is metered per tenant for your billing. The same runtime runs on a laptop, in your cloud account, on Kubernetes or air-gapped.

What does DORA's critical ICT third-party regime mean for GPU clouds running agents?

The ESAs designated their first critical ICT third-party providers in November 2025, mostly hyperscalers and AI providers. Per-tenant ledgers and a third-party register export give your financial-sector customers evidence for their own DORA work.

Turn GPUs into governed agent cloud.

Policy, approval flow and evidence, walked through with you.

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