Red Eye Tickets.
Built for the night.

A live ticketing platform designed around buyers, producers, operations teams and the front door.

My role
Co-Founder & CTO / Sole technical contributor
Context
January 2024–present / Custom launch Oct. 2025
Medium
Product / Interaction / Full-stack engineering
Red Eye Tickets red and white identity on a glowing dark red background
Red Eye Tickets identity. The interface captures below are sanitized production evidence from the existing portfolio.

Design for
the real world.

Red Eye began as a ticketing business with a WordPress MVP. I rebuilt it as a custom platform shaped around the people using it: buyers checking out, producers managing events, administrators handling support and staff admitting guests.

The contribution

As the sole technical contributor, I owned product direction, workflow discovery, architecture, full-stack implementation, operational tools and production support. The product was shaped with my co-founders, the operations team, producers and direct observation at live events.

At the front door

When the line is moving, a staff member needs an immediate answer. The successful scan state puts a clear admission decision on screen. Event controls and manual entry provide a recovery path when camera scanning is unavailable or inappropriate.

Beyond the interface

The experience connects checkout, payments, inventory, mobile admissions, refunds and reporting. Those workflows need to share a dependable view of an order rather than become separate screens with competing answers.

End-to-end product ownership. Sole technical contributor describes my engineering scope. The business and its requirements were shaped collaboratively. No improvement percentages or business outcomes are attributed to the design here.

Up next — Selected workWanted ↗

For a closer look at implementation decisions and production accountability.

Review the engineering evidence (opens in a new tab)

Have something you’d like to make?

Start a conversation