The open-source, self-hostable
alternative to Composio.
Open Connector is an open-source (MIT) credential broker for AI agents — an alternative to Composio you run on your own infrastructure. 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.
Same agent workflow. You keep the keys.
Both broker third-party credentials so your agents never touch raw secrets. The difference is ownership: Open Connector is open source and runs in your environment.
| Capability | Open Connector | Composio |
|---|---|---|
| License | Open source (MIT) | Proprietary / closed source |
| Self-hosting | Run on your own infra — Postgres, your OAuth apps, your keys | Hosted SaaS only |
| 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 brokered call | Limited / not self-hostable |
| Pricing | Free — self-host at cost | 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.
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.
- 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
// 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({ … });Switching from Composio
- Is there an open-source alternative to Composio?
- Yes. Open Connector is an open-source (MIT), self-hostable alternative to Composio. It brokers OAuth and API-key credentials for AI agents, stores tokens in an AES-256-GCM encrypted vault on your own infrastructure, and writes a tamper-evident audit record for every call.
- 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?
- Composio is a hosted SaaS, so you cannot self-host it. Open Connector is built to be self-hosted: it runs on your own Postgres, uses your own OAuth apps, and seals credentials with 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.
- How much does Open Connector cost compared to Composio?
- Open Connector is free and open source under the MIT license — you only pay your own infrastructure cost. Composio is a hosted product with usage-based paid tiers.
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.