Getting Started
Once you have decided to self-host your Next.js application, you have to decide if you deploy it on your own server (e.g. a VPS) or use a provider that does host the application for you.
No matter which way you choose, it usually means to dockerize your Next.js application. Fortunately, it's very easy to get there.
DIY: VPS + Docker + Proxy
Deploying your Next.js application on your own server (e.g. an affordable VPS) is usually the most affordable way to host Next.js. But that does come at a cost. If you do not want to manually SSH into your server every time your application code changes, you should implement a rudimentary CI/CD pipeline.
- ✅ affordable: starts at around $5/month
- ✅ you have the opportunity to learn about infrastructure and server setup
- ❌ CI/CD pipeline has to be implemented
- ❌ server setup & security relies on you
- ❌ server maintenance relies on you
- ❌ requires setup of a proxy server
Provider
Hosting your Next.js application on a VPS for your hobbiest blog or your personal website is usually a good enough solution (on top you learn something about server administration).
For a "professional" project there are usually not many reasons not to choose a provider that does host your dockerized application for you.
Especially since some providers offer a free tier to test the service.
- ✅ no server setup, maintenance or dealing with server security
- ✅ provider CLI usually simplifies CI/CD pipeline
- ✅ application scaling is usually handled for you
- ❌ more expensive compared to a VPS