# The adaptive runtime for agents across your company. Run agents with access to 1,500+ apps, browsers, and sandboxes. Govern what they can do, keep credentials out of model context, and trace every tool call. [Get a Demo](https://composio.dev/contact) · [Trust center](https://trust.composio.dev) ## Available today: tools and execution environments ### Work across company apps Give agents access to 1,500+ app integrations, including Slack, Salesforce, GitHub, Gmail and Microsoft Outlook. Composio handles managed connections and supplies tools agents can discover and use as the task requires. ### Use a browser when there is no API Let agents navigate websites, fill forms and interact with web interfaces alongside their app tools. ### Run code in a sandbox Give agents a remote environment for code execution and file processing. Configure the sandbox separately from app access, or disable it for sessions that do not need it. ### Plan work with reusable skills Composio helps agents discover tools, plan steps and route execution across apps, browsers and sandboxes. Skills supply reusable steps and guidance for recurring tasks. Your application retains ownership of the agent and its orchestration. ### Respond to app events Subscribe to events across connected apps. Composio delivers events to your endpoint with delivery retries; your application starts or resumes the agent. Event delivery retries do not guarantee that downstream business operations run only once. ### Access paid capabilities through one wallet Instant Tools run supported paid-provider actions on Composio's accounts and charge your organization's Composio balance. Allow or exclude eligible tools and inspect charges. Per-session dollar budgets require application-side enforcement. ## Available today: security where agents act ### Scoped permissions Allow or exclude specific toolkits and actions. Composio enforces configured restrictions on execution it manages before the downstream call is made, independently of the model's instructions. An agent's access elsewhere remains the responsibility of that execution path. ### Managed credentials With hosted connections and managed execution, Composio stores credentials, refreshes OAuth tokens where supported, and authenticates provider requests server-side. Your application and model receive results without needing provider tokens. Connected-account reads always redact Composio-managed credentials. For customer-owned auth configs, masking depends on project and platform settings and can be disabled in self-hosted deployments. Do not assume account responses are safe to log. ### Access boundaries Bind each session to the user it acts for and select the connected accounts it can use. Configure sandbox access separately from app tool permissions. Your application remains responsible for its own authorization and content-level safeguards. ### See what ran Execution logs record the user, connected account, tool, status and timing of a call. Tool arguments and results are stored by default. Project settings can limit covered payload storage while retaining execution metadata; sandbox processing and your own application logs have separate retention boundaries. [Session access controls](https://docs.composio.dev/docs/configuring-sessions) · [Token custody](https://docs.composio.dev/docs/security/token-custody) · [Data retention](https://docs.composio.dev/docs/security/data-retention) ### Selected tool approvals (experimental) Selected session tools can request user approval on supported execution paths. This experimental feature has client and sandbox limitations. [Approval support and limitations](https://docs.composio.dev/docs/approvals) ## Agent Firewall Detect prompt injections in tool responses and check agent actions against your access policies. ## Fit the infrastructure your company runs ### Connect enterprise identity Single sign-on supports SAML and OIDC. Enterprise identity integration includes SCIM 2.0 provisioning and directory-group mapping, with support for Okta, Microsoft Entra ID and Google Workspace. Discuss the identity and offboarding requirements for your deployment with the Composio team. [Enterprise identity and governance](https://composio.dev/solutions/ai-agent-governance) ### Choose your deployment Keep your project API key backend-only: it can authorize actions even when provider tokens are redacted. Derive user IDs from authenticated sessions and verify connection ownership before execution; browser- or model-supplied IDs are not authorization. #### Composio Cloud The default hosted deployment. Composio stores credentials and can decrypt them to authenticate provider requests. #### Private VPC An Enterprise arrangement within a private network. Agree storage, operator access, and key ownership; a VPC alone does not establish who can decrypt credentials. #### Self-hosted An Enterprise arrangement in your environment, with Helm support. Your team operates the agreed infrastructure; confirm decryption access, logs, and backups. #### Customer-managed keys A separate deployment arranged with Composio, not a dashboard toggle. A proxy in your cloud handles credentials under keys in your KMS; Composio does not hold the keys needed to decrypt them. [Read the token custody architecture and deployment options](https://docs.composio.dev/docs/security/token-custody). Confirm the deployment design and availability with our team. ### Keep your choice of agent and model Use the runtime through the SDK or MCP. Your connected accounts are managed by Composio rather than tied to one model provider, so teams can use their existing agents without rebuilding authentication for each one. ## Evidence for your security review Composio is SOC 2 Type II attested and ISO 27001:2022 certified. Provider credentials are encrypted at rest, and requests use encryption in transit. Review the current reports and supporting documents in the Trust Center and agree any deployment-specific requirements with the team. [Trust center](https://trust.composio.dev) · Security contact: security@composio.dev ## Runtime at scale - 1,500+ managed app integrations - 50K+ individual tools available - 1B+ tool calls run on the platform - 1M+ accounts connected AWS, Glean and Zoom are among the teams building with Composio. [Read the customer stories](https://composio.dev/customers) ## Put your next agent into production Talk through the systems your agents need to reach, the actions they should be allowed to take and the deployment requirements your company needs to meet. [Get a Demo](https://composio.dev/contact) · [Trust center](https://trust.composio.dev) ## Related pages - [Developer platform](https://composio.dev/developers) - [MCP gateway](https://composio.dev/mcp-gateway) - [Pricing and plan limits](https://composio.dev/pricing) - [Documentation](https://docs.composio.dev) - [App directory: 1,500+ integrations](https://composio.dev/toolkits)