@devries-cameron20 / composio Mirror · read-only / commits / 4d8cdbe28
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 06:00 UTC

docs: frame managed auth as production-ready, own OAuth app for dedicated limits

Apply review suggestions: managed OAuth apps work in production, the shared OAuth app is why you may hit shared provider rate limits as usage grows, and your own OAuth app is the recommendation for higher volume. Drop "before you scale" and the prototype framing, switch the managed-auth callout to info, rename the table column to "Starting point", and rename the KB heading in the source, article and manifest. Link the rate-limits guide (needs #5323). Leaves out "per-plan usage limits": plan-based managed app limits are not enforced yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Jeevesh Jain committed Nov 12, 2026 at 23:05 UTC 4d8cdbe282b4ed511088c800902f720aa504acbe
7 files changed +26 -26
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. 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.
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. If your usage grows, you may run into shared provider rate limits, and your own OAuth app gives you dedicated ones. 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
@@ -10,13 +10,13 @@ Use this guide after the [quickstart](/docs/quickstart) works and before custome
10
11 ## Production decisions at a glance
12
13 -| Prototype default | Production decision |
13 +| Starting point | Production decision |
14 |---|---|
15 | One sample user such as `user_123` | Stable, immutable application user IDs |
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 | Move to your own OAuth app with a custom auth config before you scale |
19 +| Managed auth | Works in production. Consider your own OAuth app for dedicated rate limits, your own consent screen, or custom scopes |
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,7 +44,7 @@ For consumer requests, set `org_id` and `project_id` in Python or `orgId` and `p
44
45 ## 3. Decide how customers authenticate
46
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.
47 +Composio-managed OAuth apps work in production. They remove OAuth app setup and token refresh work. Because the OAuth app is shared, you may run into shared provider rate limits as your usage grows. When you're ready for higher volume, we recommend your own OAuth app with a [custom auth config](/docs/authentication/custom-app-vs-managed-app). [Avoid and recover from rate limits](/docs/poc-to-prod/avoid-rate-limits) shows how to spot and handle those limits.
48
49 Your own OAuth app also gives you:
50
docs/content/kb/guide/platform-production-readiness.mdx
+7 -7
@@ -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":"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"}]
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":"Use managed auth in production, and your own OAuth app when you need dedicated limits"},{"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,13 +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 -## Move from managed auth to your own OAuth app before you scale
34 +## Use managed auth in production, and your own OAuth app when you need dedicated limits
35
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.
36 +Composio-managed OAuth apps work in production. Because the OAuth app is shared,
37 +you may run into shared provider rate limits as your usage grows. For higher
38 +volume, we recommend a custom auth config with your own OAuth app. It also gives
39 +you your application's OAuth brand, custom scopes, a dedicated provider quota,
40 +different polling requirements, and custom 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
+2 -2
@@ -6,8 +6,8 @@ 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).
9 +<Callout type="info">
10 +Managed OAuth apps work in production. Because the OAuth app is shared, you may run into shared provider rate limits as your usage grows. For higher volume, we recommend your own OAuth app. See [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) and [Avoid and recover from rate limits](/docs/poc-to-prod/avoid-rate-limits).
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.
docs/kb/articles/platform-production-readiness.md
+6 -6
@@ -20,13 +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 -## Move from managed auth to your own OAuth app before you scale
23 +## Use managed auth in production, and your own OAuth app when you need dedicated limits
24
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.
25 +Composio-managed OAuth apps work in production. Because the OAuth app is shared,
26 +you may run into shared provider rate limits as your usage grows. For higher
27 +volume, we recommend a custom auth config with your own OAuth app. It also gives
28 +you your application's OAuth brand, custom scopes, a dedicated provider quota,
29 +different polling requirements, and custom 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": "Move from managed auth to your own OAuth app before you scale"
997 + "sourceHeading": "Use managed auth in production, and your own OAuth app when you need dedicated limits"
998 },
999 {
1000 "sourcePath": "platform/production-readiness/public.md",
docs/kb/source/platform/production-readiness/public.md
+6 -6
@@ -37,13 +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 -## Move from managed auth to your own OAuth app before you scale
40 +## Use managed auth in production, and your own OAuth app when you need dedicated limits
41
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.
42 +Composio-managed OAuth apps work in production. Because the OAuth app is shared,
43 +you may run into shared provider rate limits as your usage grows. For higher
44 +volume, we recommend a custom auth config with your own OAuth app. It also gives
45 +you your application's OAuth brand, custom scopes, a dedicated provider quota,
46 +different polling requirements, and custom 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.