INTEGRATIONS
Three ways to connect Ackuity to your agents.
Ackuity is the Agent Execution Control Switch AI builders add to their agents, verifying every action before it runs. Pick the way in that fits where your agents run. Everything stays in your cloud account.
SIDECAR · DEEPEST COVERAGE
In the execution path.
Checks every action before it runs, and can stop it.
API INJECTION · PLATFORM AGENTS
Inside agent platforms.
For agents built on hosted platforms where you cannot run a sidecar.
EVENT PULL · OBSERVE-ONLY
From the telemetry you already collect.
The fastest way to start. Ackuity reads agent events and reports findings without blocking anything.
AGENT PLATFORMS
Hosted agents and code-first frameworks.
The Ackuity platform view includes Microsoft Copilot Studio, Microsoft 365 Copilot, LangChain and LangGraph. Copilot Studio uses API injection. The Kubernetes sidecar is a separate deployment route. Confirm the action paths in scope for your environment.
IDENTITY, POLICY & SECURITY
Work with your existing controls.
Connect identity context from Okta, policies through Open Policy Agent and security operations through Splunk. These adjacent tools keep their roles. Ackuity uses the relevant context to assess agent actions and connects findings to your security workflow. Configuration and supported data flows depend on the integration.
DATA & COLLABORATION
Follow the action to the data.
SharePoint, PostgreSQL, SQL databases, Snowflake, MongoDB and Databricks are part of the agent activity Ackuity can assess at the configured integration boundary. Access to a system does not imply coverage of every operation. Confirm the connector, permissions and action paths during the assessment.
YOUR QUESTIONS, ANSWERED
Before you take the next step.
Does Ackuity require a sidecar for Microsoft Copilot Studio?
No. Ackuity supports API injection for Microsoft Copilot Studio, where an agent-side container cannot run. The sidecar is a separate option for Kubernetes agents. Confirm which actions the API integration covers; event pull is observe-only.
Which way in should we start with?
Start with event pull if you want results fast. It reads the telemetry you already collect and changes nothing. Move to the sidecar or API injection when you want Ackuity to stop actions before they run.
Does Ackuity work with NVIDIA OpenShell?
An integration is in development. Ackuity is building it on OpenShell’s supervisor middleware, so the supervisor can ask Ackuity for a verdict on each outbound action.
Do any of these need agent code changes?
No. The sidecar reroutes traffic with an init container, API injection works through the platform, and event pull reads existing telemetry.
Does Ackuity replace our gateway, IAM or SIEM?
No. Ackuity works alongside them and feeds them the context they lack about each agent action.
NEXT STEP
Not sure which way in fits?
Tell us where your agents run, and we’ll suggest the fastest start.