52INTEGRATIONS

Integration Roadmap

First secure where agents are created and authenticated; then where they take consequential business actions.

Priority: P0
Phase: MVP → Phase 3
Primary owner: Product / Partnerships
Status: Blueprint

Objective

Prioritize integrations by control value, installed base and ability to produce differentiated agent visibility. Avoid chasing logos before the platform has repeatable connector mechanics.

What to build

Wave 1 — AI/model: OpenAI, Anthropic, Azure OpenAI, Google Gemini/Vertex, AWS Bedrock.
Wave 1 — Identity/cloud/dev: Microsoft Entra, Okta, AWS, Azure, Google Cloud, GitHub.
Wave 1 — Tooling: MCP gateway/server integrations, generic HTTP/OpenAPI proxy.
Wave 2 — Enterprise SaaS: Microsoft 365, Google Workspace, Salesforce, ServiceNow, Slack/Teams.
Wave 3 — ERP/PAM/SIEM: SAP, Oracle, Workday, CyberArk, Splunk, Microsoft Sentinel and others based on customer demand.

Implementation decisions

Gate each connector on real customer use case, not logo value.
Publish supported read/write capabilities and limitations.
Create certified partner path for third-party connectors once SDK stabilizes.
Maintain deprecation/versioning policy.

Definition of done

Wave 1 supports end-to-end discovery and at least one enforceable action path.
Wave 2 is driven by paid pilots or repeat demand.
Connector roadmap is reviewed monthly against pipeline.

Success metrics

ARR influenced by integration
Connector active tenants
Usage per connector
Demand-to-delivery cycle

BUILD ORDER

First secure where agents are created and authenticated; then where they take consequential business actions.