01 · Route
The K app sends AI calls to your collector
Only requests to model APIs are routed. Banking, email and the rest of the web go direct and never touch Kilasec.
See what every agent calls, cap runaway costs, and hold risky actions for a human — before the bill or the damage lands. Kilasec also masks secrets and PII before they leave, surfaces AI services nobody registered, and scans the replies coming back. No SDK to wire into your agents.
No SDK to wire into your agents, no sidecar, no rewrite. The K app on each device hands AI traffic to your collector, the collector decides in-line, and your console sees the decision — not the content.
Only requests to model APIs are routed. Banking, email and the rest of the web go direct and never touch Kilasec.
It decrypts the call and applies your policy — allow, mask, block, hold for a human, or cap spend — then scans the reply on the way back. It runs on hardware you own.
Verdict, rule, destination, user and cost reach the cloud with redaction already applied. Prompts and replies stay on your network.
Decrypted inspection of OpenAI, Anthropic, Copilot, Gemini, Bedrock, Ollama and 30+ endpoints — classified on the fly, including ones not yet named.
Secrets, credentials, customer PII and card numbers are masked before they cross the wire — even deep inside a long, oversized coding-agent conversation — and model replies are checked on the way back — reverse shells and dangerous commands caught, suggested package installs flagged for a human.
Map each request to a user and directory group — synced from AD by the collector itself, with agentless identity mapping from your domain controllers, or from CSV. Write allow group:eng → api.anthropic.com.
Every admin change and blocked request, kept up to 7 years on paid plans (30 days on Free). Export for SOC 2, HIPAA, or your own change control. Admins sign in with SSO on DNS-verified domains, and every signed-in session can be seen and cut off.
Built for the admin who has to live with it. No application changes, no SDK in your agents, no new box to rack — the enforcement point runs on hardware you already own.
Kilasec Connect sends in-scope AI calls to your collector and leaves everything else direct, untouched. Push it zero-touch through your MDM on macOS; on Windows it installs with enrollment and updates itself from signed releases. The same policies follow people off-network.
Runs read-only, non-root, --cap-drop=ALL, no-new-privileges, on amd64 or arm64. Keeps enforcing if the cloud blips, and request bodies are never written to disk.
Every failure carries an AFW-### code with its fix attached — on the console's Health page and in the on-box kilasec CLI. Or connect Claude to the console's MCP server.
# the entire deployment — one service services: collector: image: ghcr.io/blox-24/kilasec-collector:latest network_mode: host # sees the edge read_only: true cap_drop: [ALL] security_opt: ["no-new-privileges"] ulimits: nofile: 65536 env_file: .env # token from enrollment restart: unless-stopped # bring it up $ docker compose up -d # … and to remove it entirely $ docker compose down
Secrets and PII masked, destructive and shadow-AI calls blocked, runaway spend capped, the risky ones held for a human. Tap a control — or watch them cycle.
Illustrative replay of real policy decisions.
The exact event patterns Kilasec's policy engine detects and acts on — the everyday ways sensitive data, shadow AI, and runaway cost leave a network through model APIs, and the ways trouble rides back in on the replies.
An engineer asked for help debugging a script with a hardcoded access key and secret. Both would have left the network in the prompt body.
A support team's AI agent received raw transcripts containing SSNs and card numbers. None of it should have reached the provider.
A misconfigured QA agent kept re-running evals on a frontier model. At that rate, tens of thousands by morning.
A coding agent asked for an install script. The reply came back with a download-and-exec one-liner and a typosquatted package name — threats that travel toward your network, not out of it.
No form, no install, no sales call — every screen an operator gets: what Kilasec sees, what it enforces, and what it keeps on record.
Drop the DNS, proxy or packet-capture logs you already have and see every AI service on your network. It runs entirely in your browser — nothing is uploaded.
Tell us who you are and we'll set up your workspace — you'll get a link to sign in. Need more than 5 devices? Talk to us.