Replace Vercel / Heroku / Render with Self-Hosted Dokploy

# Production Docker Compose: Dokploy (Replaces Vercel / Heroku / Render)
services:
  caddy:
    image: caddy:2-alpine
    restart: unless-stopped
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./Caddyfile:/etc/caddy/Caddyfile:ro
      - caddy_data:/data
    networks:
      - stack_net

  dokploy:
    image: dokploy/dokploy:latest
    container_name: stack-dokploy
    restart: unless-stopped
    environment:
      - "NODE_ENV=production"
      - "DATABASE_URL=postgres://postgres:${POSTGRES_PASSWORD:-strongpassword}@postgres:5432/dokploy"
    volumes:
      - dokploy_data:/data
    networks:
      - stack_net

  postgres:
    image: pgvector/pgvector:pg16
    container_name: stack-postgres
    restart: unless-stopped
    environment:
      - "POSTGRES_USER=postgres"
      - "POSTGRES_PASSWORD=${POSTGRES_PASSWORD:-strongpassword}"
    volumes:
      - postgres_data:/var/lib/postgresql/data
    networks:
      - stack_net

  redis:
    image: redis:7-alpine
    container_name: stack-redis
    restart: unless-stopped
    volumes:
      - redis_data:/data
    networks:
      - stack_net

networks:
  stack_net:
    driver: bridge

volumes:
  caddy_data:
  dokploy_data:
  postgres_data:
  redis_data:

# Automatic Let's Encrypt HTTPS for Dokploy
dokploy.{$DOMAIN:yourdomain.com} {
  encode zstd gzip
  reverse_proxy dokploy:3000
}

Why Teams Switch to Dokploy

• ✓Native Docker Compose visual stack deployments
• ✓Multi-server cluster support
• ✓Built-in CPU/RAM monitoring & alerts

Deploy Dokploy in 60 Seconds

Sized automatically for Dokploy (512MB container RAM + OS overhead).