- Role
- Product Engineer · Full-Stack Developer
- Stack
- Astro · Vite · Firebase
- Links
In one minute
EurekTickets is a production ticketing platform created for an event producer that wanted direct control over its ticketing operation rather than depending on high-commission third-party platforms. Roberto owned the product end to end, from requirements and business logic to frontend, backend, ticket workflows, and payment integration.
The problem
The company historically relied on providers such as e-ticket and Star Ticket. They wanted their own platform to reduce third-party commissions and gain direct control over tickets and event operations.
My role
- Frontend
- Backend
- Business logic
- Requirements discovery and direct client communication
- Ticket-type modeling
- Physical-versus-virtual ticket workflows
- Payment integrations
Product capabilities
- Event creation
- Ticket type and quantity selection
- Ticket sales, assignment, and verification
- Personnel management
- Sponsor management
- Physical and virtual tickets
- Buyer profile and identification
- Checkout and payment flows
Walkthrough
Purchase flow: order summary and email capture. 
Gate check: entry-code verification, invalid-code result.
The engineering behind it
A transactional ticketing product whose payment flow had to live with external provider constraints and approvals — not just with the domain model of events and tickets.
Architecture
Astro and Vite on the client, with Firebase for the platform.
Payment-provider dependency
The original payment-gateway integration reached a provider-approval dependency that kept online card charges out of production. Rather than presenting the product as complete, the system kept operating through SINPE and bank transfer while another payment integration was completed.
The earlier financial institution is not named here.
Current status
In production and used in real event operations.