Security

Built to be trusted with the data you can't afford to leak.

A governance gateway sees your most sensitive traffic, so it has to be the most careful part of your stack. Here is how agentKeyRoute is built, including what it doesn't do.

Principles

How we handle your data.

Minimise what leaves

Sensitive values are redacted at the gateway, before a request reaches any model. The response cache keys on the redacted request, and health, card and secret data are never cached by default.

Default deny, fail closed

A request no rule allows is denied. If the model that answered isn't one the policy allowed, the request fails. Guardrails can be set to block when they're unavailable.

Organisations kept apart

The database enforces row-level security per organisation. Each organisation's routing keys are restricted to its own provider connections, and its cache is separate.

Keys sealed, not shared

Provider keys are stored once, sealed with the organisation's own data key, and never handed to tools. Tools get governed agentKeyRoute keys you can revoke at any time.

Tamper-evident records

Every decision is written to a hash-chained audit log. An integrity check shows whether any entry was changed or removed.

Two people for big changes

Roles, teams, two-step sign-in and two-administrator approval for sensitive changes. Support access is read-only and recorded in your own audit log.

Architecture

Your tools never talk to providers directly.

Tools call the agentKeyRoute gateway with a governed key. The gateway runs detection, policy, guardrails and risk scoring, then sends the request through a routing engine that can only use the models and connections your policy allows. The control API and console manage configuration, and the audit log records every decision.

Content capture is set per profile: off, redacted, sampled or full, depending on your plan. Retention runs from 90 days to seven years.

AI workspace

Sandboxes that can't wander off.

Each person gets their own container for the AI workspace. It runs as a non-root user with all Linux capabilities dropped, memory, CPU and process limits, a private volume and no host mounts, on an isolated network that reaches the gateway but never the database, cache or control API.

Its settings are written by agentKeyRoute in a file the person can't change, so the coding agent can only use governed models. Idle sandboxes are removed after 30 minutes; files are kept in the person's volume until it goes unused for 30 days.

  • Non-root user, all capabilities dropped
  • 2 GB memory, 1.5 CPU, 512 processes
  • Reaches the gateway, never internal services
  • Provider and account changes refused
  • One-time, 60-second sign-in links
  • Shown only inside your console

Deployment

Run it where your data rules say it must run.

Cloud

Hosted by us on the Starter, Pro and Enterprise plans.

Dedicated

An isolated instance for your organisation alone, on the Enterprise plan.

On-premises

The whole platform inside your network on the Enterprise plan. Model catalogue and zero-retention lookups can be switched off for air-gapped installs.

Being honest about limits

What agentKeyRoute doesn't do.

Attachment contents aren't scanned

Data detection reads text. Images, audio, video and files aren't inspected, so for sensitive workloads, profiles can block attachments entirely.

Some endpoints are refused, not governed

Audio transcription, batch and file uploads can't be inspected before they leave, so the gateway refuses them instead of passing them through.

The workspace's terminal can reach the internet

Code mode needs internet access to install packages, so someone could call an outside service from the terminal themselves. Restrict outbound traffic if that matters for you.

Personal subscription accounts carry vendor risk

Organisations can connect Claude, ChatGPT, Copilot or Gemini subscriptions. Vendors license these for personal use and may suspend accounts used for shared traffic, and frameworks keep sensitive data away from them.

Questions from your security team?

Start an organisation and look at the controls yourself: every decision is visible in the request explorer.