Selected projects.

Challenge

HUBRAUM stores valuable vehicles near Munich and also offers vehicles for sale. The old website ran on Django, with Google Analytics and a cookie banner, and described the offering with adjectives instead of evidence. What was needed was a presence that shows concretely what customers pay for, and on which the team maintains its sales vehicles itself.

Approach

It started with personas and a content concept. From these came the copy and a new identity in anthracite and gold, in German and English. The site is built with Astro and runs on the client's existing server, without external services and without cookies for visitors; even the built-in visitor statistics work without cookies and without stored IP addresses. For sales, the team maintains vehicles and their photos in a separate area with roles and fixed permissions, and the photos get a watermark automatically. Invited VIP customers see preferential prices in their portal, and selected vehicles before anyone else. Sign-in works by passkey or password, and staff additionally need a second factor. In the database, row-level security decides who sees which data.

Outcome

The new site has been live since 14 October 2026 and has fully replaced the old one; the old addresses redirect. It no longer needs a cookie banner. The team maintains vehicles and client accounts itself. New versions go live without downtime, and everything is backed up every night.

Challenge

Create, schedule, and play content centrally across many distributed screens. Across web, Android, iOS, and Windows, tenant-separated and in unattended continuous operation on cheap hardware, often without a stable connection.

Approach

A multi-tenant cloud platform with its own layout and schedule editor, media library, and super-admin area. Plus the devices: a custom kiosk launcher takes over an Android device's home screen, starts and supervises the player, controls rotation, and provisions new devices itself. The player is built cross-platform (Kotlin Multiplatform), with all playback and scheduling logic in a shared core with a state machine, so it keeps running without a network and without supervision. Content and commands arrive in real time from the cloud. A custom engine scales a template, built once, without loss from Full HD to 4K, including unusual zone formats.

Outcome

A platform instead of one-off installations. New devices come online through provisioning without manual work, content reaches the screen in seconds, and the state of every player is visible remotely. Several tenants share the same system without getting in each other's way.

Challenge

Deliver live odds reliably across many displays in hundreds of betting shops, each with its own vendor branding and low latency. Over the years the requirement grew from a pure display into a whole device fleet that has to be managed centrally and kept up to date unattended.

Approach

I have worked on this odds display for around ten years, throughout as lead in the team. Across several generations it evolved from the native desktop client to the web; the move to the web renderer I carried out on my own. Today every display is driven by a single URL. For the latest version I added a complete, multi-tenant management system that controls over 250 installations centrally, up to eight monitors per location. Configuration, themes, translations, and software updates run through a custom API; device status, commands, and logs come back in real time. Where native clients are needed, a Windows kiosk runs with forced fullscreen and channel-based updates that complete without on-site work.

Outcome

A desktop display has become a centrally managed platform. Over 250 locations run under one management, new ones come on board without on-site work, updates roll out unattended, and faults are visible and controllable remotely.

Challenge

Operators in a heavily regulated gambling market must be able to prove at any time that they meet requirements: audit checklists, shift planning, working hours, and responsible-gaming monitoring. All tenant-separated, data-protection compliant, and audit-durable.

Approach

A multi-tenant platform with a Python/FastAPI backend and a React interface. Data protection (GDPR) and working-time rules are anchored in the data model and workflows, not bolted on afterwards. Modules for checklists, shift planning, time tracking, and responsible-gaming monitoring interlock. Built four-eyes, with shared architecture ownership in the team.

Outcome

A system that reflects day-to-day compliance instead of managing it in spreadsheets. Evidence is produced during operation and holds up under audit.

Challenge

A marketplace where sellers and buyers meet: listings, accounts, payment, multilingual. From the first draft to a working checkout, alone.

Approach

Built full-stack alone: interface, a data model with row-level access rules, sign-in, file storage, and payment via an established provider. Designed trilingual. Particular care for the tricky spots like sign-in, where timing bugs quickly turn into problems, and for a clean checkout.

Outcome

A working marketplace with real payments, delivered in a manageable time by a single person. Proof that I take a product from idea to checkout on my own.