Skip to main content
Wrkks is a Next.js application designed for seamless deployment on modern hosting platforms. This guide will help you deploy your application to production.

​
Platform recommendations

Wrkks works best on the following platforms: Vercel is the recommended platform for deploying Wrkks as it’s built by the creators of Next.js and offers:
  • Zero-configuration deployments
  • Automatic HTTPS and CDN
  • Edge network for optimal performance
  • Built-in preview deployments
  • Serverless function support
Wrkks uses Node.js runtime for PDF parsing, which is fully supported on Vercel’s serverless functions.

​
Other supported platforms

Wrkks can also be deployed on:
  • Netlify - Supports Next.js with serverless functions
  • Railway - Simple deployment with persistent environments
  • Render - Docker-based deployment option
  • Self-hosted - Deploy on your own infrastructure using Docker or Node.js

​
Deployment checklist

Before deploying, ensure you have:
1

Environment variables configured

Set up all required environment variables including Clerk, Supabase, and OpenRouter credentials. See Environment variables for details.
2

Database configured

Create and configure your Supabase database with the required tables and RLS policies. See Database setup for instructions.
3

Authentication configured

Set up your Clerk application with proper redirect URIs and webhook configurations.
4

API keys secured

Ensure all API keys are set as environment variables and never committed to your repository.

​
Quick deployment to Vercel

The fastest way to deploy Wrkks is using Vercel:
1

Connect your repository

Import your Git repository to Vercel through the Vercel dashboard.
2

Configure environment variables

Add all required environment variables in the Vercel project settings. You can also upload them as a .env file during initial setup.
3

Deploy

Click “Deploy” and Vercel will automatically build and deploy your application.
4

Set up custom domain (optional)

Configure your custom domain in the Vercel project settings under the “Domains” tab.
Make sure to set the NEXT_PUBLIC_BASE_URL environment variable to your production domain before deploying.

​
Build configuration

Wrkks uses the following build configuration:
package.json
{
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start"
  }
}

​
Node.js version

Wrkks requires Node.js 18.x or higher. Set this in your platform’s configuration:
.nvmrc
18

​
Post-deployment verification

After deployment, verify your application:
  1. Authentication flow - Test sign up and sign in with Clerk
  2. PDF parsing - Upload a resume PDF and verify it parses correctly
  3. Database operations - Ensure user data is saved to Supabase
  4. AI extraction - Test the OpenRouter integration for resume parsing
  5. Public profiles - Verify that published resumes are accessible via share URLs

​
Troubleshooting

​
Build fails

  • Check that all environment variables are set correctly
  • Verify Node.js version is 18.x or higher
  • Review build logs for specific error messages

​
PDF parsing doesn’t work

  • Ensure serverExternalPackages: ["pdf-parse-new"] is set in next.config.ts
  • Verify the Node.js runtime is enabled (default on Vercel)
  • Check file size limits (max 5MB for PDFs)

​
Database connection errors

  • Verify Supabase environment variables are correct
  • Check that RLS policies are properly configured
  • Ensure your Supabase project is not paused

​
Next steps

Environment variables

Configure all required environment variables

Database setup

Set up your Supabase database

Build docs developers (and LLMs) love

Get started for freeTalk to us