- Save data per user — bookings, settings, content, history.
- Gate features behind sign-in (a checkout, a profile page, an admin panel).
- Personalize the experience by name, role, plan, or past behavior.
- Track activity and usage by individual rather than by session.
How auth works in a Replit app
Replit ships two built-in auth options. Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.- Replit Auth — your users sign in with their existing Replit accounts. The sign-in page is Replit-branded. There’s no setup beyond asking Agent to add it.
- Clerk Auth — your app gets its own dedicated Clerk tenant. Users create accounts inside your app, not Replit. You control the branding, the login methods, and the look and feel of the sign-in screen.
Replit Auth vs. Clerk Auth
If you’re building a prototype or an internal tool, Replit Auth is the fastest path. If you’re building something with its own brand identity, especially something customer-facing or commercial, Clerk Auth is the better fit.
Add auth to your app
You don’t have to choose up front — you can start with one and migrate later. The fastest path is to tell Agent which one to use:- “Add sign-in to my app. Use Replit Auth.”
- “Add sign-in to my app. Use Clerk Auth.”
Next steps
Replit Auth
Replit-branded sign-in with zero setup — users sign in with their Replit account.
Clerk Auth
Your own branded auth tenant — fully customizable login, separate Dev/Prod environments.
Add login
Worked example: wire Clerk Auth into a real app and test it with two customers.
Migrate from Replit Auth to Clerk
Move an existing app from Replit Auth onto a Clerk tenant.