throughthewire.dev

Give an agent a machine, not your machine.

Dev environments and agent sandboxes, each a Linux virtual machine with its own kernel, in a browser tab.

Break anything inside. Reach nothing outside. Hold only the secrets scoped for the job. Start again in seconds.

Its own kernel Not a shared one with namespaces around it. Getting out means escaping KVM, not a container.
Deny by default A workspace reaches DNS and HTTPS. Your network, your cloud metadata and the host itself are refused.
Its own keys Secrets come from the profiles a workspace carries, never from whoever starts it.

The 78-second version

An illustrated explainer, with narration: why an agent belongs in a box of its own, with only the code it needs, while your keys stay outside it.

Every environment in one place

Who has what, what it runs on, and what it costs you in CPU and memory. People create their own workspaces without filing a ticket, and each one is private to them.

The throughthewire.dev hub overview: tiles counting workspaces, running VMs, profiles and volumes, and a graph linking each workspace to its base image, its devtools and the profiles and volumes it uses, with the webterm-dev workspace's links highlighted.
The hub, showing one node. Workspaces on the left are built from an image; on the right are the profiles and storage they use.

Book a demo

We'll show it running on a real node: workspaces, the hub, an agent hitting the walls. Tell us a little about your setup and we'll reply with a few times that work, and help you work out where it should run.

Where would you want it to run? optional

Fully managed: we run everything. Hybrid: we run the control plane, the workspaces run on your hardware. Self-hosted: all of it in your environment.