Skip to content
Inside ORION

Six apps, one hub.

ORION runs as a single member hub with six purpose-built apps. Same surface for customers and partners — the data scope changes based on your account type.

01 · PROCESS

Process

Day-to-day ITSM intelligence over your HaloITSM or ServiceNow estate via the official MCP adapter.

DashboardIncidentsProblemsChangesCatalogAssetsReports
Connected and answering questions
02 · KNOWLEDGE

Knowledge

T1 best practice, T2 vendor docs, and T3 your live data — embedded, coverage-mapped, and refreshable on demand.

DashboardDocumentsCoverageSync
T1 + T2 coverage > 80%
03 · PROJECTS

Projects

ORION-native work contexts. Customers run one project. Partners run a project per client engagement.

DashboardProjectsActivity
First project active
04 · MIGRATE

Migrate

Bidirectional ServiceNow ↔ HaloITSM migration. Canonical field mapping, dry-run validation, per-record status.

DashboardJobsRecordsValidationsTemplates
Dry-run passed, job completed
05 · CONNECT

Connect

ITSM adapter connections. Credentials stored as vault references — only the last 4 characters are ever shown.

DashboardConnectorsCredentialsTest
test_status = ok
06 · SESSIONS

Sessions

Read-only history of every AI session. Four-verb audit (explain · route · unlock · act) with human-confirmation gates.

DashboardSessionsActionsAudit
Every action accounted for
Headless by design

AI lives in Claude Desktop or Cowork. ORION is the system of record.

There is no companion panel inside ORION. Live sessions happen in your existing Claude surface; ORION renders the audit log read-only so every explain, route, unlock, and act is accounted for.

See how it works