E-Commerce / Current / In active development

eventOS

Currently designing and building eventOS end-to-end: organiser workflows, public event surfaces, ticketing, payments, access control, subscriptions, support operations, and internal platform administration.

Commercial and operational implementation details remain private during active development.

What this system solves

Event organisers need one operational system for event creation, ticket sales, attendee communication, payments, door access, support, and platform administration.

System overview

I own both the product design and technical implementation across the public site, organiser dashboard, backend services, internal operations, ticket delivery, and door workflows.

What I built

• Designed organiser onboarding, event creation, subscription, payout, and support journeys.
• Built public, organiser, backend, and internal operations surfaces.
• Implemented ticket delivery, door access, provider integrations, and reporting.

Architecture

• Public, organiser, internal-admin, and backend surfaces share explicit domain contracts.
• Server-owned transitions govern ticket, payment, identity, subscription, and access workflows.
• Operational permissions are isolated from normal organiser and customer actions.

Limitations

• The platform remains in active development, so launch metrics are not yet public.