Vovy creates your Clerk production instance, adds its DNS records, swaps in live keys and your own Google credentials, and tests the live login.
Switch Clerk to production on my domain
How it works
- Create the production instance: Vovy switches to Production in the Clerk Dashboard, enters your domain, and copies your development settings over.
- Add Clerk's DNS records: It adds the CNAME records Clerk lists, like clerk.yourdomain.com, in your DNS provider. DNS is the address book that points names at servers.
- Use your own Google credentials: Development uses Clerk's shared Google keys. For production Vovy creates your own OAuth client in Google Cloud and pastes it into Clerk.
- Swap in the live keys: Vovy replaces the pk_test_ and sk_test_ keys with pk_live_ and sk_live_ in Vercel's Production environment variables, then redeploys.
- Test the live login: It signs in on your real domain and shows a card confirming DNS, SSL and each provider are green in Clerk.
What you provide
- Your domain
- Access to your DNS provider
- A Google Cloud account
What you get
- Clerk running on your domain
- Your own Google OAuth app
- Live keys in production only
- A green status card
FAQ
Will my development users move over?
No. Production is a separate instance with its own user list, so test accounts stay behind.
Why can't I use Clerk on a vercel.app address?
Clerk production needs a domain you own so it can set up its subdomains, so a free vercel.app address won't work.
How long do the DNS records take?
Usually under an hour, occasionally up to 48 hours. Clerk shows each record as verified when it's ready.
Related tasks
All tasks