Deployment

Learn more about Mintlify

Enter your email to receive updates about new features and product releases.

Infrastructure
Requirements
Build Process
Build Command
Build Output
Environment Variables
Required Variables
Environment Variable Security
Vercel Deployment
Automatic Deployments
Custom Domain
Supabase Setup
Create Supabase Project
Supabase Configuration
Production Checklist
Deployment Commands
Local Build Test
Manual Deployment
Troubleshooting
Monitoring & Analytics
Vercel Analytics
Supabase Monitoring
Next Steps

Deriverse is optimized for deployment on Vercel with Next.js 16. This guide covers production deployment, environment configuration, and Supabase setup.

Infrastructure

Vercel

Recommended Platform: Native Next.js support with automatic deployments, edge functions, and zero-config setup.

Requirements

Node.js: 20+ (Runtime)
Next.js: 16.1.6+
Build Tool: Next.js build system
Package Manager: npm, yarn, or pnpm

Vercel automatically detects Next.js projects and configures build settings. No additional configuration needed.

Build Process

Build Command

next build

Build Output

The build generates a .next directory containing:

Static Assets: HTML, CSS, JavaScript bundles
Server Functions: API routes and server components
Middleware: Wallet adapter and RPC proxies
Optimized Images: Next.js Image Optimization artifacts

Standard Build
Standalone Mode

Default Output Directory

.next/
├── cache/              # Build cache
├── server/             # Server-side code
├── static/             # Static assets
└── standalone/         # Standalone mode (optional)

Used for standard Vercel deployments.

Self-Contained DeploymentEnable in next.config.js:

next.config.js

module.exports = {
  output: 'standalone',
};

Includes all dependencies for Docker or custom hosting.

Environment Variables

Deriverse requires several environment variables for production. Configure these in Vercel’s dashboard under Settings → Environment Variables.

Required Variables

Solana Network Configuration

RPC Endpoints

# Primary RPC URL (Helius recommended)
NEXT_PUBLIC_HELIUS_RPC_URL=https://api.devnet.helius-rpc.com/?api-key=YOUR_API_KEY

# Devnet RPC (fallback)
NEXT_PUBLIC_RPC_DEVNET=https://api.devnet.solana.com

# Mainnet RPC (production)
NEXT_PUBLIC_RPC_MAINNET=https://api.mainnet-beta.solana.com

# Default cluster (devnet or mainnet-beta)
NEXT_PUBLIC_WALLET_CLUSTER=devnet

Use a dedicated RPC provider (Helius, Alchemy, QuickNode) for production. Public endpoints have strict rate limits.

Deriverse Program Configuration

On-Chain Program IDs

# Deriverse program ID
NEXT_PUBLIC_PROGRAM_ID=Drvrseg8AQLP8B96DBGmHRjFGviFNYTkHueY9g3k27Gu

# Deriverse protocol version
NEXT_PUBLIC_DERIVERSE_VERSION=12

Program IDs differ between devnet and mainnet. Ensure you use the correct ID for your target network.

Supabase Configuration

Database Credentials

# Supabase project URL
NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.co

# Supabase anonymous key (public)
NEXT_PUBLIC_SUPABASE_ANON_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...

Get these from your Supabase project dashboard under Settings → API.

The anon key is safe to expose publicly. Row Level Security (RLS) enforces data isolation.

Application Metadata

Optional Configuration

# Environment mode
NODE_ENV=production

# Application URL (for wallet adapter metadata)
NEXT_PUBLIC_APP_URL=https://deriverse.app

Environment Variable Security

NEXT_PUBLIC_ Prefix

Variables prefixed with NEXT_PUBLIC_ are exposed to the browser. Use only for:

RPC URLs (public endpoints)
Supabase anon key (protected by RLS)
Program IDs (on-chain public data)

Never expose:

Supabase service role key
Private API keys
Secret signing keys

Server-Only Secrets

Variables without NEXT_PUBLIC_ are server-only and never sent to the browser.Example:

# Server-only (if needed)
SUPABASE_SERVICE_ROLE_KEY=your-secret-key
DATABASE_PASSWORD=your-db-password

Local Development

Create a .env.local file in the project root:

.env.local

# Copy from .env.example
NEXT_PUBLIC_HELIUS_RPC_URL=https://api.devnet.helius-rpc.com/?api-key=dev-key
NEXT_PUBLIC_SUPABASE_URL=http://localhost:54321
NEXT_PUBLIC_SUPABASE_ANON_KEY=local-dev-key

Never commit .env.local to version control. Add it to .gitignore.

Vercel Deployment

Automatic Deployments

Vercel automatically deploys when you push to your Git repository.

Connect Repository

Link your GitHub, GitLab, or Bitbucket repository to Vercel.

Log in to Vercel Dashboard
Click New Project
Import your Deriverse repository
Vercel auto-detects Next.js configuration

Configure Environment Variables

Add production environment variables in Vercel:

Go to Settings → Environment Variables
Add each variable from the list above
Select Production environment
Click Save

Use different values for Preview (staging) and Production environments to test with devnet before mainnet deployment.

Deploy

Push to your main branch:

git add .
git commit -m "Deploy to production"
git push origin main

Vercel automatically:

Runs npm install
Executes next build
Deploys to global edge network
Provides a unique deployment URL

Verify Deployment

Check the deployment URL provided by Vercel:

https://deriverse-your-project.vercel.app

Test wallet connection, trade lookup, and database persistence.

Custom Domain

Add a custom domain in Vercel:

Go to Settings → Domains
Add your domain (e.g., deriverse.app)
Configure DNS records as instructed
Vercel automatically provisions SSL certificates

Vercel provides automatic HTTPS with Let’s Encrypt certificates. No additional SSL configuration needed.

Supabase Setup

Create Supabase Project

Create Project

Sign in to Supabase Dashboard
Click New Project
Choose organization and region (closest to users)
Set database password (store securely)

Run Database Migrations

Execute the schema creation scripts in Supabase SQL Editor:

-- Create user_wallets table
CREATE TABLE user_wallets (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  wallet_address TEXT UNIQUE NOT NULL,
  network TEXT NOT NULL,
  wallet_provider TEXT NOT NULL DEFAULT 'manual',
  connection_method TEXT NOT NULL DEFAULT 'manual',
  last_synced_at TIMESTAMPTZ,
  created_at TIMESTAMPTZ NOT NULL DEFAULT NOW(),
  updated_at TIMESTAMPTZ NOT NULL DEFAULT NOW()
);

CREATE INDEX idx_user_wallets_address ON user_wallets(wallet_address);
CREATE INDEX idx_user_wallets_last_synced ON user_wallets(last_synced_at DESC);

See Database for full schema.

Enable Row Level Security

Apply RLS policies to protect user data:

-- Enable RLS on user_wallets
ALTER TABLE user_wallets ENABLE ROW LEVEL SECURITY;

-- Policy: Users can view their own wallets
CREATE POLICY "Users can view their own wallets"
ON user_wallets
FOR SELECT
USING (wallet_address = current_setting('request.jwt.claim.wallet_address'));

Get API Credentials

Copy credentials from Settings → API:

Project URL: https://your-project.supabase.co
Anon Key: Public key for client-side requests
Service Role Key: Admin key (never expose to frontend)

Add these to Vercel environment variables.

Supabase Configuration

Authentication
Real-time
Storage

Disable Auth (Current Setup)Deriverse does not use Supabase Auth. Data isolation is enforced via RLS policies based on wallet addresses.If you want to add authentication later:

import { createClient } from '@supabase/supabase-js';

const supabase = createClient(url, key, {
auth: {
persistSession: true,
autoRefreshToken: true,
},
});

Enable Real-time SubscriptionsListen for trade updates:

supabase
.channel('trades')
.on('postgres_changes', 
{ event: 'INSERT', schema: 'public', table: 'trades' },
(payload) => console.log('New trade:', payload)
)
.subscribe();

Enable in Supabase Dashboard under Database → Replication.

File Storage (Optional)If you need to store trade screenshots or export files:

const { data, error } = await supabase.storage
.from('trade-exports')
.upload('trades.csv', file);

Create storage bucket in Storage → Create Bucket.

Production Checklist

Before going live, verify:

Once all items are checked, your Deriverse deployment is production-ready.

Deployment Commands

Local Build Test

Test the production build locally:

# Build for production
npm run build

# Start production server
npm run start

Access at http://localhost:3000.

Manual Deployment

Deploy manually with Vercel CLI:

# Install Vercel CLI
npm i -g vercel

# Login
vercel login

# Deploy to preview
vercel

# Deploy to production
vercel --prod

Manual deployments bypass Git-based workflows. Use for emergencies only.

Troubleshooting

Build Fails with 'Module not found'

Cause: Missing dependencies or incorrect import paths.Solution:

# Clear node_modules and reinstall
rm -rf node_modules package-lock.json
npm install

# Rebuild
npm run build

Wallet Adapter Fails to Load

Cause: SSR hydration mismatch with Jupiter adapter.Solution: Ensure Providers component uses lazy loading:

useEffect(() => {
  import('@jup-ag/wallet-adapter').then(mod => {
    setWalletProvider(() => mod.UnifiedWalletProvider);
  });
}, []);

See src/app/providers.tsx for implementation.

Supabase Connection Errors

Cause: Incorrect credentials or RLS blocking requests.Solution:

Verify NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY
Check RLS policies allow anonymous access
Test query in Supabase SQL Editor

RPC Rate Limit Exceeded

Cause: Too many blockchain queries, insufficient RPC plan.Solution:

Verify 24-hour caching is active
Upgrade RPC provider plan
Implement request throttling
Consider using multiple RPC providers with fallback

Monitoring & Analytics

Vercel Analytics

Enable in Vercel dashboard:

Go to Analytics tab
Click Enable Analytics
View real-time metrics:
- Page views
- Unique visitors
- Performance scores (Web Vitals)
- Geographic distribution

Supabase Monitoring

Track database usage:

Database Size: Settings → Usage
Query Performance: Database → Query Performance
API Requests: Settings → API → Request Logs

Set up alerts in Supabase for:

Database storage > 80% of limit
Slow queries > 1 second
High error rates

Next Steps

Architecture

Understand the system design and data flow patterns.

Database

Explore the database schema and caching strategy.

Service APIs

Explore Supabase service integrations.

GitHub

View source code and report issues.

Last Updated: February 2026 For architecture details, see Architecture. For database schema, see Database.

Database

Local Development Setup

⌘I

Build docs developers (and LLMs) love

Get started for free Talk to us

Get Started

Core Features

Platform

Development

Infrastructure

Vercel

Requirements

Build Process

Build Command

Build Output

Environment Variables

Required Variables

Environment Variable Security

Vercel Deployment

Automatic Deployments

Custom Domain

Supabase Setup

Create Supabase Project

Supabase Configuration

Production Checklist

Deployment Commands

Local Build Test

Manual Deployment

Troubleshooting

Monitoring & Analytics

Vercel Analytics

Supabase Monitoring

Next Steps

Architecture

Database

Service APIs

GitHub

Build docs developers (and LLMs) love

Get Started

Core Features

Platform

Development

​Infrastructure

Vercel

​Requirements

​Build Process

​Build Command

​Build Output

​Environment Variables

​Required Variables

​Environment Variable Security

​Vercel Deployment

​Automatic Deployments

​Custom Domain

​Supabase Setup

​Create Supabase Project

​Supabase Configuration

​Production Checklist

​Deployment Commands

​Local Build Test

​Manual Deployment

​Troubleshooting

​Monitoring & Analytics

​Vercel Analytics

​Supabase Monitoring

​Next Steps

Architecture

Database

Service APIs

GitHub

Build docs developers (and LLMs) love

Infrastructure

Requirements

Build Process

Build Command

Build Output

Environment Variables

Required Variables

Environment Variable Security

Vercel Deployment

Automatic Deployments

Custom Domain

Supabase Setup

Create Supabase Project

Supabase Configuration

Production Checklist

Deployment Commands

Local Build Test

Manual Deployment

Troubleshooting

Monitoring & Analytics

Vercel Analytics

Supabase Monitoring

Next Steps