Node.js Hosting in France - Tuned VPS

French Linux VPS tuned for Node.js: Express, Next.js, NestJS, Strapi, Fastify. PM2 + Nginx reverse proxy.

Starting at €4.99/mo

Introduction

Host your Node.js applications with By-Hoster on French KVM Linux VPS. NVMe SSD, root access, unlimited bandwidth. Compatible with Node.js LTS (18, 20, 22).

Typical stack: Node.js + PM2 (process manager) + Nginx reverse proxy + Let's Encrypt SSL. Works with Express, Next.js, NestJS, Fastify, Hono and Strapi.

Included features

Node.js LTS

Versions 18, 20 and 22 LTS ready to install.

PM2 + Nginx

Standard process manager and reverse proxy.

MongoDB / PostgreSQL

Node.js-friendly databases ready to install.

Use cases

Next.js / Remix

React SSR/SSG frameworks hosted.

Express / NestJS APIs

High-performance REST/GraphQL APIs.

Strapi headless CMS

Node.js CMS + PostgreSQL backend.

Discord bots

discord.js, Telegraf and friends, 24/7.

Frequently asked questions

Node.js 22 LTS for new projects. Node.js 20 LTS for broader compatibility. Both installable via nvm in one command.

Use PM2: npm i -g pm2; pm2 start app.js; pm2 startup; pm2 save. PM2 restarts your app automatically after a crash or a server reboot.

Install Nginx (apt install nginx), create /etc/nginx/sites-available/mysite with a location / block that runs proxy_pass http://localhost:3000. Add headers Host, X-Real-IP, X-Forwarded-For and X-Forwarded-Proto. Enable the site and grab SSL with certbot: certbot --nginx -d mysite.com.

No hard limit. PM2 runs multiple apps in parallel with pm2 start app1.js, pm2 start app2.js, etc. The bottleneck is RAM (each Node app uses 50-300 MB). On a Starter 2 GB VPS: 4-6 small apps. On a VPS Pro 4 GB: 10-15 lightweight apps. Use distinct ports (3000, 3001, etc.) and an Nginx reverse proxy to route by domain.

Yes. pnpm (npm install -g pnpm) is faster and saves disk space thanks to its content-addressable store. yarn (npm install -g yarn) or bun (curl -fsSL https://bun.sh/install | bash) are also supported. No restriction on the package manager you pick.

Three options: 1) A .env file at the project root + the dotenv module (npm i dotenv). 2) systemd variables (Environment=NODE_ENV=production inside the service). 3) PM2 ecosystem.config.js with an env section. For sensitive secrets (API keys, tokens), avoid committing them in git, add .env to .gitignore.