Carrel

lab machines, asked for in words2026GoProxmox VEMCPKeycloakEVPNCaddy

A carrel is the desk a library sets aside for one graduate student. Carrel gives every WinLab member their own corner of the lab's Proxmox VE cluster.

Members never touch Proxmox. They tell their agent what machine they need, and one MCP endpoint creates it and returns an SSH line.

From there the same endpoint gives the machine a domain, opens its ports and deploys its code on every push.

Ask for a machine

The member says what the machine is for. The agent picks an image and a size, calls one tool and waits for the answer.

The answer comes when the machine is ready to use: it has booted, initialized and answered over SSH. In our own test that took 29 seconds. The agent writes the SSH alias into the member's config, so the next line just works.

The member says what the machine is for.

A desk of your own

Every member gets the same budget, and spends it as they like: 8 small machines, or one large one. A project group gets a second budget of its own.

A machine is a full VM (Debian or Ubuntu, with Docker and cloud-init) or a lighter container. Each member also has private networks, so machines talk to each other and to nobody else.

The default: enough for a bot or a small service.

Machines
8, with 8 vCPU, 16 GiB of memory and 100 GiB of disk between them.
Names
10 domains under the member's own name, with HTTPS.
Ports
10 public TCP or UDP ports.
Networks
4 private networks.
Snapshots
4 per machine.

Publish and deploy

One call puts a service on the internet: a domain with a certificate, or a public port. Names outside the member's own and fixed ports go to an admin as a request.

A repository on GitHub links to a machine once. After that every push builds, switches the machine to the new release and watches its health for 60 seconds. A failing release rolls back by itself.

A push to the linked branch starts it.

Keep, pause, put away

A machine does not have to run to be kept. What a member is not using stops counting against the cluster, and comes back as it was.

Snapshot
Saves the disk, and rolls back to it.
Pause
Holds a VM in memory and resumes it where it stopped.
Freeze
Moves a stopped machine to backup storage. Thaw restores it with the same name and address.
Resize
Changes CPU, memory and disk.
VPN
A WireGuard profile into the member's private networks.
Console
A link to the machine's screen in the browser, when SSH is not enough.

How it is built

The control plane is one Go service. It serves MCP, signs members in with the lab's Keycloak account, checks every request against the quota and runs it as a durable job, so a dropped connection never loses a machine.

Under it are the cluster's own parts: Proxmox VE for machines, EVPN and VXLAN for each member's networks, and Caddy for HTTPS. A reconciler compares the cluster with the records every 5 minutes.

The member's agent calls one MCP endpoint, signed in with the lab account.

In numbers

Carrel has run the lab's machines since October 2026. These are from its public status page on 2026-11-12.

Cluster
4 nodes with 160 CPU threads, 503 GiB of memory and 2,125 GiB of disk.
In use
30 machines for 11 accounts.
Tools
84 MCP tools: 66 for members and 18 for admins.

Details