About · Servor
Servor came out of a frustration shared by anyone who has spent a sleepless night on an operation that should have taken five minutes — made worse by a generation of AI agents that will happily fire off rm -rf without blinking. We wanted an agent that thinks before it acts, and proves what it did afterwards. So we built Servor.
Scope
Servor operates the server itself: getting in, running the operation, watching the machine, telling people what is happening, keeping a record of who did what. Everything on the other side of that line stays there on purpose.
In scope
Out of scope
Operate, don't deploy. The two categories sit next to each other — you can ship your application with one tool and run the machine underneath it with Servor.
Principles
They are constraints before they are values: each one shows up in the code as something we cannot do, not as something we promise.
Zero-knowledge is the base architecture, not a line on a slide. The passphrase, the derived key and the private key never leave the browser, and every command is signed there before it is relayed. You do not trust us to guard your credentials — a fully compromised control plane still cannot read them, nor forge an execution.
Every command is classified by risk, approved under the mode you picked, then written down with its output and its exit code. The guardrails reduce the risk of an automated operation; they do not remove it, and the operator stays responsible. What we can do is make sure nothing happens that you cannot read back afterwards.
We write the code we still want to be maintaining in ten years: a stable stack, no framework of the month, no dependency that will be abandoned in two releases. Server operations are not a place for novelty for its own sake.
Our position
An AI agent is not there to replace the infrastructure engineer. It is there to give them their time back — automating what repeats, structuring what is complex, handing control back where it matters.
Which also means saying the unglamorous part out loud: the copilot proposes, you approve, and you remain responsible for what runs on your machines. The guardrails make a bad command far less likely. They do not make it impossible.
Roadmap
This is a state of the code, not a launch calendar. Nothing below is dated, and nothing is listed before it works.
Shipped
V1
Next
No dates
We are not announcing dates — what is written here is what runs.
A question, a suggestion, a complaint?
One address, read by the people who write the code.