Service · 04 · Backend
A backend your web or mobile clients can trust — documented enough to keep building on.
APIs, databases, authentication, payments, webhooks, and the admin around them. We stand up a backend for a new product, or we add the slice an existing app is missing.
Two paths. Same studio. Pick the one that matches — both are in scope.
Path A · Greenfield
Data model, API, auth, and the first integrations — shaped for the clients you already have or are about to build.
Path B · In production
New endpoints, Stripe or OAuth, a queue, a migration. We work in your repo and keep current clients working.
The product shapes inside this service, in plain terms.
REST (and BFF patterns when the web app needs them). Typed contracts, not a folder of mystery routes.
JWT, OAuth, roles, Stripe subscriptions and webhooks — the unglamorous path money and accounts take.
PostgreSQL or MongoDB, Prisma when it fits, indexes and the queries the product actually runs.
Admin and support tools so you are not SSHing into production to refund a user.
What you can expect in scope when this is the brief.
API design and implementation
Auth, roles, and session/token handling
Payments and third-party webhooks in scope
Database schema and the admin needed to operate it
Live products where this kind of work actually shipped.
A studio cut, not a staff-aug black box.
Clients, data, and the jobs the API has to own.
Endpoints, auth, and what must not break for existing apps.
Services, data, integrations, an admin if you need one.
Deploy notes, env, and a path for the next endpoints.
Map → contract → build → ship
Straight answers. The rest belongs in the brief.
Yes. New APIs, or endpoints and integrations on a running Node/Express/Nest app. Greenfield only when there is nothing to join.
Stripe, webhooks, JWT and Google OAuth are in production on our atlas products. We do not treat them as “phase two”.
We can ship backend only, or take the client too. If the UI is in another team, we agree the contract and mock what they need.
Not for sport. We extend what you have unless it cannot carry the next feature. Then we say so before writing a migration.
Same studio. Different job.
Field intake
This form is already tagged for backend & integrations.
