Deploy to Production

Choose a domain registrar:

• Namecheap - Affordable with good customer service
• Google Domains - Simple interface with free privacy protection
• Porkbun - Budget-friendly with free WHOIS privacy
• GoDaddy - Well-known provider with many TLDs

Select a domain name that:

• Is memorable and easy to spell
• Reflects your brand/product
• Ideally has a .com TLD (or relevant alternative like .io for tech products)

Purchase your domain with WHOIS privacy protection enabled

Configure your DNS settings (you’ll need this for the next steps)

Create a new production project in Supabase:

• Log in to Supabase
• Click “New Project”
• Name it “[Project Name] Production”
• Set a secure database password (avoid special characters like ’#’ and ’&’)
• Select a region closest to your target users
• Create the project

Securely store your production credentials:

• Database password
• NEXT_PUBLIC_SUPABASE_URL
• NEXT_PUBLIC_SUPABASE_ANON_KEY
• SUPABASE_SERVICE_ROLE_KEY
• DATABASE_URL (with pgbouncer)
• DIRECT_URL (without pgbouncer)

Migrate your schema to production:

• Connect to your production database using the Supabase CLI
• Apply your migrations

bun run db:push

• Apply your RLS policies

bun run db:rls

Create a production instance in Clerk:

• Log in to Clerk
• Create a new application for production
• Enable required authentication methods (Google, Email, etc.)

Configure your production domain:

• Add your custom domain in Clerk settings
• Verify ownership of your domain
• Set up proper redirect URLs

Configure Google OAuth:

• Add your production Google OAuth credentials
• Configure redirect URLs

Create a new webhook in Clerk:

• Use your production domain as the webhook URL (e.g. https://your-production-domain.com/api/webhooks)

Securely store your production API keys:

• NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY
• CLERK_SECRET_KEY
• CLERK_WEBHOOK_SECRET

Create your production products and prices:

• Create the same products/prices as in your test environment (you can copy them from the test environment)

• Note the live product and price IDs

Switch from test mode to live mode

Configure webhook endpoints:

• Set up webhook endpoints for your production domain (e.g. https://your-production-domain.com/api/webhooks)
• Configure the following webhook events:
  • customer.subscription.created
  • customer.subscription.updated
  • customer.subscription.deleted
  • invoice.payment_succeeded
  • invoice.payment_failed
  • checkout.session.completed
  • payment_intent.succeeded
  • charge.refunded
  • refund.updated
  • refund.failed
  • charge.refund.updated
  • refund.created
• Store the webhook signing secret

Securely store your production API keys

• STRIPE_SECRET_KEY
• NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY
• NEXT_PUBLIC_STRIPE_PRICE_ID (for each product)
• STRIPE_WEBHOOK_SECRET

Set up your production email templates in Plunk:

• Log in to Plunk
• Create/update email templates for production
• Test all email templates

Configure sender domains and verification:

• Add your custom domain as a sender domain
• Verify domain ownership by adding required DNS records

Securely store your production API key:

• PLUNK_API_KEY

• Create a board in UserJot dashboard
• Set the link on the “Submit a bug/Request a Feature” button in your app
• No additional configuration is needed as this is pre-configured in the Titan repository

• Add the analytics script tag to your index.html file
• No local testing is required, this is for production use only

• Connect your Stripe account to handle support tickets
• No additional configuration is needed

Create a new project in Vercel:

• Log in to Vercel
• Click “Add New Project”
• Connect to your GitHub repository

Configure project settings:

• Select NextJS as the framework
• Configure build settings if needed
• Set your production domain

Set all environment variables:

• Add all your production API keys and configuration values
• Double-check for any missing or incorrect values

Deploy your application:

• Click “Deploy”
• Monitor the build process for any errors

Set up your custom domain:

• Add your domain in the Vercel project settings
• Configure the required DNS records at your domain registrar
• Wait for DNS propagation (can take up to 48 hours)

Verify authentication flows:

• Test sign-up and sign-in
• Test social authentication providers
• Verify email verification process

Verify payment processing:

• Test subscription sign-ups
• Test one-time payments (if applicable)
• Verify webhook handling

Verify email functionality:

• Test transactional emails
• Check for proper formatting and delivery