Deploy on Vercel

Overview

Vercel offers the fastest deployment path for Kuest Prediction Market with one-click Supabase integration. This guide covers the complete deployment process including environment configuration, database setup, and domain management.

Vercel deployment is the recommended approach for most users. It includes automatic Supabase integration, serverless functions, and built-in cron jobs.

Prerequisites

Before deploying to Vercel, ensure you have:

GitHub account
Vercel account (free tier available)
Kuest CLOB Auth credentials from auth.kuest.com
Reown AppKit Project ID from dashboard.reown.com

Deployment Steps

Fork the Repository

Star the repository on GitHub

Fork the repository to your account

Clone your fork locally (optional for local development)

Configure Environment Variables

Download the .env.example file and configure the required variables:

.env.example

# ============================================================
# REQUIRED
# ============================================================

# Get your Kuest CLOB Auth credentials by connecting your EVM wallet at https://auth.kuest.com
KUEST_ADDRESS=""
KUEST_API_KEY=""
KUEST_API_SECRET=""
KUEST_PASSPHRASE=""

# Admin wallets (comma-separated, EVM 0x... addresses on Polygon)
ADMIN_WALLETS=""

# Your REOWN APPKIT project id http://dashboard.reown.com/
REOWN_APPKIT_PROJECT_ID=""

# Random 32 characters – generate one at https://www.better-auth.com/docs/installation#set-environment-variables
BETTER_AUTH_SECRET=""

# Vercel Cron Jobs (Create a random secret of at least 16 characters)
CRON_SECRET=""

# ============================================================
# OPTIONAL
# ============================================================

# Enable Next.js image optimization (can increase Vercel costs)
IMAGE_OPTIMIZATION=false

Changing BETTER_AUTH_SECRET after deployment will invalidate all user sessions and encrypted credentials, requiring users to log in and re-authenticate for trading.

Create Vercel Project

Go to Vercel Dashboard

Click Add New → Project

Connect your GitHub account if not already connected

Find and click Import on your forked repository

In the import modal, open Environment Variables

Click Import .env and select your edited .env.example file

Click Deploy

Wait for the initial deployment to complete

Click Continue to Dashboard when finished

Create Supabase Database

Vercel offers native Supabase integration:

Open your Vercel project dashboard

Navigate to Storage tab

Click Create Database → Supabase

Use default settings (create Supabase account if prompted)

Click Create and wait for provisioning

Click Connect Project on the confirmation screen

This automatically configures:

POSTGRES_URL - Database connection string

SUPABASE_URL - Supabase project URL

SUPABASE_SERVICE_ROLE_KEY - Service role key for storage

Supabase integration includes:

PostgreSQL database (500MB free tier)
Object storage bucket (kuest-assets)
Automatic cron job scheduling via Supabase Edge Functions

Redeploy with Database

Open Deployments tab in your Vercel project

Click the three dots (…) next to the latest deployment

Select Redeploy

Check Use existing Build Cache (optional)

Click Redeploy to confirm

This deployment will include the Supabase environment variables.

Configure Custom Domain (Optional)

After the initial deployment is stable:

Navigate to Settings → Domains

Click Add Domain

Enter your custom domain (e.g., markets.example.com)

Follow the DNS configuration instructions

Wait for DNS propagation (usually 5-30 minutes)

Vercel will automatically provision SSL certificate

After adding a custom domain, update SITE_URL in your environment variables to match your production domain, then redeploy.

Enable GitHub Actions

To keep your fork synchronized with upstream updates:

Go to your forked repository on GitHub

Navigate to Settings → Actions → General

Under Actions permissions, select Allow all actions and reusable workflows

Click Save

Complete Admin Setup

Visit your deployed site

Navigate to Admin → General

Configure:

Company name and branding
Trading fees
Market categories
Theme customization

Environment Variables Reference

Required Variables

Variable	Description	Example
`KUEST_ADDRESS`	Your Kuest wallet address on Polygon	`0x1234...`
`KUEST_API_KEY`	API key from auth.kuest.com	-
`KUEST_API_SECRET`	API secret from auth.kuest.com	-
`KUEST_PASSPHRASE`	API passphrase from auth.kuest.com	-
`ADMIN_WALLETS`	Comma-separated admin addresses	`0x123...,0x456...`
`REOWN_APPKIT_PROJECT_ID`	Reown project ID	-
`BETTER_AUTH_SECRET`	32-character random string	-
`CRON_SECRET`	16+ character random string	-

Auto-Configured by Vercel

These are automatically set when you connect Supabase:

Variable	Description
`POSTGRES_URL`	PostgreSQL connection string
`SUPABASE_URL`	Supabase project URL
`SUPABASE_SERVICE_ROLE_KEY`	Supabase service role key

Optional Variables

Variable	Description	Default
`IMAGE_OPTIMIZATION`	Enable Next.js image optimization	`false`
`SENTRY_DSN`	Sentry error tracking DSN	-
`SENTRY_ORG`	Sentry organization	-
`SENTRY_PROJECT`	Sentry project name	-
`SENTRY_AUTH_TOKEN`	Sentry auth token	-

Vercel-Specific Features

Automatic Cron Jobs

When using Supabase mode on Vercel, cron jobs are automatically configured via vercel.json:

{
  "crons": [
    {
      "path": "/api/sync/events",
      "schedule": "*/5 * * * *"
    },
    {
      "path": "/api/sync/resolution",
      "schedule": "*/5 * * * *"
    },
    {
      "path": "/api/sync/translations",
      "schedule": "*/10 * * * *"
    },
    {
      "path": "/api/sync/volume",
      "schedule": "*/30 * * * *"
    }
  ]
}

Serverless Functions

All API routes automatically deploy as serverless functions with:

10-second execution timeout (Hobby)
60-second execution timeout (Pro)
Automatic scaling
Edge network distribution

Build Configuration

Vercel automatically detects the Next.js framework and uses optimal settings:

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

Troubleshooting

Deployment Failed

Check build logs in Vercel dashboard
Verify all required environment variables are set
Ensure BETTER_AUTH_SECRET is exactly 32 characters
Check for syntax errors in .env file

Database Connection Issues

Verify Supabase integration is connected in Vercel Storage
Check POSTGRES_URL format in environment variables
Redeploy after connecting Supabase
Check Supabase dashboard for database status

Cron Jobs Not Running

Verify CRON_SECRET is set in environment variables
Check Vercel deployment logs for cron execution
Ensure Supabase mode is properly configured
Verify cron endpoints are accessible

Custom Domain SSL Issues

Wait 24 hours for DNS propagation
Verify DNS records match Vercel requirements
Check domain provider for DNSSEC conflicts
Remove and re-add domain in Vercel settings

Maintenance

Updating Your Deployment

To deploy updates from upstream:

Sync your fork with the upstream repository
Vercel automatically deploys on git push to main branch
Monitor deployment in Vercel dashboard
Verify changes in production

Database Migrations

Database schema updates are handled automatically through:

Build-time migration scripts
Supabase migration tracking
Zero-downtime deployment strategy

Monitoring

Monitor your deployment through:

Vercel Analytics: Usage, performance, Core Web Vitals
Supabase Dashboard: Database queries, storage usage
Vercel Logs: Function execution, errors
Sentry (optional): Error tracking and performance monitoring

Scaling Considerations

Free Tier Limits

100GB bandwidth per month
100 serverless function invocations per day
500MB PostgreSQL storage (Supabase free tier)
1GB file storage (Supabase free tier)

Upgrading to Pro

Consider upgrading when you need:

Custom domains on team projects
Longer function timeouts (60s)
Advanced analytics
Priority support
Password protection
More team members

Next Steps

Configure Docker deployment for self-hosting
Set up Kubernetes for enterprise scale
Explore cloud providers for alternative hosting

Get Started

Deployment

Configuration

Features

Customization

Operations

Overview

Prerequisites

Deployment Steps

Environment Variables Reference

Required Variables

Auto-Configured by Vercel

Optional Variables

Vercel-Specific Features

Automatic Cron Jobs

Serverless Functions

Build Configuration

Troubleshooting

Deployment Failed

Database Connection Issues

Cron Jobs Not Running

Custom Domain SSL Issues

Maintenance

Updating Your Deployment

Database Migrations

Monitoring

Scaling Considerations

Free Tier Limits

Upgrading to Pro

Next Steps

Build docs developers (and LLMs) love

Get Started

Deployment

Configuration

Features

Customization

Operations

​Overview

​Prerequisites

​Deployment Steps

​Environment Variables Reference

​Required Variables

​Auto-Configured by Vercel

​Optional Variables

​Vercel-Specific Features

​Automatic Cron Jobs

​Serverless Functions

​Build Configuration

​Troubleshooting

​Deployment Failed

​Database Connection Issues

​Cron Jobs Not Running

​Custom Domain SSL Issues

​Maintenance

​Updating Your Deployment

​Database Migrations

​Monitoring

​Scaling Considerations

​Free Tier Limits

​Upgrading to Pro

​Next Steps

Build docs developers (and LLMs) love

Overview

Prerequisites

Deployment Steps

Environment Variables Reference

Required Variables

Auto-Configured by Vercel

Optional Variables

Vercel-Specific Features

Automatic Cron Jobs

Serverless Functions

Build Configuration

Troubleshooting

Deployment Failed

Database Connection Issues

Cron Jobs Not Running

Custom Domain SSL Issues

Maintenance

Updating Your Deployment

Database Migrations

Monitoring

Scaling Considerations

Free Tier Limits

Upgrading to Pro

Next Steps