Unmanaged Node.js hosting

Node.js hosting on an unmanaged VPS

Use an unmanaged KVM VPS when the application needs a persistent Node.js process, custom system packages, background workers, or direct control over the reverse proxy and runtime.

Join waitlist Compare plans →

Bitfoo opens for orders soon.

Platform: Unmanaged VPS
Runtime: Your Node.js version
Processes: Supervised
Access: Full root

Choose by responsibility

Choose VPS when the process must stay yours

A persistent server is useful for APIs, web applications, workers, and custom services when the team wants host-level control.

Persistent server

Choose a Bitfoo VPS

Run the application and its supporting services on a host your team operates.

Custom Node.js or native package requirements
Persistent APIs, WebSockets, or workers
Direct control over proxy and network behavior

Review the VPS platform →

Platform-managed runtime

Consider a managed application platform

Reduce server work when direct host access is not necessary.

The team wants platform-managed builds and restarts
Automatic scaling matters more than a durable server
No one owns Linux security and recovery

Discuss the workload →

Production foundation

Operate the process, not just the code

The server needs an explicit answer for how the app starts, receives traffic, records failure, and returns after a reboot.

Process supervision

Run the application under a service manager with defined restart behavior and a clear health signal.

Reverse proxy

Terminate TLS and handle public request concerns at an intentional proxy before forwarding to the application port.

Runtime control

Pin the Node.js version and package lockfile, then make runtime and dependency upgrades a tested release activity.

Observability

Capture application and service logs, watch memory and event-loop behavior, and alert on externally meaningful failures.

Plan comparison

Size beyond the average request

Include peak process memory, background work, builds, package installation, databases or caches, logs, and the operating system in the capacity decision.

Swipe horizontally to compare every plan.

Compare unmanaged VPS plans for Node.js Hosting.
Specification	VPS-1 Development, staging, or one light process	VPS-2 A small production API or web application Recommended starting point	VPS-4 Workers, multiple services, or more traffic	VPS-8 Larger or data-heavy Node.js 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

Make the service restartable

A production Node.js deployment should recover from both a bad release and a server reboot without improvised steps.

01
Pin runtime and dependencies

Document the Node.js version, package manager, lockfile, native modules, and required system packages.
02
Separate configuration

Keep secrets server-side and define which values are read at build time versus process startup.
03
Define health and shutdown

Expose a meaningful health check and handle termination signals so restarts do not cut work off unpredictably.
04
Test release and rollback

Automate installation, migration, process restart, validation, and return to a previous release.

Related hosting guidance

Next.js hosting Apply the Node.js operating model to a self-hosted Next.js application. Docker hosting Package the runtime and dependencies into a container-based release. VPS plans Compare resources and the unmanaged responsibility boundary.

Common questions

Is Node.js pre-installed?

No. The VPS is an unmanaged server. You install and maintain the Node.js version and any system packages the application requires.

Can I run WebSockets or background workers?

Yes. Full server control supports persistent services, provided you configure supervision, proxy behavior, resource limits, monitoring, and security.

Does Bitfoo restart my application after a failure?

No. You configure a process supervisor and health monitoring so the service starts after boot and responds appropriately to process failure.

Which plan is the starting point?

VPS-2 is the general production starting point shown here. Choose from measured process memory, traffic, build requirements, and any database, cache, or workers on the same host.