Why we built YourKey
The industry is focused on making agents more capable. Far less attention has gone to what determines whether you can responsibly delegate to one: what it is permitted to access, who authorized that, and what it did.
That gap is why YourKey exists. Issuing an agent broad credentials and reviewing logs afterwards is not a control. The missing piece was never intelligence — it is knowing which agent did what, on whose behalf, and under whose authority.
What YourKey does
YourKey is where an agent is put to work under authority you define. The agent is Key: it operates in your community, converses with your members, and carries out the automations you configure. Everything it does runs on permission granted deliberately — limited to what was specified, ended the moment it is withdrawn, and recorded either way. "Who did this, and why were they allowed to?" is a question with an answer.
The company
Bastion Systems LLC is an independent software company. We develop YourKey and operate it on our own infrastructure. The product lives here at yourkey.ai; the underlying infrastructure runs at key-gateway.io, which documents its own automated traffic.
Naming
- Key — the agent your members interact with.
- YourKey — the software the Key runs in: the console, the automations, the approvals. The name states the principle. The Key is yours, as is every permission it acts under.
- Bastion Systems LLC — the company that builds and operates both.
A single product
YourKey has no feature tiers. Every customer receives the same fully featured product. What differs between a gaming community and a company is what they configure and how much they use — not which capabilities they were sold.
Contact
General inquiries, early access, and support: [email protected]. Data requests: [email protected]. Security disclosures are welcome at [email protected]; see also /.well-known/security.txt.