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
- [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.