MANTLEKIT
MantleKit Team·2026-03-25·1 min read

Deploying MantleKit to Vercel

A step-by-step guide to deploying your MantleKit project to Vercel with environment variables and custom domains.

deploymentvercelnextjs

Prerequisites

Before deploying, make sure you have:

  • A Vercel account
  • Your project pushed to a Git repository (GitHub, GitLab, or Bitbucket)
  • Your Supabase project set up (if using database: true)

Connect to Vercel

  1. Go to vercel.com/new
  2. Import your Git repository
  3. Vercel will auto-detect Next.js settings
⚠️

Do not commit your .env.local file. Add environment variables through the Vercel dashboard instead.

Environment Variables

Add these environment variables in Vercel's project settings:

NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=your-anon-key
SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
💡

You can copy these from your Supabase project's Settings > API page.

Custom Domain

After your first deploy:

  1. Go to your project's Settings > Domains
  2. Add your custom domain
  3. Update your DNS records as instructed
# Verify DNS propagation
dig your-domain.com CNAME

Build Configuration

MantleKit works with Vercel's default Next.js build settings. No custom configuration needed:

{
  "buildCommand": "next build",
  "outputDirectory": ".next",
  "framework": "nextjs"
}

Continuous Deployment

Every push to your main branch will trigger a new deployment. Preview deployments are created automatically for pull requests.