Control & Sovereignty | Pillar 3 of the platform

Tailor this page to you

Adopt AI without your data, costs,
or models leaving your control.

You’re mandated to adopt AI — but your data can’t leave the perimeter, only certain models are approved, and most AI testing SaaS is disqualified on day one. Karate runs entirely inside your network, on your own model, with a token bill you can cap.

Self-hosted, air-gapped,
BYO-LLM by design.

One Docker container on your infrastructure. Bring any model — cloud, approved, or fully local via Ollama. No outbound calls, no telemetry, no hosted control plane — and the deterministic core runs with zero AI at all.

What stays inside your walls

  • Your data

    No egress, no telemetry — ever

  • Your models

    BYO-LLM, including fully local

  • Your network

    One Docker container, air-gap ready

  • Your budget

    Token cost capped · ~$0 replay

Local-first by design — not a deployment option

No outbound calls.·No telemetry.·No hosted control plane.

Every component runs inside your perimeter. We don’t know what you’re testing — unless you tell us.

The business case

Say yes to the AI mandate —
without betting the data.

The board wants AI everywhere. You own the blast radius if it leaks data or runs up an uncapped bill. This is how you say yes, safely.

Your data never leaves

The whole stack runs inside your perimeter — no egress, no telemetry, air-gap ready. The deterministic core runs with no AI at all, so security can buy it before a single model is turned on.

Use the models you’re allowed to

BYO-LLM: your approved Azure OpenAI / Copilot models, or open-weight models you host yourself (Llama, Qwen, Gemma) via Ollama. Your keys, never captured by a vendor.

A cost your CFO can sign

Token-frugal by design, with ~$0 deterministic replay and usage on every report. Scale by adding a container — not by buying another row of per-seat licenses.

Our data can’t leave the country, only certain models are approved, and most AI testing SaaS is disqualified by security on day one.

— What regulated-enterprise security teams tell us

You feel this when…

  • Regulated industry or data-residency rules (data can’t leave Canada, Germany, the US…)
  • Security forbids cloud AI touching your code or data
  • Approved-model-only policy (Copilot / Azure OpenAI)
  • Token cost is under finance scrutiny
  • OSS-first / anti-lock-in engineering culture

Under the hood

One container. Your network. Your model.

What leaves your network: nothing. The entire pipeline — browser, agent, model — runs where you put the container.

Cloud AI testing SaaS

  • Sends your code, screens & data to vendor servers
  • Locked to the vendor’s models & token markup
  • Disqualified by security in regulated shops

Karate — self-hosted

  • One Docker container on your infrastructure
  • BYO-LLM — cloud, approved, or fully local via Ollama
  • Deterministic core runs with zero AI; air-gappable
# everything runs where you put the container
docker run -p 8080:8080 \
  -e LLM_ENDPOINT=http://ollama.internal:11434 \   # your network
  -e LLM_MODEL=gemma3 \                              # open-weight, local
  karatelabs/karate-agent

# no outbound calls  ·  no telemetry  ·  no keys leave your VPC

How we keep it inside your walls

Three guarantees, one perimeter

Use cases

Built for the rooms that can’t use SaaS

Run it inside your perimeter.

Deploy the container in your environment, point it at an approved or open-weight model, and watch the token meter — nothing leaves your network.