Integrations

Two ways to integrate.

Use the platform as it ships — modules, connectors and AI interfaces ready to wire up — or extend it with your own services on the SDK. Either way, you stay under the same identity, policy and audit contract.

Pick your path

Pick the path that fits the team.

Path one

Use the platform.

Connect the systems you already run through the application — identity providers, document sources, knowledge bases, communication tools, line-of-business systems. Configure agents, scopes and processes without writing code.

  • Identity federation with EntraID, Okta, Keycloak and others
  • Document sources — SharePoint, file shares, custom drives
  • Communication — Microsoft 365, Slack, Teams
  • Models — bring your provider or use what's bundled
Path two

Build on the SDK.

When the platform doesn't ship what you need, extend it. The .NET SDK lets your team write services, integrations and process modules that run inside the platform — same identity, policy and audit surface as everything else.

  • .NET SDK for services, integrations and modules
  • Custom modules deployed on your tenant
  • Same identity, policy and Evidence Pack contract
  • Plugs into the Open Orchestrator alongside managed agents
What's next

Developer documentation is coming.

We're publishing the SDK reference, integration guides and example modules shortly. If you'd like an early look at the surface and timelines, ask us — we'll walk you through.

Request early access

Have an integration in mind?

Tell us what you'd want to connect — we'll show you whether it's a configuration job or an SDK build.