Cilantrobyte.

Tech Stacks · Backend

Node.js

The default backend runtime for JavaScript shops.

Category

Backend

At the studio

Since 2019

Projects shipped

2 case studies

Status

Active

(01) Our take

Most of our backend work runs on Node. The concurrency model suits I/O-heavy workloads, the package ecosystem is unmatched, and sharing code between frontend and backend is a real productivity win. We typically pair Node with Hono for new services and Express for inherited ones.

For Node-native tooling we lean on Bun in local development but still deploy Node for production. Bun's maturity curve has been steep but we want two years of production history before we trust it under real load.

(02) What we build with it

Typical work

  • REST and GraphQL APIs
  • Realtime services (WebSockets, Server-Sent Events)
  • Background job processing
  • BFF (backend-for-frontend) layers

(03) How we engage

Engagement shape

Usually paired with a Next.js or mobile frontend. Standalone backend-only engagements are rare — we typically own the stack end-to-end.

(04) In production

Where we've shipped it

All case studies →

(05) Pairs with

Works well with

Technologies we reach for alongside Node.js in most engagements.

Frontend

TypeScript

Strict mode, no exceptions.

Backend

Hono

The Express replacement we wish we'd had five years ago.

Data

PostgreSQL

The default database. For almost everything.

Infra

AWS

The default cloud when compliance, scale, or sovereignty demand it.

Thinking about a Node.js project?

Start a project →back to all stacks