SarmaPlayerManaged IPTV platformA managed player for IPTV subscribers, built as a platform rather than an app: native TV and mobile clients, a zero-install web player, an owner dashboard and a staff operator console.
One API behind many clients.
Active JoinOperating system for jiu-jitsu academiesGyms lose members quietly — people drift off the mat weeks before anyone cancels.
A single GraphQL API over modular services, with authorisation enforced at field level so six audiences share one schema instead of one API per role.
Photo TrimiPhone photo library manager with USB backupFor people whose photo library outgrew their phone: browse 80,000 photos at 120fps, see at a glance what is on the device versus stranded in iCloud, clear whole months at once, and copy straight to a USB drive without a computer in the middle.
A native engine with an app around it.
My Photo CopyVerified photo backup to a drive you ownPhoto Trim decides what you can delete.
The same native core as its sibling, pointed at a different promise: a job engine that copies originals to an external volume and then reads them back to check them.
MammitoMulti-tenant care platformFamilies searching for a midwife find one in a verified catalogue by postcode and service, book and pay for the appointment, and meet in an encrypted browser consultation with nothing to install.
One modular API serving several host-routed frontends, with the tenant boundary pushed down into the database rather than enforced by convention in application code.
WiesnScoutSeconds-level availability monitorOktoberfest tables sell out months ahead, so the only real supply is cancellations — and they are gone in under a minute.
An edge-resident watcher feeding an alert path, with detection, deduplication and delivery as separate stages so latency can be measured and bounded at each one.
Content StudioHeadless publishing platform and editorial appA publishing platform born out of a rescue: a long-running news site on a legacy PHP stack, with roughly 100,000 articles, 65 GB of media and two decades of search ranking that could not be put at risk.
Headless: a read-mostly public API with a statically generated reader in front of it, and the editorial application as a separate client.
Consumer cameras keep your footage behind someone else's subscription.
A module-first backend with camera vendors behind a provider contract, so supporting a different kind of camera is an adapter rather than a rewrite.
PointPalReal-time estimation for agile teamsPlanning poker that holds up in a real session: persistent rooms, owner and host controls, rounds with reveal and reset, reactions and an activity feed — and state that survives a refresh, a dropped connection or a laptop closing mid-vote..
One durable coordinator per room makes each session a single-threaded authority, which removes distributed locking and split-brain votes from the problem instead of solving them.
A demo app for Amazon Vega OS, the new Fire TV operating system, built to show it at the next.app devCon 2026 booth in Berlin.
A Vega OS TV app as the centrepiece, with two supporting pieces around one typed contract: a phone page with a hidden booth view, and an edge API.
Booking and scheduling software for ski schools and outdoor instructors, taken far enough to judge whether the product is worth building: positioning, feature architecture (dispatch calendar, POS with Austrian and German fiscal compliance, wallet ticketing, shop widgets, accounting exports), brand, copy and a marketing site — without writing the application behind it..
Deliberately no application: a prerendered site over a design system with the brand as a swappable layer, built to answer a product question rather than to run.
The stack behind them
None of this is CV padding. Every technology here is running one of the builds above right now. I picked each one for a specific problem, then lived with it long enough to know where it hurts.




