// INTEGRATIONS
Agents working in your ERP and everything around it.
ORiON connects to the ERP, CRM, billing, payroll and email your finance and operations team already runs, so agents can take on any manual ERP process, for example the re-keying and matching between them. You can also ask about any of it.
ORiON connects to NetSuite, SAP, Dynamics 365, Oracle, Sage Intacct, Acumatica, Infor, Epicor, M3, Odoo, QuickBooks and Xero, and to the CRM, billing, payroll, Google Workspace, Microsoft 365 and Slack around them. Anything else with an API connects through the Model Context Protocol, and websites with no API at all are reachable through the ORiON Companion.
// 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. No migration and no new ERP modules: if a system has an API, it can be reached.
// MCP CONNECTORS
For the system nobody else integrates with.
Every finance and operations team has one: the legacy ERP, the industry-specific platform, the internal tool somebody built years ago that the close still depends on. That is usually where the manual copying happens, 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 point it at your own server.
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. This is the route for legacy and 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 finance and ops teams actually run.
Sixteen categories, from the ERP down to the tool one team uses. Don't see yours? Anything with an API can be reached, most of it through MCP.
// CREDENTIALS
Connected once for the organization, or once per person.
Organization-level
One connection serves the whole team, right for an ERP or CRM where everyone works from the same records. 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 your ERP and the systems your finance and operations team copies data between, and we'll tell you honestly what connects directly, what goes through MCP, and what would take work.