Deploying NestSaaS

This section covers the various options for deploying your NestSaaS application to production environments. NestSaaS is built on Next.js and can be deployed to various hosting platforms.

Deployment Options

NestSaaS can be deployed to:

Vercel (Recommended)
Netlify
Self-hosted environments

Pre-Deployment Checklist

Before deploying your NestSaaS application, ensure you have:

Configured your environment variables
Set up your database
Configured authentication providers
Set up storage for media files
Tested your application locally

Vercel Deployment

Vercel is the recommended platform for deploying NestSaaS applications, offering seamless integration with Next.js.

Steps for Vercel Deployment

Create a Vercel account if you don't have one
Connect your GitHub, GitLab, or Bitbucket repository
Configure your environment variables in the Vercel dashboard
Deploy your application

# Install Vercel CLI
pnpm add -g vercel
 
# Login to Vercel
vercel login
 
# Deploy
vercel

Detailed Vercel Deployment Guide

Netlify Deployment

Netlify is another excellent option for hosting NestSaaS applications.

Steps for Netlify Deployment

Create a Netlify account if you don't have one
Connect your GitHub, GitLab, or Bitbucket repository
Configure your build settings:
- Build command: pnpm build
- Publish directory: .next
Configure your environment variables in the Netlify dashboard
Deploy your application

Detailed Netlify Deployment Guide

Self-Hosted Deployment

For complete control over your hosting environment, you can self-host NestSaaS.

Requirements for Self-Hosting

Node.js server (v18.x or later)
Database server (PostgreSQL recommended)
Storage solution for media files
HTTPS certificate

Deployment Options

Docker containers
Traditional VPS or dedicated server
Kubernetes cluster

Detailed Self-Hosted Deployment Guide

Database Considerations

PostgreSQL

For production deployments, we recommend:

Using a managed PostgreSQL service (AWS RDS, DigitalOcean Managed Databases, etc.)
Setting up proper backups
Configuring connection pooling

Connection Pooling

For optimal database performance, configure connection pooling:

// prisma/client.ts
import { PrismaClient } from '@prisma/client'
 
const globalForPrisma = global as unknown as { prisma: PrismaClient }
 
export const prisma =
  globalForPrisma.prisma ||
  new PrismaClient({
    log: ['query'],
    connectionLimit: 5,
  })
 
if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = prisma