@devries-cameron20 / composio-1 / commits / 4d2bd91e2
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs: say managed apps are not built for production scale

Composio-managed OAuth apps work in production but are not built for production scale. Update the production readiness guide, its KB source, the managed OAuth apps page, and the authentication overview to tell readers to move to their own OAuth app before they scale. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Jeevesh Jain committed Nov 11, 2026 at 16:37 UTC 4d2bd91e2ed2346be7741bd582211011157f1a6f
7 files changed +28 -21
docs/content/docs/authentication/index.mdx
+1 -1
@@ -116,7 +116,7 @@ Composio manages authentication with **auth configs**. An [auth config](/referen
116 - **Scopes**: what actions your tools can perform
117 - **Credentials**: your own app credentials, or Composio's managed auth
118
119 -Composio creates one auth config per toolkit and applies it to every user who connects that toolkit. Most toolkits use Composio managed auth, so you don't create or configure anything. You only need a [custom auth config](/docs/authentication/custom-app-vs-managed-app) to use your own OAuth app or customize scopes.
119 +Composio creates one auth config per toolkit and applies it to every user who connects that toolkit. Most toolkits use Composio managed auth, so you don't create or configure anything. Managed auth works in production but is not built for production scale, so move to your own OAuth app before you scale. You only need a [custom auth config](/docs/authentication/custom-app-vs-managed-app) to use your own OAuth app or customize scopes.
120
121 <AuthConfigFlow />
122
docs/content/docs/production-readiness.mdx
+3 -3
@@ -16,7 +16,7 @@ Use this guide after the [quickstart](/docs/quickstart) works and before custome
16 | One project for every test | Separate projects for environments that must not share credentials or resources |
17 | A new session on every run | Persist and reuse session IDs for multi-turn work |
18 | Every toolkit is discoverable | Restrict toolkits and tools to the product's intended scope |
19 -| Managed auth | Keep it, or use custom auth for branding, scopes, quotas, or custom providers |
19 +| Managed auth | Move to your own OAuth app with a custom auth config before you scale |
20 | API keys in a local `.env` file | Server-side secret manager and environment-specific keys |
21 | A successful demo call | Real account, failure-path, webhook, and tenant-isolation tests |
22
@@ -44,9 +44,9 @@ For consumer requests, set `org_id` and `project_id` in Python or `orgId` and `p
44
45 ## 3. Decide how customers authenticate
46
47 -Keep managed auth when its provider app, scopes, and quotas fit your product. It removes OAuth app setup and token-refresh work.
47 +Composio-managed OAuth apps work in production, but they are not built for production scale. They remove OAuth app setup, so they suit prototypes and early launches. Move to your own OAuth app with a [custom auth config](/docs/authentication/custom-app-vs-managed-app) before you scale.
48
49 -Use a [custom auth config](/docs/authentication/custom-app-vs-managed-app) when you need:
49 +Your own OAuth app also gives you:
50
51 - Your own app name on the provider consent screen
52 - Different or additional OAuth scopes
docs/content/kb/guide/platform-production-readiness.mdx
+7 -6
@@ -2,7 +2,7 @@
2 title: "Move a Composio Integration from Prototype to Production"
3 description: "Public guidance for production user identity, environment isolation, authentication, sessions, and trigger delivery."
4 keywords: ["authentication","deployment","platform","production","projects","sessions","users","auth-config","authentication","getting-started","security-and-trust","sessions-and-execution","workflows"]
5 -sources: [{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Replace example user IDs with stable application user IDs"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Isolate environments with separate Composio projects when needed"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Switch from managed auth only when production requirements call for it"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Restrict the production session to the capabilities the agent needs"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Reuse a stored session until the user or configuration changes"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Test production trigger handling through the real webhook path"}]
5 +sources: [{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Replace example user IDs with stable application user IDs"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Isolate environments with separate Composio projects when needed"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Move from managed auth to your own OAuth app before you scale"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Restrict the production session to the capabilities the agent needs"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Reuse a stored session until the user or configuration changes"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Test production trigger handling through the real webhook path"}]
6 lastVerifiedAt: "2026-08-24"
7 reviewAfter: "2026-11-22"
8 freshness: "evergreen"
@@ -31,12 +31,13 @@ apps, scopes, or provider credentials differ.
31 - [Composio glossary: Project](https://docs.composio.dev/reference/glossary#project)
32 - [Configure authentication](https://docs.composio.dev/docs/tools-direct/authenticating-tools)
33
34 -## Switch from managed auth only when production requirements call for it
34 +## Move from managed auth to your own OAuth app before you scale
35
36 -Keep Composio-managed OAuth apps in production when their consent branding,
37 -scopes, and shared provider quotas fit your product. Create a custom auth
38 -config when you need your application's own OAuth brand, custom scopes, a
39 -dedicated provider quota, different polling requirements, or a custom instance.
36 +Composio-managed OAuth apps work in production, but they are not built for
37 +production scale. Before you scale, create a custom auth config with your own
38 +OAuth app. Your own app also supports your application's OAuth brand, custom
39 +scopes, a dedicated provider quota, different polling requirements, and custom
40 +instances.
41 Both options keep connected-account credential storage and refresh in Composio.
42 Pass the resulting auth config ID to the session; creating the config alone
43 does not make the session use it.
docs/content/toolkits/managed-auth.mdx
+4
@@ -6,6 +6,10 @@ keywords: [managed OAuth, OAuth app, auth config, client credentials, toolkit li
6
7 Composio can provide the OAuth app that your users authorize when they connect a toolkit. You do not need to register an OAuth app or supply its client ID and client secret.
8
9 +<Callout type="warn">
10 +Managed OAuth apps work in production, but they are not built for production scale. Move to your own OAuth app before you scale. See [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app).
11 +</Callout>
12 +
13 Your users still authorize their accounts through a [Connect Link](/docs/tools-direct/authenticating-tools#hosted-authentication-connect-link). Composio stores and refreshes the resulting tokens. See [Authentication](/docs/authentication) for the full connection flow.
14
15 This catalog identifies who provides the OAuth app, not which execution framework you must use. For per-user OAuth with application-owned tools, follow [Managed authentication for your own tools](/docs/authentication/managed-auth-for-custom-tools). Your code can call provider endpoints through the authenticated proxy without predefined tools, MCP, or an LLM.
docs/kb/articles/platform-production-readiness.md
+6 -5
@@ -20,12 +20,13 @@ apps, scopes, or provider credentials differ.
20 - [Composio glossary: Project](https://docs.composio.dev/reference/glossary#project)
21 - [Configure authentication](https://docs.composio.dev/docs/tools-direct/authenticating-tools)
22
23 -## Switch from managed auth only when production requirements call for it
23 +## Move from managed auth to your own OAuth app before you scale
24
25 -Keep Composio-managed OAuth apps in production when their consent branding,
26 -scopes, and shared provider quotas fit your product. Create a custom auth
27 -config when you need your application's own OAuth brand, custom scopes, a
28 -dedicated provider quota, different polling requirements, or a custom instance.
25 +Composio-managed OAuth apps work in production, but they are not built for
26 +production scale. Before you scale, create a custom auth config with your own
27 +OAuth app. Your own app also supports your application's OAuth brand, custom
28 +scopes, a dedicated provider quota, different polling requirements, and custom
29 +instances.
30 Both options keep connected-account credential storage and refresh in Composio.
31 Pass the resulting auth config ID to the session; creating the config alone
32 does not make the session use it.
docs/kb/manifest.json
+1 -1
@@ -994,7 +994,7 @@
994 },
995 {
996 "sourcePath": "platform/production-readiness/public.md",
997 - "sourceHeading": "Switch from managed auth only when production requirements call for it"
997 + "sourceHeading": "Move from managed auth to your own OAuth app before you scale"
998 },
999 {
1000 "sourcePath": "platform/production-readiness/public.md",
docs/kb/source/platform/production-readiness/public.md
+6 -5
@@ -37,12 +37,13 @@ apps, scopes, or provider credentials differ.
37 - [Composio glossary: Project](https://docs.composio.dev/reference/glossary#project)
38 - [Configure authentication](https://docs.composio.dev/docs/tools-direct/authenticating-tools)
39
40 -## Switch from managed auth only when production requirements call for it
40 +## Move from managed auth to your own OAuth app before you scale
41
42 -Keep Composio-managed OAuth apps in production when their consent branding,
43 -scopes, and shared provider quotas fit your product. Create a custom auth
44 -config when you need your application's own OAuth brand, custom scopes, a
45 -dedicated provider quota, different polling requirements, or a custom instance.
42 +Composio-managed OAuth apps work in production, but they are not built for
43 +production scale. Before you scale, create a custom auth config with your own
44 +OAuth app. Your own app also supports your application's OAuth brand, custom
45 +scopes, a dedicated provider quota, different polling requirements, and custom
46 +instances.
47 Both options keep connected-account credential storage and refresh in Composio.
48 Pass the resulting auth config ID to the session; creating the config alone
49 does not make the session use it.