Editorial take
Why it stands out
Node.js should read as runtime plus infrastructure, not as a licensable product. The real risk and cost live in patch cadence, hosting shape, and the supporting services around the runtime.
Tool profile
JavaScript runtime for servers, APIs, CLIs, and tooling with an event driven model and broad ecosystem.
JSON APIs and BFF layers for web and mobile clients
The V8-based JavaScript runtime behind npm’s ecosystem: APIs, CLIs, edge workers, and full-stack TypeScript services.
Node.js is distributed under the MIT License under the OpenJS Foundation governance model. There is no per-server runtime royalty—your invoice is CPU/RAM on VMs, containers, or serverless platforms, plus optional enterprise support from vendors such as Red Hat or HeroDevs if you purchase long-term support builds. Private npm organizations bill through GitHub/npm pricing separately from Node itself.
Stay on Active LTS releases for security patches; EOL nodes become compliance blockers fast.
Quick fit
Editorial take
Node.js should read as runtime plus infrastructure, not as a licensable product. The real risk and cost live in patch cadence, hosting shape, and the supporting services around the runtime.
What it does well
Primary use cases
Fit notes
Pricing snapshot
The official Node.js repository says Node.js is licensed under the MIT License. There is no Node.js runtime fee; cost comes from the compute, observability, package infrastructure, and optional commercial support arrangements you choose around it.

Apollo GraphQL
Free planGraphQL federation, routing, and schema governance
Commercial GraphQL platform for schema management, federation, routing, and API governance with free and usage-based GraphOS plans.
Choose Apollo when GraphQL has become important enough to need governance, routing, and federation workflows.