A normal portfolio shows client work behind a login, under an agreement, with the numbers rounded. Ours shows the systems that run our own company, because we can be completely specific about those and because they are the ones that prove the point: these are the things an agency rents, and we built them.
Every figure on these pages carries the command, file or dashboard it came from and the day it was read. If a number here is stale, that is a defect and we would like to know. A guard in our build refuses to ship a claim that has no source and no date.
12 systems
The cluster we run our own company onA production Kubernetes platform, operated by the people who deploy to itA distributed data layer, chosen deliberatelyDistributed SQL, wide-column, cache, object storage and vectors — each for a reasonInference we run ourselvesModels, embeddings, vector search, speech and translation — on our own hardwareKnowing something is wrong before a customer tells usMetrics, logs and distributed traces, self-hosted and actually usedOur own mail serversPostfix, Dovecot and Rspamd — because deliverability is decided below the campaign toolOur own telephone networkAsterisk, Kamailio and FreeSWITCH, carrying real callsOur own video conferencingWebRTC media servers, TURN relays and the ICE path in betweenDocuments, signatures and the paperwork layerCollaborative editing, e-signature and OCR, built rather than boughtThis websiteA build that refuses to ship a page it knows is wrongThe attribution pipeline we wroteFirst-party tracking, from first visit to closed dealTwenty-two languages, done correctlyhreflang, canonicals and a translation pipeline that admits what it has not translatedA mobile application, in the storesReact Native with native modules where JavaScript will not do
Tell us what you are trying to do
A short conversation is usually enough to tell whether we are the right people. If we are not, we will say so and point you somewhere better.