Run Claude Code, Codex and Grok on your own server, from the browser
Start, follow, approve and stop Claude Code, Codex and Grok sessions on a server you own, from a web console or the CLI, with your existing accounts.
Blog
Technical notes on running, governing and auditing AI tools on infrastructure you run.
Audit evidence a verifier can check offline
How a hash-chained ledger with per-event Ed25519 signatures and OSCAL export produces audit evidence an external verifier can confirm independently.
Ephemeral credentials for Claude Code with workload identity federation
Static API keys never expire, share identity, and silently shadow federation. WIF replaces them with attested JWT exchange for short-lived per-session tokens.
Inside the hooks PEP: deny-closed policy inside Claude Code
How a PEP classifies every Claude Code hook event into gating, context, or observe, wires the correct output schema per event, and deny-closes unknown events.
Governing MCP servers with RFC 9728 and RFC 8707: what actually works
Trace the OAuth 2.1 flow MCP mandates after a protected server returns 401, what RFC 9728 and RFC 8707 provide, and the security pitfalls.
Permitted vs observed: drift as a first-class finding
Drift between what an AI agent is permitted to do and what it is observed doing becomes a structured, classified finding with confidence levels.
Self-hosted governance next to the Claude apps gateway: a co-deployment guide
Anthropic's apps gateway handles OIDC auth for Claude. Your estate is more than Claude. This is the co-deployment architecture that governs both paths.
What your AI agents can actually reach: mapping agent access on real infrastructure
An AI agent holds credentials, is permitted some actions, and is observed doing others. The access map shows the gap, and where least-privilege quietly broke.
Auditing Claude Code and MCP servers in self-hosted environments
Build an auditor-grade trail for Claude Code and MCP servers without leaving your perimeter: per-agent identity, a hash-chained ledger, untrusted MCP signals.
Least-privilege drift: catching over-privileged AI agents before an incident
How to spot least-privilege drift in AI agents by comparing permitted access with observed behavior and enforcing policy at access time.
Self-hosted AI governance and data residency: the strongest GDPR story
Why self-hosting an AI platform is the strongest data-residency posture under GDPR: the governance tool never receives your data. Edges, not payloads.
Passive discovery vs proxies: inventorying AI agents without sitting in the data path
Two ways to see your AI agents: an inline proxy with high blast radius, or passive discovery from logs, OpenTelemetry and an eBPF backstop. An honest tradeoff.