BatonX / Integrations

Integrate through adapters, govern through one model.

BatonX uses adapter boundaries so agents, model providers and enterprise outputs can evolve without fragmenting the core governance model.

Scope your integrations Review support status

Agent adapters

Project sources

BatonX

One governance model

IdentityPolicyAudit

Approved models

Customer event systems

Conceptual adapter model · support varies by integration

Support status is part of the integration.

Claude Code and Codex CLI are supported agents. Additional agents are evaluated against the same session, policy and audit contract.

Supported agent: Available for governed agent sessions. Confirm the version and capability scope for your pilot.
Planned: Future evaluation; not currently presented as supported.
Architectural direction: A defined integration model. Specific products, endpoints and capabilities require validation.

Support status is part of the integration.
Integration	Status	Scope and validation boundary
Claude CodeCoding agent	Supported agent	First supported agent. Read the scope Use Claude Code’s native workflow within a governed BatonX session. Agree the version and required workflow capabilities during pilot scoping.
Codex CLICoding agent	Supported agent	Supported coding-agent adapter. Read the scope Use Codex CLI in governed BatonX sessions with shared policy and audit foundations. Agree the version and required workflow capabilities during pilot scoping.
Additional coding agentsCoding agent	Planned	Further adapters are evaluated individually. Read the scope The architecture is vendor-independent. New agent adapters need their own capability and compatibility validation before being presented as supported.
Cloud, private and internal modelsModel provider	Architectural direction	Approved compatible endpoints; capability-based support. Read the scope No blanket provider compatibility is asserted. Endpoint, model, region and required capabilities must be reviewed and validated for the intended workflow.
Enterprise identityIdentity	Architectural direction	Enterprise IdP integration; SCIM and controlled JIT are targets. Read the scope Specific identity-provider connectors and provisioning flows require validation. Provisioning does not automatically grant access to projects.
Customer secret-management systemsSecrets	Architectural direction	Customer-owned secrets and credential separation. Read the scope Validate the chosen secret-management integration and its capability scope. Brokering or proxying keeps long-lived credentials outside the agent where technically possible.
Repositories and MCP toolsProject and tool sources	Architectural direction	Authorised project sources and centrally governed tools. Read the scope Source and tool integrations are approved explicitly. Specific connectors and tool capabilities need validation against the project and policy scope.
Webhooks, SIEM/syslog and event streamsEnterprise outputs	Architectural direction	Standard, versioned event outputs; validate each destination. Read the scope The product defines signed webhook and approved security-event outputs. A named SIEM connector or downstream notification service is not presented as validated without a compatibility record.

Approve a destination. Validate its capabilities.

Route requests to approved third-party, private or internally hosted model endpoints. Provider support is capability-based and must not imply identical behaviour across every model.

Adding an adapter can extend the platform without replacing the shared governance model. It does not make every LLM immediately compatible or supported.

Your event workflows. A standard output boundary.

BatonX produces standard, versioned security events. Customers can route them through secure webhooks, SIEM/syslog or event infrastructure to Slack, Teams, email, SMS or incident systems managed by the customer.

BatonX events
Structured security and operational events.
Approved output
Signed webhook, SIEM/syslog or event infrastructure; destination compatibility is validated.
Customer-managed workflow
Notification delivery and incident handling remain with your systems.

Your enterprise identity.

Identity integrations connect organisation and project entitlements to the governed workflow. SCIM and controlled JIT provisioning are target capabilities; individual IdP support needs validation.

Your secret-management boundary.

The product is designed to integrate with enterprise identity and secret-management systems while preventing provider credentials from being exposed to the agent runtime.

Explore customer-managed deployment Review the security boundary

Validate the connections your workflow needs.

Bring your agent, approved model destination and enterprise integration requirements. Define a pilot with a clear, testable compatibility scope.

Scope your integrations