Case study · 2025-2026
Tixello: the ticketing platform my marketplaces also run on.
A SaaS for event organisers: they put their event online, sell tickets on their own site or on marketplaces, scan at the entrance and get paid, with invoices issued automatically. Underneath it is ePAS, the platform that AmBilet, bilete.online and Viaqui also run on.
- Role
- Founder. Product, architecture, code
- Period
- October 2025 - present
- Status
- Live on tixello.com
- Stack
- Laravel 12, Filament 4, Livewire, PostgreSQL, Redis
- The problem
- A small or mid-sized organiser pays high commissions and works with separate tools for sales, entry, invoicing and marketing.
- What I built
- A single platform, with an organiser panel, payments, seating maps, scanning, e-Factura and integrations. All the code also serves the marketplaces.
- The result
- 410,444 tickets and €5.2M processed, according to the public counter on tixello.com. The commission starts at 1%.
- 410,444 tickets sold through the platform
- 107,255 customers who bought
- 5,016 events
- €5M processed
The public counter on tixello.com, cumulative, read on 5 November 2026. I did not split it by organiser or by marketplace.
01 · The problem
The organiser pays a lot and works in five places.
An organiser of concerts, theatre or stand-up needs several things at once: the event page, ticket sales, the venue map, entry scanning, invoices, the report for the record label or the venue. They usually get them from different suppliers and pay a commission to each.
I started from the AmBilet experience: I already had a ticket marketplace and knew what organisers ask for. I built a platform that does all of this in one place, with a commission that starts at 1% and no fixed costs.
02 · What it does
From the event created to the money received.
The organiser creates the event, the ticket types and, if they have one, the venue map, drawn in the seating editor. They sell on their own site, through a widget, or on the connected marketplaces. At the entrance, the team scans tickets from a phone. After the event they see the sales, the attendees and the settlement.
Besides tickets, the platform has discount codes, affiliates, gift cards, newsletters, sales at the door (POS), cashless payments at festivals and integrations with marketing and CRM tools.
03 · The architecture
A single codebase, several kinds of customers.
ePAS is a single Laravel application with five Filament panels: admin, organiser, marketplace, operator and seller. Each organiser is a separate tenant in the same database, and every row is filtered by the tenant it belongs to.
- 01
Organisers
- Panel with 66 sections
- Events, orders, customers, seating maps
- Invoices, reports, team
- 02
The ePAS core
- Tickets, orders, payments, settlements
- Seat holds in Redis, with expiry
- Queues for emails, invoices, balances
- 03
Payments and tax
- Stripe, Netopia, PayU, EuPlatesc
- e-Factura (Romania’s national e-invoicing system) to ANAF (the Romanian tax authority)
- VAT on the date of sale
- 04
Sales channels
- Widget on the organiser’s site
- Marketplaces: AmBilet, bilete.online, Viaqui
- API and 21 integrations
The marketplaces are separate sites that talk to ePAS through an API with their own key. A new module is switched on only for the tenant that uses it.
04 · Components
What I built.
The organiser panel
Everything an organiser does, from creation to settlement.
- Events, tickets, dynamic pricing
- Seating map editor, with SVG import
- Discount codes, affiliates, group bookings
- Points, badges and rewards for customers
- Blog, pages and newsletters
At the entrance and at the event
What happens on the day of the event.
- Web scanning app, made for iPhone
- Sales at the door (POS)
- Cashless and NFC payments at festivals
- Mobile app for customers and organisers
Money and tax
The part that has to add up to the last cent.
- Four payment processors, behind the same interface
- Invoices and e-Factura, with a test adapter
- Company lookup by CUI (company tax ID) at ANAF
- Organiser balance recalculated after every sale or refund
Integrations
21 connectors, each switched on only on request.
- HubSpot, Salesforce, Zapier, Slack
- GA4, Google Ads, TikTok Ads, Meta CAPI
- WhatsApp, SMS, Zoom, Google Sheets
- Public API for developers
05 · The organiser’s money
Three calculations for the same settlement.
In summer 2026 I did a full audit of the settlements. I found three different ways of calculating how much an organiser receives: a breakdown saved at the moment of sale, a calculation redone on request and a reporting service. Most of the time they gave the same figure. But not every time.
The fix was a single source of truth: the organiser’s balance is recalculated in a queue after every sale, refund or adjustment, and reports read only that balance. When it is someone else’s money, two calculations that “usually” match mean a problem.
06 · Metrics
What I counted.
The sales counter is the public one on tixello.com. The code figures are counted across the whole ePAS repo, so they also include the marketplace part.
- 410,444tickets sold, cumulativefrom the site
- €5.21Mprocessed through the platform (27.8 million RON)from the site
- 6,521commits, since 28 October 2025git
- 230Filament panel sections, across four panelsin code
- 843database migrationsin code
- 4payment processors and 21 integrationsin code
How much code
- 544
- data models
- 843
- migrations
- 230
- Filament resources
- 5
- panels
- 58
- test files
- ~557k
- lines of PHP in app/
Counted on 5 November 2026, across the whole repo, marketplace code included.
07 · What I learned
What I take with me.
Money needs a single source
Any figure about money is calculated in one place. The rest of the application only reads it.
Change the database only by adding
On a live platform, migrations add columns and do not delete or rename them. I use text instead of enum types, so a new value does not need a risky migration.
Small details stop the queue at the entrance
QR codes now get a white margin. Without it, some scanners could not read tickets on phones with a dark theme.
A shared platform makes a new marketplace cheap
bilete.online and Viaqui started on payments, tickets and a panel that already existed. I built only what was new for them.
08 · Further
The marketplaces built on Tixello.
AmBilet, the ticket marketplace, moved from WordPress to ePAS. bilete.online, attractions in Romania. Viaqui, the same idea for all of Europe.
Do you need a platform with payments and many customers?
I build SaaS products and marketplaces, with payments, invoicing and panels for every role. Write to me and we will see if it fits.