Skip to main content
Tesser has three parts. Your laptop holds the code, the agent, and the browser. Boxes in the cloud run your software. A small control plane keeps track of which boxes exist, where their dependencies point, and which should be asleep. Files and terminal output go straight between laptop and box over SSH. The control plane gets ids, ports, and states, never your files.

The laptop has the only copy that matters

Every command that runs something on a box copies your worktree there first, sending only what changed. The box’s copy is overwritten, never merged back. So editing files on a box does nothing lasting, and removing a box loses nothing you can’t get back: the code is on your laptop, and setup can install the rest again. Only data that lives just on the box, like a local database, goes with it. That is why Tesser can put boxes to sleep and remove them freely.

What runs on a box

Each box runs one Tesser process, boxd, next to your software. It starts the dev server, writes its output to a log, forwards dependency ports, and tells the control plane the box is alive. It does not restart a crashed server. You run tesser dev again, so every running process traces back to someone who started it. A workbench is the same machine with no server on it.

Names, not addresses

A manifest says 5001 = "api", never where api is. Each box has a small routing table: the org’s shared instance of each service, plus any wires its owner set with tesser wire or tesser dev api web. A dependency with neither reaches the owner’s own box of that service from the same worktree. boxd listens on the dependency ports and forwards each connection to the right box. Your app sees a plain localhost port: no SDK, no env convention, no DNS. Shared instances belong to the org and can’t be wired. So they look the same for everyone and never reach someone’s half-done branch.

The control plane mostly turns things off

Nothing in the cloud starts a service nobody asked for. Every dev server was started by a person, an agent, or a CI job. The control plane’s own jobs are putting idle boxes to sleep and removing boxes that slept too long. When a box wakes, a server that was running comes back. The one exception is the warm pool. tesser pool target keeps a few booted boxes of a size ready, replaces one when it is claimed or dies, and stops once nothing has needed one for an hour. A pool box runs nothing until a make, exec, or dev claims it.

What stays on your laptop

Your agent runs on your laptop, not on a box. So does git: the laptop sends the box the commits it needs, and boxes never fetch from GitHub, so no box holds a credential that can read or push your repo. Security and data flow has every hop your code takes and everything the control plane receives.