01Integrations

Connects to the systems you already run.

Lattice governs the boundary between an agent and a system of record, so an integration is a category of connection rather than a logo. Availability is stated for every item, and at this stage none of them is available.

02How integration works

Five kinds of connection.

Only the first kind needs to sit on the hot path. Everything else is asynchronous, which is why adding Lattice does not make an agent slower to reason.

Boundary integrations
Where an action is intercepted: SDK, gateway, MCP shim. These do the governing.
Telemetry integrations
Where runs come from: OpenTelemetry, SDK spans. These do the observing.
System integrations
What an agent acts on: CRM, ERP, payments, repositories, databases.
Identity integrations
Who the actor is: SSO over SAML or OIDC, with group-to-role mapping.
Notification integrations
Where an approval request goes: webhooks, and communication tools over them.

18Integrations

Connects to the systems you already run.

Categories rather than logos. Nothing here is presented as a completed integration unless it is marked available — and at this stage, none are.

Models

Model providers reached through the gateway.

  • Hosted model providersDesigned
  • Cloud AI servicesDesigned
  • Self-hosted inferenceRoadmap
  • Embedding providersDesigned

Infrastructure

Where the control plane runs.

  • AWSDesigned
  • AzureDesigned
  • GCPDesigned
  • Private deploymentRoadmap

Business systems

Systems an agent can change.

  • CRMDesigned
  • ERPDesigned
  • Support deskDesigned
  • CommunicationRoadmap

Developer systems

Engineering surfaces.

  • Git providersDesigned
  • REST APIsDesigned
  • DatabasesDesigned
  • CI pipelinesRoadmap

AI infrastructure

The agent runtime itself.

  • MCP serversDesigned
  • Vector storesDesigned
  • Inference endpointsDesigned
  • OpenTelemetryDesigned
Full integration ecosystem

Available · connected today · Designed · interface defined · Roadmap · planned, not built

03In the console

Search, status, connection detail.

How the integration surface appears inside Lattice: each entry shows what it is, whether it is configured, the scopes it requests and when it last synchronised.

Lattice / IntegrationsPRODUCTIONIllustrative data
Integrations
Hosted model providersModelsNOT CONFIGUREDDesigned
Cloud AI servicesModelsNOT CONFIGUREDDesigned
Self-hosted inferenceModelsAVAILABLERoadmap
Embedding providersModelsNOT CONFIGUREDDesigned
AWSInfrastructureNOT CONFIGUREDDesigned
AzureInfrastructureNOT CONFIGUREDDesigned
GCPInfrastructureNOT CONFIGUREDDesigned
Private deploymentInfrastructureAVAILABLERoadmap
CRMBusiness systemsNOT CONFIGUREDDesigned
ERPBusiness systemsNOT CONFIGUREDDesigned
Support deskBusiness systemsNOT CONFIGUREDDesigned
CommunicationBusiness systemsAVAILABLERoadmap
Git providersDeveloper systemsNOT CONFIGUREDDesigned
REST APIsDeveloper systemsNOT CONFIGUREDDesigned
DatabasesDeveloper systemsNOT CONFIGUREDDesigned
CI pipelinesDeveloper systemsAVAILABLERoadmap
MCP serversAI infrastructureNOT CONFIGUREDDesigned
Vector storesAI infrastructureNOT CONFIGUREDDesigned
Inference endpointsAI infrastructureNOT CONFIGUREDDesigned
OpenTelemetryAI infrastructureNOT CONFIGUREDDesigned
What the status words mean
● Available
Built, connected and usable today. No item on this site carries this status yet.
◇ Designed
The interface and data model are defined. Implementation is not complete.
○ Roadmap
Planned, not designed in detail and not built.

Put a control layer around your AI systems.

Connect your agents, understand their behaviour, define their boundaries and operate AI systems with a clear audit trail.