What Gatelion is
AI agents can now read and change the systems your business runs on: they look up stock, place orders, book flights, refund payments. Gatelion sits between those agents and your systems. It decides what each agent may do, asks a person when a call matters, and records everything that happened.
An agent asks
Gateway
What happens
inventory.list
Allowed: runs at once, result returned
purchase_orders.create
max_total 12,500
An approver decides, then it runs once
purchase_orders.cancel
No rule allows it: never reaches the system
An agent never talks to your system directly. It calls a Gateway, which checks every call against your policy before anything is sent:
- Allowed calls run at once, and the agent gets the result.
- Calls that need approval wait until a person in your organization approves the exact request. Then they run once, unchanged.
- Everything else is denied and never reaches your system.
Two ways to use it
Your own agents, in your own systems. Your company builds or buys agents that work in your ERP, CRM or internal APIs. You decide which operations each agent may use, for whom it may act, and which calls need a colleague's approval. This is how most organizations start.
Your customers' agents, using your services. You run a service, like a booking portal or a shop, and your customers want their own AI assistants to use it for them. Each customer signs in with your existing login and gives the agent permission. Calls that matter wait for the customer's own confirmation. See Your customers' agents.
The parts
| Part | What it does | Where it runs |
|---|---|---|
| Console | Where your admins connect systems, choose tools, write policies and manage agents, and where approvers decide and auditors look back. | This website |
| Control Plane | Keeps your organization's configuration, decides approvals, and keeps the audit trail. | Run by Gatelion |
| Gateway | The gate. Agents connect to it over MCP, it enforces your policy, and it calls your systems. | In your network, or hosted by Gatelion |
A Gateway only ever connects out: it fetches your signed configuration from the Control Plane every 15 seconds and reports what happened. Your systems' secrets stay with the Gateway.
What makes it safe to say yes
- Default deny. A call that no rule allows doesn't run. An operation of your system isn't a tool until you add it, and a new tool does nothing until a rule allows it.
- Exact approvals. An approver sees the exact values the agent sent, and the approval is bound to them. If anything changes, the approval no longer counts.
- Separation of duties. The person an agent acts for, the agent's owner and whoever issued its token can't approve its requests.
- No silent retries. A write that may or may not have happened is marked unknown and shown to a person, never sent twice.
- A trail you can verify. Every request, decision and result is recorded in an append-only, hash-chained audit trail that the console can check for gaps or edits.
Where to go next
Gatelion is free to use. The usual limits are in Limits and defaults.
- New here? Read How a call is governed, then follow the Quick start. It uses a public test API, so you can try everything before you connect your own systems.
- Setting up for your organization? Start with Gateways and Connect a system.
- Building an agent? Go to Connect an MCP client.
Still stuck? Contact support from the console.