Aipotheosis Labs

license

Apache-2.0(OSI)

source

public(the platform backend and its portal)

self-host

yes(run the backend and frontend yourself)

service

optional(the vendor also runs a hosted tier)

core features withheld

no — nothing withheld from the published tree

Apache-2.0 covers the whole platform, including the multi-tenant OAuth and secrets machinery that is the product's central feature, which sets it apart from the closed connector platforms it competes with. The README documents a separate hosted offering without holding back any part of the published platform, so the core is ungated.

• https://api.github.com/repos/aipotheosis-labs/aci recorded 2026-09-17

  Repository metadata: spdx_id Apache-2.0, 4,891 stars, not archived, not a fork, last pushed 2026-05-28, described as "the open source tool-calling platform that hooks up 600+ tools into any agentic IDE or custom AI agent".

• https://raw.githubusercontent.com/aipotheosis-labs/aci/main/LICENSE recorded 2026-09-17

  The LICENSE body: the verbatim Apache License 2.0 text.

• https://raw.githubusercontent.com/aipotheosis-labs/aci/main/README.md recorded 2026-09-17

  The README names the hosted offering separately - "Managed Service: aci.dev" - while publishing the platform itself: "To run the full ACI.dev platform (backend server and frontend portal) locally, follow the individual README files for each component: Backend: backend/README.md Frontend: frontend/README.md". That multi-tenant OAuth machinery is part of the published platform, which is what makes this `ungated` under the acceptance standard rather than a claim from path absence.

GitHub stars are the only usable adoption signal, since the aci-sdk package on PyPI measures downloads of a client library rather than the platform itself, and no customer or request count is published. A star is not a use, so this reading stands on a weak signal alone.

• https://api.github.com/repos/aipotheosis-labs/aci recorded 2026-09-17

  Repository metadata for aipotheosis-labs/aci: 4,891 stargazers.

ACI's multi-tenant authentication runs entirely in its own portal: the caller addresses a linked account by an owner id rather than a stored end-user token, and its own API key is the only secret the caller ever handles. That places it level with Composio, the other platform built the same way around managed OAuth and secrets.

• https://raw.githubusercontent.com/aipotheosis-labs/aci/main/README.md recorded 2026-09-17

  The README: "Instead of writing separate OAuth flows and API clients for Google Calendar, Slack, and more, use ACI.dev to manage authentication and provide AI agents with unified, secure function calls", with "Multi-tenant Authentication: Built-in OAuth flows and secrets management for both developers and end-users" and "600+ Pre-built Integrations".

• https://www.aci.dev/docs/introduction/quickstart.md recorded 2026-09-17

  The quickstart: "Click Start OAuth2 Flow button to start the OAuth2 flow and link your Github account under the project", after which "you'll need to provide this linked account owner id in your code to execute functions on behalf of the user". The caller's own credential is ACI's: "Each Agent is assigned an API key".