Vercel vs Hetzner VPS (self-host) Comparison

# Vercel — zero-config Next.js deploy + environment variable + Edge Config example

# 1) vercel.json at the project root for function region and cron settings
{
  "regions": ["fra1"],
  "crons": [
    { "path": "/api/cron/revalidate", "schedule": "0 */6 * * *" }
  ]
}

# 2) Deploy via CLI (build+TLS+CDN automatic)
npx vercel --prod

# 3) To reduce the cost of ISR write units (1 unit = 8 KB, no included quota),
# adjust the revalidate interval based on traffic
export const revalidate = 3600; // regenerate once an hour

# 4) To reduce Fast Origin Transfer, force the function
# output into a static cache
export async function GET() {
  return Response.json(
    { data: "ok" },
    { headers: { "Cache-Control": "public, s-maxage=600" } }
  );
}

# Hetzner VPS — Next.js standalone self-host + systemd + nginx

# 1) next.config.js — standalone output mode (per the official self-hosting guide)
module.exports = {
  output: "standalone",
};

# 2) Build + copy into standalone
npm run build
cp -r .next/static .next/standalone/.next/static
cp -r public .next/standalone/public

# 3) systemd unit — process management (portfolio-ssr.service example)
[Unit]
Description=Next.js standalone server
After=network.target

[Service]
Type=simple
User=portfolio
WorkingDirectory=/var/www/app/.next/standalone
ExecStart=/usr/bin/node server.js
Restart=on-failure
Environment=PORT=4000
NoNewPrivileges=true
ProtectHome=true

[Install]
WantedBy=multi-user.target

# 4) nginx reverse proxy (Next.js's official recommendation)
server {
  listen 443 ssl;
  server_name example.com;
  location / {
    proxy_pass http://127.0.0.1:4000;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  }
}

# 5) Install sharp — required for Image Optimization
npm install sharp