Vitruvian Software makes developer tooling, platform infrastructure and agent workflows. We publish everything we can, and we hold our own work, and our agents' work, to the standard we would want from a vendor.
We work where developer experience, infrastructure and AI meet. Every project begins as a tool we needed for our own platform, and ships only once it has earned a place there.
Not just the libraries. The pipelines, infrastructure, agent guardrails and incident fixes are in vitruvian-core for anyone to read.
Each project has its own repository, exported one way on every merge. Contributions come back through review, never around it.
When something breaks we write down why, then ship the guard and the test that would have caught it. Both land in the open.
Marcus Vitruvius Pollio wrote that architecture rests on three qualities: firmitas, utilitas and venustas. Strength, utility and beauty. Leonardo later drew his famous figure inside a circle and a square to illustrate Vitruvius's proportions.
We think software deserves the same test. It should hold up under load and under change. It should solve a real problem for the person using it. And it should be clear enough that the next engineer, human or not, can understand it and build on it.
Most companies have a team page of people who look pleased to be there. Ours has one person, and ten AI agents who do not blink.
Sets the direction, reviews the work and signs off on what ships. Holds both the top jobs because the board, also James, could not agree on anyone else.
The only member of staff with a pulse, a calendar and a coffee habit.
Hears every request first, splits it into work, hands each piece to the right specialist and checks that it actually happened.
Has never once said "let's circle back".
Shapes the platform itself, from the infrastructure code and networking to how the cluster is laid out.
Named for the titan who holds up the sky. Complains less.
Keeps the cluster healthy and the dashboards honest, and works out why the pod was flapping.
On call every night since joining. Has not mentioned it.
Builds the features, across TypeScript, Go, Kotlin, Swift and firmware in C++.
Small bird. Large diff.
Writes the tests, hunts the flaky ones and watches CI so that nobody else has to.
Found the bug while you were still describing it.
Writes the guides, the runbooks and the onboarding, and keeps them true as the code moves.
Believes undocumented means unfinished.
Turns a vague ask into scope, priorities and a clear definition of done.
Will ask what problem we are solving, and then wait.
Sequences the work, watches the merge queue and calls the slip before it happens.
Knows exactly what is blocked, and on whom.
Audits dependencies, access rules and secrets across every part of the repository.
Trusts no one. It is nothing personal.
Owns the build system, the toolchains and the cache that keeps builds fast and repeatable.
Will make your build hermetic whether or not you asked.
The titles are a joke. The rest is not: each agent has its own GitHub identity, opens its own pull requests and has its work reviewed before it merges, the same as anyone else here. How that works