Who Speedwave is for

Speedwave is designed for entire software development teams, providing workflows tailored to developers as well as non-technical collaborators.

Software engineers and developers

For developers writing code, the terminal CLI provides an efficient, scriptable workflow. Executing speedwave launches the container environment for the active project and establishes an interactive Claude Code session within the sandbox. The CLI operates as a lightweight client: it relies on the Speedwave Desktop installation for initial provisioning, including virtual machine setup, container image builds, and credential management. Desktop also automatically configures the speedwave binary in your PATH, ensuring version alignment across both interfaces.

Cross-functional team members

Non-coding team members can use Claude Code without touching the terminal. The Desktop application (Speedwave.app) delivers an intuitive chat interface with a project switcher, setup wizard, and operating system integrations (such as system tray controls and automatic update checks). The application streams Claude responses in real time from within the container sandbox.

Both the Desktop application and CLI interact with the exact same underlying runtime (speedwave-runtime) and container orchestration engine, guaranteeing identical model behavior across both interfaces.

Regulated-sector organizations

For organizations operating in regulated sectors (such as banking, financial services, healthcare, or insurance), Speedwave provides technical guardrails designed for strict compliance:

• Isolated credential storage: Claude executes in a container with zero service tokens. Third-party integrations (like Slack or GitLab) run in separate worker containers with read-only credential mounts, ensuring that models never receive direct access to secrets.
• Provider choice and data sovereignty: Each project configures its own model backend (Anthropic, local model servers such as Ollama, or OpenRouter). Local model endpoints allow code and prompts to remain on local infrastructure when data residency policies require it.

These security boundaries represent foundational architectural commitments. See Security architecture for an in-depth review of compliance and isolation guarantees.