EventMS PRO

The problem

Event operators run ticketing, registrations, vendor coordination and reporting across disconnected spreadsheets and single-purpose tools. Nothing joins the money to the logistics, so every event ends with someone reconciling numbers by hand.

What I built

1. 01Designed the domain model as one relational schema covering events, ticket tiers, registrations, vendors and payouts, rather than bolting separate modules together.
2. 02Built the Laravel REST API with authentication, role-based access, and queued jobs for the email and reporting workloads that would otherwise block a request.
3. 03Built the Nuxt SSR frontend against that API, with a dashboard for operators and a public registration flow.
4. 04Packaged the system with Docker for reproducible deployment into customer environments.

Outcome

First commercial license sold to kulturgehtweiter.de, a German cultural-events operator. The platform runs their event operations in production.

Stack