Node.js development
We build server-side software on Node — APIs, tooling, and real-time features in JavaScript and TypeScript — the runtime our own product backends run on, built typed and tested.
Node's case is a simple one that has held up: one language across the browser and the server, the largest package ecosystem in software, and an event loop that handles many concurrent connections without a thread per request. For anything I/O-bound — an API talking to a database and a handful of services, a real-time feed, a build tool — that shape fits well.
We write Node in TypeScript by default, because the runtime's flexibility is a liability without types to hold the shape. Most of what we build sits on Fastify for HTTP work, but the same runtime carries the scripts, workers, and real-time pieces around it — the backends under Docusift, Memoria, and Lekha are all Node, typed and tested from the first commit.
What we build on Node
-
APIs and services
HTTP services, background workers, and the glue between them — typed, tested, and structured so the codebase stays legible as it grows rather than sprawling.
-
Real-time where it earns it
WebSockets and streaming for the features that genuinely need a live connection, built to hold up under real concurrency instead of demoing well and stalling.
-
Tooling and automation
CLIs, scripts, and build tooling in the same language as the app — one toolchain for the team to reason about instead of a second one to learn.
Related from Ekarche
Need server-side work in Node?
Tell us what the service has to carry. We will build it in TypeScript on Node — typed, tested, and structured to outlive the engagement.