Ongoing engineering for a US software company
A long-running retained engagement: senior engineering capacity for a US client, working their hours, in their repositories, invoiced in USD from India.
Home / Work
WRK/ — Engagement notes
What we've actually built.
Not case studies. Notes on real work, written plainly — what the situation was, what we did, and what we'd tell you if you asked about it over a call.
Replacing a 5-container invoicing platform with one container
We deployed a well-known open-source invoicing suite, found it was five services and a database to produce four invoices a year, and replaced it with a purpose-built tool in a day.
A hardened public VPS with a push-based deploy pipeline
The site you're reading: an ARM cloud VM locked to three ports, deployed from a CI runner that the server cannot reach back to, with scanning as a release gate.
HON/ — About this page
Why the list is short.
It would be easy to fill this page. Plenty of consultancy sites carry four glossy case studies about clients in New York, London, Berlin and Singapore, and a fair number of those clients do not exist.
We'd rather have a short honest list. If you need references before engaging, ask — that's a conversation we're happy to have directly, and it's worth more than a page of anonymous praise you have no way to verify.
The rules we follow here
- No client is named without written permission
- In-house builds are labelled as in-house, not implied to be client work
- Nothing is invented — no composite clients, no aspirational projects
- Failures are included. One of these notes is about deploying something and throwing it away the same day
CTA/ — Your project
Want to be the next one?
Tell us what you're dealing with. If we're a fit you'll get a plan and a price; if we're not, you'll get a straight answer and, where we can, a pointer to someone better suited.
Start a conversation →