- More Node.js processes on your web hosting account
- Who benefits from a Node.js web hosting plan with a high process limit?
- What is NPROC (and what does it have to do with Node.js)?
- Run Node.js apps directly on Oderland
- TL;DR
More Node.js processes on your web hosting account
The process limit, or NPROC limit, controls how many simultaneous processes a web hosting account can have running.
Previously, the limit was 100 processes for Standard and Premium, and 150 for Deluxe — now we’re raising the limit to 500 for all web hosting packages. That’s between 3 and 5 times more capacity, depending on your current package.
– We’ve seen how our customers’ needs have changed. Modern web applications require more long-running processes than a traditional PHP application. That’s especially noticeable when running Node.js or Next.js, for example, says Martin Stenröse, Operations & Security Manager at Oderland.
“We want our customers to build their entire web presence with us, without having to buy add-ons elsewhere to fill the gaps.”
The result of this upgrade means you can run more demanding web applications directly with us, without having to place parts of the solution with other providers.
– The change was rolled out in several stages and has been closely monitored throughout the process. We want to improve things for those running Node.js without negatively impacting anyone else on our platform, says Martin.
Who benefits from a Node.js web hosting service with a high process limit?
The increase is most noticeable for those who run or use:
- Node.js applications, where each worker is counted separately
- Next.js and other frameworks that start multiple processes per deployment
- Applications with many cron jobs or background jobs running in parallel
- Applications built directly on the server via, for example, ‘npm run build’, where build tools spawn many short-lived processes, something that’s becoming increasingly common when developing with AI tools like Claude Code or Codex
For those running a standard WordPress site without heavy plugins, the old limit was rarely an issue. But as headless solutions and JavaScript-based frontends become more common, the new limit provides plenty of room to grow.
– We’ve seen some customers hit the limit when building with Node frameworks, and we believe part of the explanation is that AI tools have made it much easier to build these types of applications. It’s a trend we want to embrace, not slow down, says Martin.
What is NPROC (and what does it have to do with Node.js)?
NPROC (Number of Processes) is the number of simultaneous processes your account is allowed to run. The limit is managed via CloudLinux Manager (LVE), which we use to distribute resources fairly among all customers on a server.
Every time something runs on the account — a cron job, a PHP process, a Node.js instance— it counts as one or more processes. The more modern frameworks you run, the more processes there tend to be.
“We’ve seen some customers hit the limit when building with Node frameworks, and we believe part of the explanation is that AI tools have made it much easier to build these types of applications. It’s a trend we want to embrace, not slow down.”
Run Node.js apps directly on your Oderland account
An important effect of the increase is that more customers can consolidate their solution in one place. A common perception is that our web hosting packages needs to be supplemented with services from other providers.
With the new limit, your Oderland account can accommodate significantly more, allowing you to deploy your web application directly with us.
– We want our customers to build their entire web presence with us, without having to buy add-ons elsewhere to fill the gaps.
TL;DR
We’re raising the NPROC limit to 500 on all web hosting packages at no additional cost.
This allows you to:
- run more Node.js processes in parallel
- handle more concurrent requests without hitting the limit
- build more complex applications directly on your web hosting, using tools such as AI assistants
