What is Node.js?
Node.js runs JavaScript outside the web browser, with standard-library tools for files, networking and other application work. It is a runtime used by servers and development tools; npm package installation and a production hosting service are separate parts of the workflow.
Who is Node.js for?
Developers running JavaScript applications or build tools who can maintain the runtime, dependencies and deployment environment.
Separate the runtime from the package manager
Node.js executes JavaScript outside a web browser. Its introduction describes V8 and the standard library used for files, networking and other application work. A command-line build tool and a server application can both depend on Node.js without being the same kind of product.
npm handles package workflows around the project. Installing dependencies is separate from running the application or hosting it for customers. Node-RED, for example, uses a Node.js runtime underneath its flow-based interface; it is not another name for Node.js.
Node.js features
The core capabilities to consider for your workflow.
- JavaScript execution outside the browser
- Asynchronous I/O and standard-library modules
- Command-line and server application workflows
Check what actually runs on the target machine
Use node --version to record the runtime and npm --version for the package-management CLI. Keep those observations alongside the project’s dependency and deployment requirements.
Our offline npm reproduction records both versions while examining a real dependency installation. It distinguishes the runtime from the package manager, the installed files and the lockfile. It is not a Node.js hosting or application-performance benchmark.
Node.js pricing
Free open-source JavaScript runtime
There is no core Node.js runtime subscription. Budget hosting, operations, application work and any commercial support or service separately.
Calculate the cost of your quote →Free access & evaluation
Node.js is free, open-source software. Its distribution includes MIT-licensed Node.js code and separately licensed components.
Before you choose Node.js
The runtime does not include a managed production hosting service.
Package and framework compatibility depends on the selected Node.js release.
Choose a supported release and plan upgrades; an installed executable can belong to an end-of-life branch.
A working executable can be out of support
Check the official release status before deploying. The project recommends Active LTS or Maintenance LTS for production applications. Compatibility with one development machine does not establish a supported production arrangement.
On 17 October 2026, that table listed Node.js 24 and 22 as LTS, 26 as Current and 25 as end of life. Our npm study used the installed Node.js 24.19.0 runtime. Record the release status as well as the executable version when planning a rollout; the test does not establish application compatibility.
Explore related software
Node.js FAQs
What is NodeJS, and is it a programming language?
Node.js is a runtime for JavaScript outside the browser. JavaScript is the language; Node.js provides an execution environment and APIs used by applications and development tools.
What is the difference between Node.js and npm?
Node.js runs JavaScript. npm is a separate package-management tool with associated website and registry services. Record node --version and npm --version separately when checking a project environment.
Does Node.js include production hosting?
No. The local runtime does not supply a managed production hosting service. Deployment, monitoring, backup and operating responsibilities depend on the environment you choose.
Which Node.js release should production applications use?
The Node.js release guidance recommends Active LTS or Maintenance LTS for production applications. Check the current support table and the application’s compatibility requirements rather than choosing solely because a version is installed locally.
Is Node-RED the same product as Node.js?
No. Node-RED is a flow-based programming tool that uses Node.js as its runtime. Evaluate the application and its runtime compatibility separately.