ACBDiDATAP.AI
Integrations

One Engine.
Every Enterprise AI Surface.

Insert a regulator-grade AI gate into the SaaS platforms your customers already pay for — Control-M, Salesforce, ServiceNow, SAP, Dynamics, Workday. Same engine. Same audit story.

See the live integration →Talk to us →

Why one engine, many adapters

We don’t build a separate governance product per platform. We build one engine and ship thin per-platform adapters that fit each ecosystem natively.

🧩

One engine, many fronts

Same /v1/governance/gate REST API behind every adapter. The audit story is identical across Control-M, Salesforce, ServiceNow, SAP, Dynamics — just different caller_system tags.

🌐

Customer-VPC deploy, always

Engine runs inside your AWS / Azure / GCP / on-prem account. Prompts and audit data never cross your perimeter. Each adapter is a thin REST/Action/Connector — not another SaaS to security-review.

🧠

Framework-agnostic on both sides

Adapters don't care if your AI is AG2 / LangChain / LlamaIndex / OpenAI SDK / native Joule / Agentforce. The gate evaluates the prompt + workload context, not the framework.

📝

Cross-platform audit pane

Every gated call lands in fct_ai_guardrail_decision tagged with caller_system. Your CCO sees AI activity across every integrated SaaS in one query — not 6 vendor dashboards.

Available integrations

Live · in design partnership · on roadmap. Click any to see the adapter shape and buyer persona — or request to shape the design.

⚙️

BMC Control-M

Batch orchestration
● Live

Insert a regulator-grade AI gate into any Control-M flow in 5 minutes. Standard Web Services job. No plugin build.

Adapter: Web Services job → POST /v1/governance/gate · Application Integrator package on roadmap.
Who buys: Batch ops · platform engineering · AI governance leads in regulated banks / insurers / gov.
See the demo + audit row →
☁️

Salesforce + Agentforce

CRM · Agentic AI
◐ In design partnership

Gate every Agentforce action against APRA, ASIC, OAIC + 13 more — without leaving the Salesforce trust boundary.

Adapter: MCP server (Model Context Protocol) hosted in customer VPC · Apex callable wrapper · AppExchange managed package on roadmap.
Who buys: Salesforce architects · CCOs at AFSL/insurance customers · AI Cloud champions.
Talk to us about shaping this →
🛎

ServiceNow + Now Assist

ITSM · Workflow
◐ In design partnership

Drop a Flow Action into any Now Assist or AI Agent step — APRA / NSW AIAF / OAIC citations land in the same record.

Adapter: Custom Flow Action · spoke for Now Assist · IntegrationHub workflow templates · ServiceNow Store listing on roadmap.
Who buys: ServiceNow practice leads · Public-Sector CCOs (NSW, federal) · AI Control Tower owners.
Talk to us about shaping this →
🏢

SAP BTP + Joule

ERP · Business AI
◐ In design partnership

BTP destination + Joule extension that gates SAP-originated AI calls before they touch master data or financial postings.

Adapter: BTP destination · Joule skill wrapper · CAP service binding · S/4HANA RAP intercept on roadmap.
Who buys: SAP CoEs · CFO offices in regulated industries · BTP architects shipping Joule pilots.
Talk to us about shaping this →
🟦

Microsoft Dynamics + Copilot

ERP · CRM · Copilot Studio
◐ In design partnership

Power Platform connector + Copilot Studio plugin so Dynamics-bound AI actions are gated against AU and global frameworks.

Adapter: Custom connector (Power Platform) · Copilot Studio plugin · Dataverse plugin step · Microsoft AppSource on roadmap.
Who buys: Dynamics partners · Microsoft AI Cloud customers · Public-sector tenants under DTA AI Assurance.
Talk to us about shaping this →
👥

Workday + AI

HCM · Financials
○ On roadmap

Gate Workday-embedded AI features (skills inferences, recruiting AI, anomaly detection) against Privacy Act, OAIC, and HR-specific frameworks.

Adapter: Studio integration · Worktag-aware audit · Workday Marketplace listing under evaluation.
Who buys: Workday HCM/FIN customers in regulated industries · CHROs concerned about AI in hiring decisions.
Talk to us about shaping this →

Don’t see your platform?

The engine is REST. If your platform can call an HTTPS endpoint, we can adapt to it. We’re especially interested in talking to customers running Oracle Fusion, Workday Studio, Pega, Appian, or in-house orchestrators.

Tell us what you run