Integrations

What this covers

Integrations are scoped and built as part of your engagement, and delivered on your own deployment. There are no prebuilt connectors: each integration is built against the systems you actually run.

Where a system already has an API, we connect to it. Where it has none, building the API is part of the work.

What an integration includes

Each integration lands on your deployment as three parts.

• An API. The system can be called by other software: asked for what it holds, and given work to do.
• Signed notifications. When something changes, the systems that need to know are notified as it happens, and every message can be verified back to its source.
• A tool surface for AI agents. The same operations are exposed as tools an agent can call, governed by the same permissions as everything else on your deployment.

All three are governed and audited like the rest of the platform.

Systems without an API

Much of an organisation's work sits in systems that were never built to be called: older line-of-business systems, in-house tools, applications whose only interface is a screen. For these, the engagement includes building the API itself. Once it exists, the system takes part in everything above, the same as any other.

How delivery works

Integrations are scoped with you at the start of the engagement. We start with the systems that carry the most weight and add further ones as the need arrives. Each integration that lands is available to everything already connected.

Integrations are built on the same event API the API reference describes. The controls that govern them are on security and trust.