MAQPNA

Product · AI agent runtime

Every AI agent action, governed.

MAQPNA is an AI agent gateway and runtime that works under any framework. It decides what agents reach, do and leave behind. New to the category? Read what an MCP gateway is.

Isolate

Agent sandbox, one per session.

Pick the boundary per agent with a trust tier. Default-deny networking, always.

  • Non-root, read-only
  • Warm pools
  • Snapshots and fork
  • Browser and code profiles
tier-0gVisorruntimeClass: gvisor
tier-1Kata + Firecracker microVMkata-fc
tier-2Confidential VM, attestedkata-qemu-snp

Identify

Short-lived agent identity, on whose behalf.

Each session gets a short-lived, signed identity bound to its agent, tier and person.

  • Ed25519 + JWKS
  • A2A delegation chains
  • Token vault
  • OIDC admin roles
session identity (illustrative)
{
  "sub": "spiffe://cluster.local/ns/team-a/agent/coder",
  "session": "asess-91d2",
  "tier": "tier-1",
  "obo": "[email protected]",
  "exp": /* minutes, not months */
}

Govern

Policy for agent tool calls, default deny.

Rules allow, deny or hold. No matching rule means no.

  • Cedar and Rego
  • Rate limits and budgets
  • Model routes
  • Test, replay, eval
policy.yaml
kind: ToolPolicy
spec:
  defaultAction: deny
  rules:
    - name: read-only-tools
      tools: ["get_*", "list_*"]
      action: allow
    - name: destructive-needs-human
      tools: ["delete_*", "deploy_*"]
      action: require_approval

Approve

Human-in-the-loop approval for agent actions.

A person decides when a rule says so. Approving lets exactly one call run. Violet means a person is needed, not that something is wrong. How human-in-the-loop approval works.

  • Four-eyes
  • No self-approval
  • On the user's device (CIBA)
  • Console, Desk or CLI
Held for approval payments.create_transfer
On behalf of
[email protected]
Amount
€48,200.00
Rule
four-eyes above €10,000
Approvers
1 of 2
ApproveDeny

Protect

DLP and egress control for AI agents.

Data and secrets stay put. The gateway inspects what goes out, what comes back, and remembers what the session read.

  • DLP
  • Taint tracking
  • Tool pinning
  • Credential injection
argument"IBAN DE89 3704 0044 0532 0130 00, call Jan Novak"
forwarded"IBAN [REDACTED:iban], call [REDACTED:person]"
Redacted · 2 findings

Stop

Kill switch, in about a second.

Revoke an agent, session, user or token everywhere. The reason goes in the ledger.

  • GitOps manifest
  • Fail closed
  • Dedicated role
from maqpna kill -h
maqpna kill --gateway "$GW" -n team-a --agent coder --reason "INC-123" --terminate

Prove

Tamper-evident audit trail, not screenshots.

Every decision is a hash-chained record anyone with the public key can verify.

  • Signed checkpoints
  • WORM shipping
  • Evidence bundles
  • OpenTelemetry, SIEM, FOCUS

Operate

Day-two operations on Kubernetes.

Agents and policies are Kubernetes resources in Git. One CLI covers the lifecycle.

  • Helm profiles
  • HA gateway (Team and above)
  • Grafana dashboards
  • Console and Desk
  • maqpna preflight
  • maqpna install
  • maqpna upgrade check
  • maqpna doctor
  • maqpna status
  • maqpna smoke
  • maqpna backup
  • maqpna dr drill
  • maqpna keys rotate
  • maqpna audit verify
  • maqpna evidence
  • maqpna airgap
  • maqpna verify
  • maqpna support-bundle
  • maqpna costs

Your turn

You are the approver. Eight calls are waiting.

Approve or deny. Then see what the policy decided, and why. Keys A and D.

Call 1 of 8Agreed with policy: 0
Agent
team-a/coder
Tool
github.get_issue
Arguments
repo=web, issue=412
Context
Fixing a bug a user reported.

Approve or deny. Then see the policy's call.

Your ledgeryou · policy
    0 entriesappend-only

    Kosa8 Labs stack

    Even better with llamay and kosa8.

    Two other Kosa8 Labs products plug straight into the gateway.

    • llamay models

      Declare provider: llamay on an Agent. Each session gets its own inference context, forks with the session, and llamay's request audit is anchored in the ledger.

      Set up llamay

    • kosa8 sandboxes

      Run local agents in a kosa8 microVM that reaches only the gateway, fork it live into governed child sessions, and write policies that require the kosa8 boundary.

      Set up kosa8

    The Kosa8 Labs stack

    Open standards

    Built on upstream, not around it.

    • KubernetesCRDs, Helm, GitOps
    • agent-sandboxsandbox primitive
    • gVisortier-0
    • Kata + Firecrackertier-1
    • Confidential Containerstier-2
    • MCPtools
    • A2Aagent to agent
    • SPIFFE, OIDCidentity
    • OpenTelemetrytraces
    • Sigstore cosignsigned releases

    See the gateway decide on your own agent.

    Start on a laptop. Move to a cluster without changing code.

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