Company
Xenon exists because the tools for looking after machines were built for enterprises with an army — and everyone else, from the ten-person shop down to one person with one computer, got dashboards and a scripting console.
AI is finally good enough to do the tedious middle of looking after a machine — the looking, the checking, the correlating — but only if the boundaries around it are engineered, not promised. That’s why the tagline isn’t a slogan, it’s the architecture: safety is in the software. Nothing runs that isn’t in a reviewed catalog of actions with typed, bounded parameters — there is no shell, and no path to arbitrary command execution. A human yes stands in front of every change, an approval covers exactly one machine, and there is a record of everything.
The self-hosted Enterprise Edition exists today: an organization runs it on its own servers — Console, Agents, approval queue, audit trail. A hosted edition for individuals — a personal assistant that helps with your actual work and looks after the machine it runs on — is being built now. Same codebase, same rules about what software may do to a machine.
One person. Zackery Hodges designs Xenon and writes it — direction and engineering both — and answers the support inbox himself. It ships fast because the product is also his own daily driver.
Xenon is a personal project, and it’s better to say that plainly than to imply a bench that isn’t there. What it means in practice: the person who answers you is the person who can act. Write in, and you’re talking to the person who built it.
Contact
Questions, product help, and Enterprise Edition enquiries — both editions, one inbox, answered by the person who builds it.
support@xenon.solutions