Platformatic is an Apache-2.0 open-source monorepo whose flagship runtime, Watt, is a Node.js application server that takes any Node.js application written in any framework and runs it as a worker thread so teams can ship faster and scale in containerized environments.

What it is

Platformatic is an open-source monorepo that ships Watt, a Node.js application server. Watt takes an existing Node.js application, regardless of the framework it was written in, and runs it inside a worker thread rather than on the process's single main thread. The project is published to npm as the wattpm package and lives in the JavaScript ecosystem alongside Node.js, Fastify, and the frameworks it hosts. It is licensed under Apache-2.0 and carries the topics fastify, graphql, nodejs, openapi, and rest.

The concrete problem Watt addresses is Node.js's single-thread execution model. When Node.js runs as a single thread, it fails to consume the CPU cores allocated to it, and the event loop blocks under heavy traffic, which produces latency spikes and crashes. Because that same thread also carries telemetry, an application crash takes observability data down with it, leaving teams without the information they need to troubleshoot. Container orchestrators, in turn, do not measure the metrics that matter for scaling Node.js, so new pods are not added until it is too late, forcing teams to over-provision services or accept downtime. Watt replaces that single-thread default with a multi-threaded architecture that manages worker threads outside the application process.

Key capabilities

• Runs any Node.js application as a worker thread, using a multi-threaded architecture to use multiple CPU cores; the project cites applications running up to 93% faster.
• Auto-heals and scales worker threads in seconds to hold latency low at p95 and above.
• Provides built-in observability managed outside worker threads: logging, metrics, tracing, health checks, and performance profiling including heap profiling and CPU flamegraphs, so telemetry survives an application crash.
• Consolidates frequently co-orchestrated services such as BFFs and microfrontends into the same process, removing network calls between them.
• Auto-generates REST and GraphQL APIs, with OpenAPI among the project's topics.
• Integrates with Astro, Next.js, Nitro, Nuxt, React Router, Remix, TanStack Start, Vite, NestJS, and plain Node.js.
• Ships TypeScript-first with auto-generated types and an SDK, plus Docker deployment, environment configuration, and scaling built in.

Who uses it and how

• Teams running Node.js services in Kubernetes or another containerized environment, where Watt supplies Docker deployment and built-in scaling.
• Teams whose event loop blocks under heavy traffic and who need worker threads auto-healed in seconds rather than manually managed.
• Teams consolidating BFFs and microfrontends into a single process to eliminate network hops between services that are always deployed together.
• Teams migrating existing Express, Fastify, or Next.js applications, using the port-your-app guide and framework integration guides.
• Developers new to Node.js following a step-by-step tutorial that builds a complete Todo API in about 30 minutes.

Getting started

Install globally with npm install -g wattpm, scaffold with npx wattpm create my-first-app, then run cd my-first-app && npm start. The application serves at http://localhost:3042 with auto-generated REST and GraphQL APIs.

How it compares

No competing products are named in the facts, so the project stands alone in this registry on this point. Its comparison is with the default single-thread Node.js runtime itself, which it replaces.

When to use it — and when not to

A self-hoster must operate the runtime inside a containerized environment and take on worker-thread lifecycle management, Docker deployment, and environment configuration, with documentation hosted externally at docs.platformatic.dev. Teams that do not run containerized Node.js workloads, or that are unwilling to adopt a runtime layer between their application and the platform, should not pick it up. Note also that the repository README excerpt functions largely as a landing page, so the capabilities above are documented across the linked external documentation rather than in the repository itself.

npm install -g wattpm
npx wattpm create my-first-app
cd my-first-app && npm start