How the products on this site were actually built — the decisions, the constraints, and the things that turned out to be hard for reasons nobody predicted. Most of these are our own products, which is the only reason they can be this specific.
We built our own streaming and batch speech-to-text service to sit alongside a managed provider — partly for cost at volume, partly for the workloads that cannot leave our infrastructure. The design problem was idle GPU cost, and the answer was to have no idle GPUs.
Zeno is eight applications — CRM, Work, Desk, Docs, HR, Campaigns, POS and Dev — sharing one API, one Postgres database and one design system. The interesting engineering is in what they share, not in any one of them.
Mavio transcribes meetings in real time across desktop, mobile and a browser extension. The hard parts were never the model — they were system audio capture on two operating systems, speaker attribution over a noisy channel, and retention rules that differ per artefact.