Do you build GraphQL as well as REST?

REST is the default because it is easier to cache, easier to debug and easier for another engineer to pick up. GraphQL is worth it when many clients need different shapes of the same data — we will say which one your case actually is.

Can you take over a backend nobody currently maintains?

Yes. Inherited services are normal. The first deliverable is usually a written map of what the service does, what is safe to touch, and what is quietly broken.

Do you handle deployment and infrastructure?

Yes — Docker, AWS and Vercel, including environment configuration, health checks and the rollback path. Infrastructure that only one person understands is a liability, so it gets documented.

Node.js Backend & API Development

APIs that hold their shape under load.

We design and build Node.js backends: the REST APIs your frontend depends on, the data models underneath them, and the boring reliability work — validation, rate limiting, error handling — that decides whether a service survives its first busy week.

What this includes

REST APIs in Node.js and TypeScript

Express services written in strict TypeScript, with request bodies narrowed through explicit type guards rather than trusted. Every route validates before it acts.

Data modelling

MongoDB, PostgreSQL and MySQL schemas designed around the queries the product actually runs, with indexes and retention rules chosen deliberately instead of inherited.

Security and abuse resistance

Origin checks, rate limiting, honeypots, strict Content-Security-Policy headers and secrets that never reach a response body. This site itself runs a nonce-based CSP with no inline scripts.

Backend performance

Profiling slow endpoints, cutting redundant queries and reworking algorithms for lower resource consumption — the work behind a 30% platform performance increase on a previous product.

Numbers

30%measured platform performance increase
12moautomated data retention enforced by TTL index
0credentials leaked in error responses, by design

Evidence

Backend work here includes a secure translation-unit management platform for enterprise customers, a DNA research system on AWS and Firebase, and contributions to PHPMailer, an open-source library used across the PHP ecosystem.

Tech stackNode.js · Express.js · TypeScript · MongoDB · PostgreSQL · Docker · AWS

An enterprise translation memory platform in the cloud
A secure, scalable Translation Memory Cloud platform for enterprise-level translation-unit management, built and maintained over two years at TransPerfect.
Read the case study →
A DNA research platform on React, Redux and AWS
A high-performance DNA research system — Netgenomics.life — developed and maintained for scalability and reliability using React, Redux, AWS and Firebase.
Read the case study →

Common questions

Do you build GraphQL as well as REST?: REST is the default because it is easier to cache, easier to debug and easier for another engineer to pick up. GraphQL is worth it when many clients need different shapes of the same data — we will say which one your case actually is.
Can you take over a backend nobody currently maintains?: Yes. Inherited services are normal. The first deliverable is usually a written map of what the service does, what is safe to touch, and what is quietly broken.
Do you handle deployment and infrastructure?: Yes — Docker, AWS and Vercel, including environment configuration, health checks and the rollback path. Infrastructure that only one person understands is a liability, so it gets documented.