Next.js Hosting: Deploy with Git on a Fixed-Price VPS

What's installed on your Next.js server?

• Coolify 4.6.0, an open-source panel that builds from your GitHub repository and deploys the result
• Railpack build tool, which recognizes Next.js; Coolify marks it as beta, and a Dockerfile option is there too
• Docker and the Traefik reverse proxy, which gets and renews HTTPS certificates
• A ready admin account, with the welcome wizard skipped and public sign-up closed
• sslip.io addresses, so everything opens over HTTPS before you add a domain
• 2 GB of swap, and a firewall with ports 22, 80, 443, 6001, 6002 and 8000 open

What size do you need for Next.js?

Next.js has no official RAM figure, and the build sets the requirement more than the running app does. In our real-server tests at 4 GB and 2 cores, an AI chat app with about 85 packages built in about 3.7 minutes, peaking at 3.5 GB of memory, dipping into swap and filling 18 GB of disk. At 2 GB that app ran out of memory during the TypeScript check, though a small example passed. Start with 4 GB, and look at 8 GB for projects with many packages. RAM and CPU can go up or down later, while disk only grows.

Who is it for?

• Anyone shipping a Next.js app, whether written by hand or with AI coding tools
• People who'd rather know the monthly cost up front than watch a usage bill grow
• Apps with queue workers, WebSockets or long-running AI responses
• Projects that keep the database on the same server as the app

What happens after you order?

1. Set the size and complete your payment. Your server starts and Coolify installs itself. This took about 12 minutes in our real-server tests.
2. In your panel, open your server from My servers. Use the Panel address, Email and Password rows on the Overview tab to sign in to Coolify.
3. On the Projects page, press New resource. For a public repository, choose Public Git Repository and enter the address.
4. For a private repository, generate a key on the Private Keys page, add the public key to Deploy keys on GitHub and choose Private Git Repository (with Deploy Key).
5. Enter your variables on the Environment Variables page and press Deploy. The Domains page has an HTTPS test address, and your own domain goes there too.
6. Put the address and secret from the app's Webhooks page into the repository's Webhooks settings on GitHub. From then on, every git push goes live.

With every server

• Daily backups included in the price
• Unlimited traffic
• Full root access
• Scale RAM and CPU up or down later, and grow the disk
• Location: Istanbul · IST-1.

Good to know

• Variables starting with NEXT_PUBLIC_ are written into the browser code during the build. Press Redeploy when you change one, and never give that prefix to model or payment keys.
• The container is rebuilt on every deploy, so a SQLite file written inside it disappears. Attach its folder with Persistent Storage or create a PostgreSQL database in the panel.
• Coolify connects to the server over SSH as root with its own key. If you disable root login completely or remove the coolify line from authorized_keys, deployments stop working.
• Once the panel works on its HTTPS address, you can close ports 8000, 6001 and 6002. Docker skips ufw, so this takes Coolify's Compose route, and the help article has the steps.
• Coolify's automatic updates are on by default. Keeping your app's packages up to date is your job.
• The server lives in one place, Istanbul. Latency grows for distant visitors, and you can put a content delivery network in front if you need one.