How Speedwave controls AI-assisted development.
Speedwave adds a security and governance layer around AI coding assistants, limiting what they can see, access and do while keeping developer workflows usable.
Built around isolated runtimes, scoped tool access, credential separation, PII tokenisation, local LLM options and audit logging.
Layers that keep the assistant inside defined boundaries.
Speedwave separates the AI assistant, project workspace, external tools, credentials and audit layer so that AI-assisted work can happen inside defined security boundaries.
AI assistant
Claude Code or a local LLM used by the developer. Runs inside the controlled runtime - it cannot reach the host directly.
Controlled runtime
A hardened local environment that limits project and workstation access. Lima on macOS, rootless nerdctl on Linux, WSL2 on Windows.
Scoped tool gateway
Approved tool integrations exposed through controlled interfaces. The assistant sees two tools: search for the right tool, and execute code.
Credential isolation
Service credentials stay outside the assistant and are only used by approved workers. API keys go directly to Anthropic - never to Speednet.
Data protection layer
Sensitive values can be detected, tokenised and restored locally. PESEL, IBAN, card numbers, email and phone numbers never reach the model as-is.
Audit trail
AI-assisted activity is logged for security, governance and review. Every READ/WRITE/DELETE with timestamp and attribution, from the first session.
What runs on every engineer workstation.
One installer. No Docker, no Kubernetes, no IT ticket.
Hardened local runtime
Scoped tool gateway
PII tokenisation
Credential isolation
13-agent code review pipeline
Full audit log
Local LLM support
Trusted integrations
11 independent defense layers.
Your security team can read every line.
Apache 2.0 with explicit patent grant. No NDA required for a security audit. Perpetual access to the codebase even if Speednet disappears - your DORA exit strategy.