Run it in your environment
Deploy the connector engine, API, and dashboard with your infrastructure, region, and retention controls.
Open source · Composio alternativeThe open-source Composio alternative,
The open-source Composio alternative,
self-hosted by you.
Open Connector is an open-source Composio alternative for teams that need to self-host their AI integration layer. It performs the OAuth handshake, seals tokens in an AES-256-GCM encrypted vault, and writes a tamper-evident audit record for every call. It's drop-in compatible with the Composio SDK: point @composio/client at your host by changing one baseURL and your existing agent code runs unchanged.
Built for teams that have to keep credentials in their own infrastructure — regulated industries, data-residency rules, and anyone whose security review won't allow user tokens in a vendor's cloud.
Why teams switch
Keep the integration layer where your security controls already live.
An open-source Composio alternative is most useful when the hosted model is the constraint: data-residency requirements, credential ownership, or a security review that requires your team to operate the OAuth and audit boundary. Open Connector is built for that case, while preserving the Composio SDK calling model.
Keep custody of credentials
OAuth tokens are stored in your encrypted vault and each integration call is recorded in your audit trail.
Migrate without rewriting agents
Point the existing @composio/client SDK at your Open Connector host and keep the same integration calls.
Open Connector vs Composio
Same agent workflow. You keep the keys.
Both manage third-party credentials so your agents never touch raw secrets. The difference isn't how many integrations we list — it's who holds the credentials: Open Connector's integration layer is open source and runs in your environment, so your users' tokens never leave your infrastructure.
| Capability | Open Connector | Composio |
|---|---|---|
| License | Open-source core (AGPL-3.0); optional commercial EE add-ons | Only the SDK is open source (MIT); the integration platform is proprietary |
| Self-hosting | Free — self-host the whole core (engine, API, dashboard) on your infra | Hosted SaaS by default; on-prem only on the paid Enterprise tier |
| Where credentials live | Your environment — AES-256-GCM vault, nothing leaves your infra | Composio's cloud |
| SDK compatibility | Drop-in: point @composio/client at your host, change one baseURL | Native |
| Audit trail | Tamper-evident, hash-chained record for every integration call (free in core) | Limited / vendor-controlled |
| Pricing | Free to self-host; pay only for optional EE features | Usage-based paid tiers |
| Data residency & compliance | Full control — your cloud, your region, your retention | Bound to vendor cloud |
Comparison reflects Open Connector's published architecture and Composio's hosted product model. Composio is a trademark of its respective owner; this page is an independent comparison.
Weighing other options too? See how Composio stacks up against the broader comparison market.
Migration
Switch in one line.
Open Connector implements the Composio v3.1 API field-by-field — auth configs, connected accounts, and tools.proxy. Keep the official @composio/client SDK; just send it to your host. Nothing else in your agent changes.
Need to serve those authenticated tools to an agent over MCP? See how the self-hosted MCP gateway keeps the same credentials behind a scoped MCP endpoint.
- 1:1 with the Composio API docs (required inputs + responses)
- Driven unchanged by the real @composio/client SDK
- Verified by SDK integration tests against the live client
migrate.ts
// Before — Composio's cloud
const composio = new Composio({
apiKey: "ck_live_…",
});
// After — your Open Connector host
const composio = new Composio({
apiKey: "oc_…",
baseURL: "https://connect.acme.com",
});
// Same calls. Same SDK. Credentials never leave your infra.
await composio.tools.proxy({ … });FAQ
Switching from Composio
- Is there an open-source alternative to Composio?
- Yes. Open Connector is an open-source (AGPL-3.0), self-hostable alternative to Composio. Its secure integration layer — OAuth, the AES-256-GCM token vault, and the tamper-evident audit trail — is open core you can run on your own infrastructure for free; only a few enterprise add-ons require a commercial license.
- Is Composio open source?
- Partly. Composio open-sources its SDK and toolkit definitions on GitHub under the MIT license, but the platform you actually run on — the managed OAuth integration layer, the credential store, and the execution sandboxes — is proprietary and hosted in Composio's cloud (its Enterprise on-prem option ships closed-source, license-gated images). Open Connector takes the opposite approach: the platform core itself is open source (AGPL-3.0) and free to self-host.
- What license is Open Connector under?
- Open Connector is open-core. The entire core — the connector engine, API, and dashboard — is licensed under the GNU AGPL-3.0, so you can self-host, modify, and redistribute it freely. A small set of enterprise add-ons (the packages/ee-* workspaces, e.g. premium audit retention and export) is source-available under a separate commercial license and needs a license key for production use. The base audit trail and the full platform stay free under AGPL.
- Is Open Connector compatible with the Composio SDK?
- Yes — it's drop-in compatible. Open Connector implements the Composio v3.1 API (auth_configs and connected_accounts CRUD plus tools.proxy) field-by-field 1:1 with Composio's API docs. Point the official @composio/client SDK at your Open Connector host by changing one baseURL and your existing code runs unchanged. The compat layer is covered by SDK integration tests against the real client.
- Can I self-host Composio?
- Only on its paid Enterprise tier — and even then you deploy Composio's proprietary, license-gated images rather than open source. By default Composio is a hosted SaaS and your tokens live in its cloud. Open Connector's core is open source (AGPL-3.0), so anyone can self-host the full platform for free: your own Postgres, your own OAuth apps, your own encryption keys — no data leaves your environment.
- How do I migrate from Composio to Open Connector?
- Because the API is wire-compatible, migration is mostly a configuration change: deploy Open Connector, recreate your auth configs, and set the @composio/client baseURL to your host. Your agent code that creates connections and proxies tool calls stays the same.
- Is Composio free, and how does the pricing compare?
- Composio has a limited free tier and usage-based paid plans billed per tool call, with self-hosting reserved for its Enterprise tier. Open Connector's core is free and open source (AGPL-3.0) — self-host the full platform at only your own infrastructure cost; optional enterprise features (like long-term audit retention) unlock with a commercial license key.
Own your connector layer.
Join the waitlist for the managed beta, or self-host today from source. Either way, the credentials and the audit trail stay yours.