A white-label platform:every client’s brand from one design system.
Multi-tenant SaaS · web · admin · native app
Head of Development on a German SaaS platform. Every client gets a branded virtual venue on its own domain, with live streaming, moderated Q&A, chat, commerce, and a native app sharing one design system with the web.
The product and the need
Event organisers wanted their own venue, not a shared platform with their logo on it. So every client’s space runs on its own domain, in its own colours, type and logo, from the same code.
How it is built
One design system, themed per client
One design system
Components, tokens and states, shared by the web and the native app.
Every client’s venue
Their colours, type and logo, on their own domain.
The native app
The same components, on iOS and Android.
Decisions that held
A deliberate monolith
One fast main server, with the heavy work on stateless workers. Microservices were left out on purpose: their complexity would have cost more than it saved.
Secure by default
Every endpoint declares its permission through one decorator, so an unprotected route is an exception anyone can see in review.
Streaming that pays for itself
Live streaming moved from AWS to dedicated Hetzner servers, with the video segments cached, when traffic costs outgrew the cloud.
A client’s venue
Walk through the venue
Working model
I started the codebase, then led a small team while still writing most of the code: about six commits in ten are mine. Still on it today, every working day.