01
Reverse proxy
Put a reverse proxy in front of the Next.js server to handle connection behavior, request limits, TLS termination, and other edge concerns.
Unmanaged Next.js hosting
Next.js hosting on an unmanaged VPS
Run a Next.js server on an unmanaged KVM VPS when you want to own the Node.js version, reverse proxy, process supervision, persistent storage, and deployment workflow.
Bitfoo opens for orders soon.
- Platform
- Unmanaged VPS
- Runtime
- Node.js
- Proxy
- Recommended
- Storage
- Persistent NVMe
Linux administration required
Installed and maintained by you
Nginx or equivalent
Plan allocation applies
Choose by responsibility
Self-hosting is an operational choice
A VPS removes platform constraints, but it also removes the managed deployment layer. Choose it when that control is useful enough to justify the server work.
Own the environment
Choose a Bitfoo VPS
Use a persistent server when you need direct control over runtime and network behavior.
- Custom Node.js and system dependencies
- A single persistent instance or a deliberately designed multi-instance setup
- Your team can operate Linux and the deployment pipeline
Reduce operations
Consider a managed application platform
A managed deployment service may be a better fit when the team does not want to administer a server.
- Preview environments and deployments should be platform-managed
- Automatic scaling is more important than server control
- No one owns patching, monitoring, and recovery
Production foundation
Plan the complete serving path
Next.js self-hosting includes more than starting a Node process. The proxy, cache, assets, environment, and release workflow form one system.
02
Process supervision
Run the application under a supervisor such as systemd or another deliberately configured process manager.
03
Cache ownership
Understand filesystem-backed caches, revalidation, and how the design changes if more than one application instance serves traffic.
04
Repeatable releases
Build, migrate if needed, switch releases, restart safely, and retain a rollback path rather than editing production in place.
Plan comparison
Size for builds, runtime, and adjacent services
Memory must cover the operating system, the running Next.js process, deployment builds if performed on-server, and any database, cache, or worker processes sharing the VPS.
Swipe horizontally to compare every plan.
| Specification | VPS-1 Development, staging, or a light single process | VPS-2 A small production application Recommended starting point | VPS-4 Heavier builds, workers, or multiple services | VPS-8 Higher-traffic or data-heavy application stacks |
|---|---|---|---|---|
| vCPU | 1 | 2 | 4 | 6 |
| RAM | 1GB DDR5 | 2GB DDR5 | 4GB DDR5 | 8GB DDR5 |
| Storage | 25GB NVMe | 50GB NVMe | 100GB NVMe | 200GB NVMe |
| Bandwidth | 1TB | 2TB | 4TB | 6TB |
| IPv4 | 1 | 1 | 1 | 1 |
| Price | Coming soon | Coming soon | Coming soon | Coming soon |
| Availability | Join waitlist → | Join waitlist → | Join waitlist → | Join waitlist → |
Exact prices will appear when ordering opens. VPS plans are unmanaged and do not include an automated backup service.
Before deployment
Define production behavior before launch
Make the runtime and recovery model explicit before the first production deployment.
- 01
Choose the deployment output
Decide how the application will be built and started, including whether a standalone output or container image is part of the release artifact.
- 02
Separate public and secret configuration
Treat browser-exposed variables differently from server-only secrets and document which values are fixed at build time.
- 03
Design cache persistence
Account for revalidation and cache coordination before adding multiple application instances or ephemeral release directories.
- 04
Prove rollback and restore
Test a failed release, process restart, and data restore before production traffic depends on them.
Related hosting guidance
Common questions
Can Next.js image optimization work when self-hosted?
Yes. Next.js documents self-hosted image optimization, while also allowing a custom loader when image processing should live elsewhere.
Should the Next.js server be exposed directly?
The Next.js self-hosting guide recommends placing a reverse proxy in front of the application server so connection and request-handling concerns are not delegated entirely to the Node process.
Does Bitfoo deploy the application?
No. The VPS supplies the server environment. Your team builds, deploys, supervises, monitors, backs up, and updates the application and operating system.
Which plan is a sensible production starting point?
VPS-2 is the general starting point shown here, but the right size depends on build memory, application traffic, background work, and other services running on the same server.