$0
The full agent on your own machine, with Claude Opus 5.5, Sonnet 5.5 and Haiku 5.5 included free — no API key needed.
GPTClaudeGeminiMistralQwen Coder+ more
Download Kryex CodeSee it in action
Kryex Code and Kryex Admin, working together.
Kryex Code plans, delegates, and remembers — and still can't go around you.
Claude Opus 5.5, Sonnet 5.5 and Haiku 5.5 included free — no API key needed.Deploys into your VPC or fully air-gapped. Your models, your logs, your walls.
Describe what you want done — the agent reads, edits, and runs commands in your workspace, with approval on anything risky.
Pick a task to watch it plan, write, and run the fix. Every call is authorized against your live grant — anything beyond it is denied with a stated reason, never run silently.
Bring the model you already trust — through your own endpoint or gateway
A live checklist, sign-off before it touches anything — not commentary after the fact.
Subtasks run in isolated subagents, each with its own tracked budget — never pooled into yours.
Project rules, past corrections, approaches it's already ruled out — reloaded automatically, next session.
The decision to reach a database, an MCP tool, or run a command lives only in Kryex Server — never in the agent's own process.
Every connector runs through the same grants, approvals and audit log. How connectors are secured
Kryex Code, Kryex Server and Kryex Admin all deploy in your own infrastructure — in your VPC or fully air-gapped. Kryex Server is the only part that makes an authorization decision and the only one that writes the audit log. Kryex Code never holds a credential or a decision; it only acts on what the server allows.
Enterprise deployments run all three in your VPC or fully air-gapped. Nothing requires Kryex Labs' servers to be reachable.
ALTER TABLE. The rm -rf. The prod deploy.Resolved through one policy engine, every time.Every tool call Kryex Code makes — database, MCP, infrastructure, deploy — resolves through one policy engine on the server before it runs. Not application logic to trust, not a wrapper the agent can talk its way around. Shell commands are checked against the same policy engine, against an admin-set, default-deny shell policy.
One governed call, traced end to end— example: a developer with read-only access
Every connected system, resolved the same way — not just this one.
Manifest resolved for this user, before a single token is generated.
Every connected system, resolved the same way — not just this one.
The LLM emits a tool call — it doesn't know what it's allowed to do.
query("DELETE FROM orders WHERE id = 8841")Enforced server-side — the call never reaches the target system directly.
One policy engine for every connector, resolved deterministically, with a reason attached.
Not a dead end — a path forward the developer can act on.
“Read-only access to Orders DB. Request write access?”
Request write accessThe write never executes. Credentials live in the vault and the decision is enforced server-side — no config to edit, no key to steal. The refusal is data the model can explain, not an opaque error.
If the grant included WRITE with the approve-first modifier: the proxy holds the call, a team admin gets it in their approvals inbox, and on approval the proxy executes with vault credentials — the result streams back into the same session. The agent waits. The developer does nothing special.
The auditor replays any session as a timeline — what the agent tried, what was allowed, what was blocked, and which grant decided it.
This isn't a suggestion the model can talk itself out of. The policy gate enforces the boundary server-side, before the command runs — not a warning after the fact, not a setting a prompt can argue past.
No separate client to trust, no config pointing somewhere else — Kryex already is the client, so every read, write, and execute already runs through the same gate before it happens.
Kryex CodeThe full agent on your own machine, with Claude Opus 5.5, Sonnet 5.5 and Haiku 5.5 included free — no API key needed.
Self-hosted or air-gapped, RBAC with grants, approve-first sign-off, live quotas, the admin console, and an audit trail you own. Runs only the models you connect, inside your walls.
Talk to usBring your own key anytime — Kryex never marks up your provider's bill. Compare plans
Most of what the market calls “governance” is a tool asking its own user for approval. The user is still the one deciding. Kryex checks the grant, not the consent — and it holds even when the user says yes.
Alex asks the agent to fix a bad price. It writes the query and asks Alex to confirm.
UPDATE orders SET price = 42 WHERE id = 43;Self-hosted, one policy, built as its own coding agent from the ground up.
Every other gateway governs the model call. Kryex owns the agent that makes it — so the check happens where the action actually happens, not one layer removed from it.
Reviewed October 2026, based on vendors' public docs. Reflects each vendor's own public docs and product announcements as of this writing, not aspirational roadmaps on either side. Governance is improving everywhere — the gap is that it stops at each vendor's own boundary.