// INTEGRATIONS
Built-in connections, plus anything with an API.
The systems operations teams run, connected through one integration layer — with widgets and agent actions on top. Including the systems you built yourself.
// WHAT A CONNECTION GIVES YOU
{{ n.type }}
{{ n.tag }}{{ n.body }}
And the rest of your stack
The full catalog is below, across sixteen categories. If a system has an API, it can be reached.
// MCP CONNECTORS
For the system nobody else integrates with.
Every operations team has one — the legacy ERP, the industry-specific platform, the internal tool somebody built years ago and everyone now depends on. Those are usually where the interesting data lives, and usually what no vendor supports.
ORiON connects to them through MCP, an open standard for exposing a tool to an AI. Pick from a catalog of available connectors, or register your own.
Connect from the catalog
Available connectors authorize through a standard OAuth flow in a popup. Enable it, and ORiON can use it.
Add your own
Register a custom connector pointing at your own MCP server — the route for internal systems.
Choose which tools are exposed
A connector may offer many operations. Enable only the ones you want reachable, and turn the rest off.
Works the other direction too
ORiON is itself an MCP server, so an external client can reach your unified data through a personal key you can revoke.
// BY CATEGORY
The systems ops teams actually run.
Sixteen categories, from the ERP down to the tool one team uses. Don't see yours? It connects too — anything with an API can be reached.
// CREDENTIALS
Connected once for the organization, or once per person.
Organization-level
One connection serves the whole team — right for a CRM or ERP where everyone should see the same pipeline. An admin decides which users may use it.
Per person
Email and calendar are authorized by each individual and tied to that identity. ORiON reads your inbox for you, not your colleague's.
Never pooled
Credentials are stored against your organization alone. There is no shared service account spanning customers.
Disconnecting is meaningful, not cosmetic. Signing in to ORiON and granting a system access are treated as two separate acts — so where a provider does both, revoking the data access is recorded independently of the login. Signing back in never silently re-grants what you revoked; it stays revoked until you press Connect again.
// DON'T SEE YOURS
Tell us what you run.
Bring the list of systems your operations team depends on to the call and we'll tell you honestly what connects natively, what goes through MCP, and what would take work.