Hosting for Next.js, React and Node.js apps
Not every JavaScript project needs the same kind of hosting. A React single-page app is static files, a Next.js site with server rendering needs a Node.js runtime, and an API is a long-running Node process. Here is how to tell which one you have, which plan fits and when a VPS is the better choice.
Static, server-rendered or API: know what you are deploying
If your Next.js app uses getServerSideProps, server components that fetch per request, route handlers or image optimisation, it needs a Node runtime. Choose the Next.js stack for that, the React stack for a client-only app, and the Node.js stack for an API or custom server.
| Project type | What runs in production | Build output |
|---|---|---|
| React SPA (Vite, Create React App) | Only static files: HTML, JS, CSS | dist/ or build/ folder |
| Next.js with output: "export" | Only static files | out/ folder |
| Next.js with SSR, ISR, API routes or middleware | A Node.js server (next start or the standalone server.js) | .next/ folder |
| Node.js API (Express, Fastify, NestJS) | A Node.js process listening on a port | Your app plus node_modules |
Prepare your app for production
- Build locally firstRun npm run build and fix every error and type warning. A build that fails on your machine will fail on the server too.
- Pin your Node versionSet "engines": { "node": ">=20" } in package.json, or the version you develop on, so builds are reproducible.
- Use environment variablesKeep API keys and database URLs out of the code. In Next.js only variables prefixed NEXT_PUBLIC_ reach the browser; everything else stays on the server.
- Consider standalone outputFor Next.js, output: "standalone" in next.config produces a small server.js with only the dependencies it needs.
- Listen on the given portFor a Node.js API, read the port from process.env.PORT instead of hard-coding 3000.
Which plan for your JavaScript projects
- Starter: one Next.js or React site, such as a company site, portfolio or product landing page. 15 GB and 500 GB of traffic a month.
- Creator: up to 5 projects, for example the site, a separate API and a preview copy. 30 GB and 1 TB of traffic.
- Professional: up to 15 projects, for developers and studios hosting client apps. 75 GB and 2 TB of traffic.
- Business, Enterprise and Ultimate: from 25 projects up to unlimited sites and traffic, for agencies.
Plans
| Plan | What you get | Price |
|---|---|---|
| Starter | 1 sites · 15 GB · 500 GB traffic | €5.99/mo |
| Creator | 5 sites · 30 GB · 1 TB traffic | €7.99/mo |
| Professional | 15 sites · 75 GB · 2 TB traffic | €9.99/mo |
| Business | 25 sites · 100 GB · 2 TB traffic | €19.99/mo |
| Enterprise | 50 sites · 200 GB · 5 TB traffic | €29.99/mo |
| Ultimate | Unlimited sites · 500 GB · Unlimited traffic | €49.99/mo |
Prices per month. Billed monthly, no long contract.
See all plansWhen a VPS fits better
Web hosting is managed, which means less to look after but also less to change. Choose a VPS when you need root access, for example to run WebSocket servers with many connections, background queues and cron workers, your own database server, Docker containers or system packages your app depends on. EclipsiumX VPS plans start at €4.99 a month, with root access over SSH, but you manage the software yourself.
Hosting it on EclipsiumX
Choose a plan, pick the stack (Next.js, React or Node.js), and enter your own domain or start on a free project address on eclipsiumx.com. Then create your EclipsiumX account and pay on checkout. Every plan includes a free SSL certificate, sites run in data centres in Germany, and billing is monthly from €5.99.
Moving from another host? Tell us where the app runs today and we help you move it. Your business email on your own domain can sit in the same account, from €2.49 per mailbox a month.