This wires Clerk into the app: email/password with a 6-digit code step, Sign in with Apple, Google SSO, and a hosted user database you never have to run. You get src/app/(auth)/{sign-in,sign-up,reset} with src/screens/auth/*, the redirect hook src/hooks/use-auth-redirect.ts (signed-out users land on /(auth)/sign-in, signed-in users leave (auth), onboarding wins first), and, with --with-examples, an example at src/app/examples/auth.tsx. @/lib/auth keeps the same API whichever option you pick - pick Clerk when you want user management, organizations and a polished dashboard without owning a database.
When to pick Clerk
Pick Clerk if you'd rather buy user management outright: hosted accounts, a good dashboard, organizations, and a code-based sign-up flow that's already wired here.
At a glance
- Runs in Expo Go
- Yes
- Files added
- 15
- npm packages
- 6
- Keys to paste
EXPO_PUBLIC_CLERK_PUBLISHABLE_KEY- Included in
- Pro
- Screens added
/(auth)/reset,/(auth)/sign-in,/(auth)/sign-up- Tests included
- 2
Set it up
bun run setup --auth clerkSetup copies the module in, installs SDK-matched versions and removes the options you did not pick. Then bun run doctor lists every key still missing, with a link to where you get it. The step-by-step guide is in the Clerk docs.
Wiring it by hand instead? Read the guide: Expo auth: Clerk vs Supabase vs Better Auth.
Clerk vs other auth options
| Option | Expo Go | npm packages | Keys to paste | Included in |
|---|---|---|---|---|
| Clerk | Yes | 6 | 1 | Pro |
| Supabase Auth | Yes | 4 | 2 | Pro |
| Better Auth | Yes | 4 | 1 | Pro |
Questions
Can I use Clerk in Expo Go?
Yes. This module runs in Expo Go, so you can try it before you make a development build.
What do I need to set up Clerk in an Expo app?
Run bun run setup --auth clerk, then paste one key into .env: EXPO_PUBLIC_CLERK_PUBLISHABLE_KEY. bun run doctor lists any that are missing, with a link to where you get each one.
Which other modules does Clerk need?
It needs a Storage option (expo-sqlite/kv-store, MMKV or AsyncStorage). Pick those in the same setup run.
Does the ReadyNative free tier include Clerk?
No. Auth is a Pro category: the free tier and Starter ship it switched off. Pro is one payment with lifetime updates.
Can I build the app without Clerk?
Yes. Pick none for auth (bun run setup --auth none) - auth.useSession() shim returns signed-out, signOut resolves.
Clerk or Supabase Auth for Expo?
Pick Clerk if you'd rather buy user management outright: hosted accounts, a good dashboard, organizations, and a code-based sign-up flow that's already wired here. Pick Supabase if you also want a Postgres database and row-level security behind the same account - it's the cheapest path from zero to a real backend.
Clerk or Better Auth for Expo?
Pick Clerk if you'd rather buy user management outright: hosted accounts, a good dashboard, organizations, and a code-based sign-up flow that's already wired here. Pick Better Auth if the user table has to be yours - it runs on your own API routes (backend/api-routes is required), with no third-party dashboard and no per-user pricing, in exchange for owning the database and the mail provider.
What does Clerk mean for the App Store and Google Play privacy forms?
It collects: Email address, phone, name (account); Session tokens; Device identifiers. Shared with: Clerk (processor). Setup adds its data types to the iOS privacy manifest; the docs page lists the answers for Play's Data safety form.
Which Clerk version does it install?
For Expo SDK 57: @clerk/backend ^3.19.0, @clerk/expo ^4.6.8, expo-apple-authentication ~57.0.2, expo-auth-session ~57.0.12, expo-crypto ~57.0.3, expo-secure-store ~57.0.4. Setup installs Expo packages with expo install, so they match the SDK.
Get it
Clerk ships in Pro: one payment, lifetime updates. See pricing or browse every module.