Deploy Next.js in 60 Seconds
Next.js is the React framework for production. Deploy it on your own server with full SSR, API routes, and middleware - no Vercel lock-in, no usage-based billing surprises.
The usual way to deploy Next.js
- Vercel bills per-function invocation, bandwidth, and ISR revalidation - costs spiral at scale
- Self-hosting means configuring standalone output, a custom server, and a CDN for static assets
- Setting up a Node.js server with proper memory limits, graceful shutdown, and health checks
- Managing next build caching, .next directory sizes, and OOM kills on small VPS boxes
- Handling environment variables at build-time vs runtime and getting IMAGE_OPTIMIZATION to work outside Vercel
Vercel makes it easy until the bill arrives. Self-hosting is powerful but painful to set up.
Or just run one command
What you get
Recommended plan for Next.js
- 2 vCPU
- 2 GB RAM
- 25 GB storage
- HTTPS included
- Custom domain support
- SSH & web terminal access
Next.js deployment notes
Build & Start Scripts
Make sure your package.json has "build": "next build" and "start": "next start". InstaPods runs npm install, then npm run build, then npm start.
Standalone Output
For smaller deploys, add output: "standalone" to next.config.js. InstaPods works with both standalone and default output modes.
Memory for Builds
next build can be memory-hungry. The Build plan (1 GB RAM) handles most projects. For large apps with many pages, use Grow (2 GB).
Deploy Next.js in 60 seconds
One command. Real server. HTTPS included. No DevOps degree required.
Start Free