Deploy RefactKit to Vercel, Cloudflare, or Node.js

RefactKit uses Nitro v3 as its server engine, which means a single codebase can target Vercel, Cloudflare Workers, or a standalone Node.js server by changing one environment variable at build time. Vercel is the primary and recommended deployment target — the package.json build script defaults to NITRO_PRESET=vercel. This page covers the pre-deploy checklist, Vercel setup, and alternative deployment targets.

Pre-deploy checklist

Run these commands in order before every production deployment. They catch type errors, test regressions, and schema drift before your code reaches users:

pnpm check           # Biome lint + format check
pnpm test            # Unit and integration tests (Vitest)
pnpm test:e2e        # End-to-end tests (Playwright)
npx drizzle-kit push # Sync schema changes to production database

Run npx drizzle-kit push against your production database by ensuring DATABASE_URL in your environment points to the production Supabase project before running the command. Schema drift between your code and the live database will cause runtime errors.

Deployment targets

Vercel
Cloudflare Workers
Node.js

Vercel is the recommended deployment target. The package.json build command is pre-configured:

# build command (already set in package.json)
NITRO_PRESET=vercel vite build

Deploy steps

Push your repository to GitHub (or GitLab / Bitbucket).
Go to vercel.com → Add New Project → import your repository.
Vercel auto-detects the build command from package.json. Confirm the framework preset is Other (not Next.js).
Before clicking Deploy, open Environment Variables and add every variable from the table below.
Click Deploy.

Required environment variables

Set these in Vercel Dashboard → Project → Settings → Environment Variables:

Variable	Example value	Notes
`DATABASE_URL`	`postgresql://postgres.[ref]:...@...pooler.supabase.com:6543/postgres`	Must use port 6543 (transaction pooler)
`BETTER_AUTH_SECRET`	output of `openssl rand -base64 32`	Minimum 32 characters
`BETTER_AUTH_URL`	`https://your-domain.com`	Your Vercel deployment URL or custom domain
`RESEND_API_KEY`	`re_...`	From Resend dashboard
`EMAIL_FROM`	`RefactKit <noreply@yourdomain.com>`	Must match a verified Resend domain
`VITE_SUPABASE_URL`	`https://xxxx.supabase.co`	From Supabase → Project Settings → API
`SUPABASE_SERVICE_ROLE_KEY`	`eyJhbGci...`	From Supabase → Project Settings → API → service_role
`VITE_APP_URL`	`https://your-domain.com`	Optional — overrides the auth client base URL

Rotating BETTER_AUTH_SECRET invalidates all existing user sessions immediately. Every logged-in user will be signed out. Plan any secret rotation during low-traffic windows and communicate the impact in advance.

VITE_ prefixed variables are embedded into the client bundle at build time. Never set SUPABASE_SERVICE_ROLE_KEY or RESEND_API_KEY with a VITE_ prefix — doing so would expose them to every browser that loads your app.

Custom domain

After the initial deployment succeeds, go to Vercel Dashboard → Project → Settings → Domains and add your custom domain. Update BETTER_AUTH_URL and VITE_APP_URL to match the custom domain, then redeploy.

To deploy to Cloudflare Workers, change the Nitro preset and build:

NITRO_PRESET=cloudflare-module vite build

The build output targets the cloudflare-module worker format. Deploy using the Wrangler CLI:

npx wrangler deploy

Set environment variables via the Cloudflare dashboard (Workers & Pages → your worker → Settings → Variables) or in your wrangler.toml. The same variables required for Vercel apply here.

Cloudflare Workers runs in an edge runtime, not Node.js. Confirm that all dependencies in your code are compatible with the Workers runtime before deploying. The postgres.js client used by Drizzle requires TCP connections — you may need to use Supabase’s HTTP-based query API or a Workers-compatible PostgreSQL driver for this target.

To produce a standalone Node.js server binary, use the node preset:

NITRO_PRESET=node vite build

After the build completes, start the server:

node .output/server/index.mjs

The server listens on the port defined by the PORT environment variable (defaults to 3000). Set all required environment variables in your server environment before starting the process, or use a process manager like PM2:

PORT=8080 \
DATABASE_URL="..." \
BETTER_AUTH_SECRET="..." \
BETTER_AUTH_URL="https://your-domain.com" \
node .output/server/index.mjs

For production Node.js deployments, use a reverse proxy (Nginx or Caddy) in front of the Nitro server to handle TLS termination and set the x-forwarded-for header. RefactKit reads this header for IP-based rate limiting.

Environment variable reference

The table below summarizes every variable and where it is consumed:

Variable	Required	Runtime	Description
`DATABASE_URL`	✅	Server	Supabase PostgreSQL connection string — port 6543
`BETTER_AUTH_SECRET`	✅	Server	Session signing secret — minimum 32 characters
`BETTER_AUTH_URL`	✅	Server	Public URL of your app — used in email links and OAuth callbacks
`RESEND_API_KEY`	✅	Server	Resend API key for transactional email
`EMAIL_FROM`	✅	Server	Sender address shown in outgoing emails
`VITE_SUPABASE_URL`	✅	Both	Supabase project URL — embedded in client bundle
`SUPABASE_SERVICE_ROLE_KEY`	✅	Server only	Supabase service role key — bypasses RLS, never expose client-side
`BETTER_AUTH_API_KEY`	Optional	Server	Enables the Better Auth admin dashboard at `/api/auth/dashboard`
`VITE_APP_URL`	Optional	Both	Overrides the base URL for the auth client

Get Started

Core Concepts

Guides

Configuration

Reference

Deploy RefactKit to Vercel, Cloudflare, or Node.js

Pre-deploy checklist

Deployment targets

Deploy steps

Required environment variables

Custom domain

Environment variable reference

​Pre-deploy checklist

​Deployment targets

​Deploy steps

​Required environment variables

​Custom domain

​Environment variable reference

Pre-deploy checklist

Deployment targets

Deploy steps

Required environment variables

Custom domain

Environment variable reference