About
A control plane for agents on machines you own
You give Glion an agent, a model, some tools and a budget. It runs the loop itself, shows every step, and holds a destructive call for a person before it runs. It runs on your network, behind your egress rules, on hardware you own.
Why it exists
An agent that can touch real infrastructure is useful exactly as far as it cannot surprise you. Assistants you talk to in a chat app are years ahead at being assistants, and some say plainly that everyone who can message them shares their owner's authority. Glion is the other shape: an operations console where authority is granted one tool at a time, and a destructive call waits for a person.
It is also built for an estate most tools do not aim at: a mixed, self-hosted one that nobody has a list of. So the first thing Glion does is look, on your own network, and the second is help you connect to what it found, with one scoped token per service. Several projects do one of those jobs well. Glion joins them for that estate, which is the reason for it, not a claim that the gap is large.
How it is made
Candid
It says what happened, including its own bugs. A number it does not have is a dash with a reason, never a zero.
Plain
It says what it means. No marketing verbs, no metaphor where a word would do.
Held
Risky calls wait for a hand on them. Reads run; writes wait when a policy holds them; a destructive call shows its plan and a hash.
Exact
What it claims is checked. The product’s tests turn red when its interface and its rules disagree.
Glion is maintained by one person. It is written down as it goes: what it can and cannot do, and why it is shaped as it is, are in the docs.
Where it stands
Glion is in private preview and Apache-2.0 licensed. Its first release, v0.1.0, is being prepared. Community, the free plan, is everything it does today with no caps; Pro adds support and updates, per deployment. Pricing has the detail.