
Product and platform engineering
I build the backend that has to keep running: APIs, workflows, data models, queues. The same engineer from first design to the pager.
What it covers
- Backends and APIs in PHP (Symfony, Laravel), Python (FastAPI, Django), Node.js and TypeScript, and Go.
- Workflow engines, queues and background jobs, with message brokers where the load calls for them.
- Data models and safe production data changes: MySQL, PostgreSQL, Redis, MongoDB.
- Front ends where the product needs them: Vue, React, Next.js, and mobile with React Native.
- Document and media pipelines: PDF generation and signing, video processing, real-time video.
- A flight-booking validation service for a travel shop: one API that confirms a booking at checkout in seconds (Obsentum).
- A custom Go + S3 image service that cut an online shop's image bill by more than 99% (Obsentum).
Track record
99.998%uptimeStudentTenant.com, over seven yearsMaster–slave replication, watched by Grafana and Uptime Kuma. About 74 minutes of downtime in seven years.
< 2 mindeposit lodgingdown from 30–40 minutes per depositUK law: protect it within 30 days. Now the data arrives pre-filled; staff only check and confirm.
< 12 hviewing confirmeddown from a 5-day average; half within the first hour
100+APIs integratedpayments, invoicing, CRMs, deposit protection
−99%image delivery costcustom Go + S3 service for ObsentumServed through Cloudflare's edge, which also kept storage traffic low.
Measured in production, not in a demo.
How it runs
Understand the goal
What the business needs, in plain words, before any technology is picked.
Design the smallest thing that works
A first version that can be run and judged, not a plan that cannot.
Build in small, reviewed releases
Tests, review and a pipeline from the first week.
Run it
If you want it: monitoring, incidents and the next release stay with the person who built it.
What you receive
- Working software in your repository, with tests and a deploy pipeline.
- Documentation for the next engineer.
- A hand-over or ongoing support, as you prefer.
A good fit when
You need a product or platform built or taken over by someone who will also run it, and you want to deal with the person doing the work.
Need a backend that keeps running?
Send a short message: what you run, what worries you, any deadline.
Get in touch