Event commerce · Entrello
Entrello
From the seating chart to the organizer payout: one system.
My role:Lead frontend
Platform-wide scale of the system I built: the admin, seating and the staff app.
Web · mobile · desktop · hardware
Every surface talks to one backend. Tap a node to jump.
The front door
The public face
entrello.app, the marketing site where organisers first meet the platform. One brand, before a single ticket is sold.
Act 1 · Storefront
The buyer storefront
Live: try it yourselfBrowse an event, pick a seat on a Konva map, pay with Stripe, get a QR ticket.
Act 2 · Admin
Entrello operator workspace
A real operator workspace, not a pretty dashboard. Teams sell, refund and export on their own. Under the hood: permission-gated routes, Apollo/GraphQL, URL-driven modals, export polling.
Act 3 · Seating
The seating editor
Design a hall on canvas, then sell those exact seats.
One Konva engine, two sides: the editor in admin and live seat-pick in the shop.
Act 4 · Campaigns
Campaigns & email, built in
Marketing lives inside the platform, with no exports and no separate tool. A GrapesJS / MJML email builder and Canva media, built right in.
Act 5 · The staff app
The box office, in your pocket
The same platform in the operator's hand: a React Native / Expo app for the day of the event: season occupancy at a glance, QR ticket check-in, and Tap to Pay on iPhone. Built for the door, in light and dark.
Act 6 · The door
The door & hardware
Where the software meets the gate: handheld QR scanners, tap-to-pay terminals and thermal printers that spit tickets in seconds.
My role
What I owned
I owned the entire product frontend, from architecture to payment surfaces and permission gating, and shipped it across web, mobile and desktop.
Lead frontend
- Product architecture
- Frontend
- Admin UX
- Payments & payouts
- Permissions
- Ops tooling
Outcome
I turned a ticket shop into an operator workspace.
Teams now sell, scan, refund, export and report on their own, with no developer in the loop.
The hard part was keeping risky money and seating actions fast yet safe: permission-gated, URL-driven state, audited mutations.
Real venues running on the platform
- Theater im Park
- Globe Wien
- Steirischer Herbst
- WABE
Stack
Built across every layer
Need something at this scale?
I can own a payments-grade, hardware-integrated platform end to end.