Service 03 · APIs · Web apps · Infrastructure
Back-ends built to be handed over.
APIs, web apps, admin panels and the data behind them. Documented, tested and in your repositories, so the day you want to leave us is easy. That is why people stay.
01 — What's included
Everything behind the screen.
A new system, or the missing half of one you already run.
02 — How we build back-ends
Boring technology, exciting results.
We pick stacks that will still be maintained in five years and that a new engineer can read on day one. Novelty goes into the product, not the plumbing.
Every endpoint has tests that run in CI. Every service has a README, an architecture note and a runbook. Every secret lives in your vault, not our laptops.
Monolith first. Services when the numbers say so, not when a conference does.
Tested
Unit and integration tests on every endpoint, run on every commit
Documented
README, architecture notes, runbooks: productive in a day
Yours
Your cloud, your repos, your domain, from the first commit
Scalable when needed
Monolith first, services when the numbers say so
03 — How it runs
What you get, week by week.
Week 1
Scope
You get: a data model, an endpoint list and an estimate.
Weeks 2–8
Build
You get: a deploy to staging every week and a shared board.
Weeks 9–10
Harden
You get: load test results, a security review, monitoring and alerts.
Launch
Release
You get: production in your account, runbooks, and a handover or a support plan.
04 — Pricing
Fixed scope
For a system with a defined endpoint and screen list. Price and date in writing.
Dedicated team
Senior engineers on your product, monthly, cancel with 2 weeks' notice.
05 — Questions
About back-end projects.
Node.js with TypeScript and PostgreSQL by default, Python where the AI work lives, React or Next.js on the front. If your team already runs something else, we fit in rather than rewrite.
Yes. That is a separate service with its own process: an audit first, then stabilise, then refactor. See Rescue and refactoring.
In your cloud account, under your billing, with infrastructure as code in your repo. AWS and GCP most often; others on request.
Secrets in a vault, least-privilege access, dependency scanning in CI, a security review before launch, and a third-party penetration test if your market requires one.
Get an estimate
Send the spec, or the napkin. We send back a data model.
A paragraph is enough to start. After one call you get a written scope and an estimate, whether or not you go on with us.