Resources
Notes from the builds,none of them gated
Six write-ups drawn from systems we actually shipped. None are published yet, so each is marked as such โ an unwritten article is not a lead magnet.
6
Systems documented
case study each
21
Service pages
each proof-linked
0
Gated downloads
no email wall
โ
Published articles
awaiting verified score
Engineering notes
What we would write up,drawn from systems we shipped
Tenant isolation in a RAG platform
Why scoping retrieval at the storage layer beats filtering results after the fact, and what it costs in index management.
not written yet
Five deep-learning modules, one pipeline
Shared feature engineering across demand, price, and risk models โ and where that sharing stops paying off.
not written yet
Modelling a hospital as 39 tables
The clinical schema behind six role-based portals, and the relationships that took three attempts to get right.
not written yet
Offline-first on a real exam day
Sync, conflict resolution, and what breaks when a thousand students lose signal in the same building.
not written yet
Three Tailwind failures that silently hide content
Opacity modifiers on arbitrary colours, commas in arbitrary values, and reveal animations with an invisible resting state.
not written yet
What a two-week AI assessment actually produces
The architecture, the cost model, and the use cases we recommend killing.
not written yet
Straight answers
Six questionsasked on every first call
Who owns the code?
You do, from the first commit โ not on final payment. We work in your repository under your organisation.
Where does it run?
Your cloud account, under your keys. We hand over infrastructure, not access to a hosted black box.
What happens when the engagement ends?
You get runbooks and a documented handover, written during the build rather than assembled at the end.
How big is the team?
Five engineers. That caps how much we run at once, and it is why the person who scoped your system is still on it a year later.
Do you sign NDAs?
NDA is the default position, which is why most of our delivered work is not named anywhere on this site.
Can we talk to a client?
Ask, and we will ask them. We do not publish quotes without written permission, but we will make an introduction where the client agrees.
Page index
Everything on this site,in one list
Services
No email wall
Nothing here is gated because a PDF is not a relationship
If you want the architecture behind one of our 5 live systems explained, ask an engineer directly. That is faster than a whitepaper and considerably more accurate.
Talk to an engineer