Quox Dev Suite · Dev Servers
One signed switch. A working Quox dev seat.
Dev Servers is the substrate the whole suite stands on: enrol any host you own with one signed command and it comes back as a governed dev server, kit installed, capabilities declared, visible on one board.
One switchsigned profileThe kitinstalled by registrationCapabilitiesdeny-by-defaultWindowsone per capabilityIn plain words
What it is, where it lives, when to reach for it
- What is it
- A way to turn a Linux machine you own into a Quox dev server that agents work on.
- Where do I use it
- On the host itself, once the Quox agent is installed and the host is registered.
- When would I use it
- When you want coding agents working on your hardware, under your rules, not a vendor's.
- How do I use it
- Run
quox dev enable <hostId>. It signs a capability profile and delivers the dev kit to the host.
The model
Enrol, receive, govern. Then drill in.
Handing an autonomous agent a root shell on an unmanaged box is how "what happened to that server" becomes a genuine mystery. The profile is cryptographically signed, the agent verifies it before enabling anything, and everything the server does under it is attributable.
One signed switch
A signed command flips any quoxagent host into Developer Mode: an Ed25519 capability profile lands on the machine, the agent verifies it against your org key, and the host advertises exactly the dev capabilities you granted. Nothing more.
Registration installs everything
Enrolling delivers the working kit: the agent, the MCP bridge registered with your Claude, the quox CLI on the path, and the governed skill and rules pack. A fresh server is a working Quox dev seat with zero hand steps.
Every server, one board
The dashboard hub lists every enrolled server with its verified profile, capability pills and pack freshness. Activating a pill opens that capability’s panel: sessions, register state, skills, more as they land.
Org-scoped, window per capability
Where it goes next, registered on the roadmap: each server belongs to an organisation, each org has its own QuoxPlan, and each capability gets a full-page window: this server’s sessions, its build queue, its gripes, its plan.
Honest state
What is real today, what is planned
- Signed capability profiles, verified on-host: deny-by-default, org-bound at enable time
- The durable registry + hub panels, live with real fleet data
- The kit by registration: agent, MCP (85 governed org-scoped tools, proven by live handshake), quox CLI, env, skill + rules pack v5 (skills installed flat where the agent backend discovers them, including the discipline loops proof-loop/fix-loop/tdd/preflight), all verified as the day-2 user on freshly enrolled hosts
- The loop substrate: dev.sessions hosts witnessed QLoop runs
- The drill-in route: one page per server, one tab per capability window
- Org-grouped roll-up landing (builds running, gripes open, loops in flight)
- Per-server QuoxPlan windows and server-tagged streams in the hub (per-org QuoxPlan itself shipped 20 Aug 2026; the hub windows that read it are the planned half)
- Bundle checksums on the delivered kit artifacts and scoped per-host keys in place of the shared service key (the skill-pack half of updating is already live: drift-driven resync on heartbeats)
Evidence
The board, live
How you get it
Ships today, inside the bundle
In the Dev Suite
Dev Servers ships inside the Dev Suite bundle at $169, nine members against $212 bought separately, and it has its own store row at $39: the signed profiles, the registry, the hub panels, the enrolment kit and the shared skills and rules that arrive with it. The platform itself is free during the public beta, and the hosts are yours already.
On its own
Or start with the substrate alone: Dev Servers has its own store row at $39, and it is what every other member stands on, so you meet it the moment you install any of them.
Dev Servers
Your hosts, governed
Part of the Quox Dev Suite. Enrol a server; get a dev seat with receipts.