Next.js deployment and hosting
An alternative to Vercel for deploying Next.js. Deploys to Docker containers, routing via Traefik, automatic SSL, custom domains and DDoS protection.
Auto-deploy from Git
The platform pulls the code from your repository, builds the project and runs it.
Ready-made environment
No Nginx or Linux setup required. Reliable RelaxNet servers under the hood.
Custom domains and SSL
Connect your domain in one click, and the platform issues a Let's Encrypt SSL certificate automatically.
RelaxNet is an alternative to Vercel for deploying Next.js. The platform detects your Next.js project automatically, builds it and deploys it to isolated Docker containers. Routing and load balancing are handled by Traefik, a modern reverse proxy. You get everything Next.js offers, including server-side rendering (SSR) and static site generation (SSG), on the platform's own servers with billing in rubles.
Deployment is as simple as it gets: connect a Git repository, and the platform takes care of building the Docker image, routing, issuing HTTPS certificates and auto-deploying on every push. It's a solid choice if you need reliable Next.js hosting that's reachable from anywhere.
How to deploy Next.js
1. Connect a Git repository
Pick the repository with your Next.js project. The platform detects the stack automatically by the presence of `next.config.js`.
2. Configure environment variables
Add all required `NEXT_PUBLIC_` and server-side variables in the project settings. Don't keep secrets in code.
3. Start the deploy
Click 'Deploy'. RelaxNet builds the project into a Docker container and starts it automatically. Every push to the main branch triggers a rebuild.
4. Connect your domain
Add your own domain in the project settings. Traefik picks up the routing automatically and issues and renews a Let's Encrypt SSL certificate.
Platform comparison
| Platform | Status | Payment |
|---|---|---|
| Plain VPS | Works | Lengthy manual setup of Docker, Traefik/Nginx, SSL |
| RelaxNet | Auto-deploy from Git | RUB, $6 free balance |
Compared with a plain VPS, the platform saves you from writing a Dockerfile by hand, configuring Traefik and maintaining server infrastructure.
Common errors and fixes
The build fails with 'heap out of memory'
Large Next.js projects may need more memory to build. Try raising the resource limits in the project settings or reducing memory usage in your app.
Environment variables aren't available on the client
Make sure variables that must be available in the browser are prefixed with `NEXT_PUBLIC_`.
502 error after deploy
Check your container logs. Most often it's an error in server code (for example, in the start configuration), or the app isn't listening on the port Traefik forwards traffic to.
FAQ
Is the App Router supported?
Yes, the platform fully supports both the App Router and the Pages Router in Next.js.
How do Server Actions work?
Server Actions work out of the box. The platform and Traefik handle them correctly during deployment and proxying.
Can I use Middleware?
Yes, you can use Middleware to handle requests inside the app before they reach a page.