Event ticketing
Ticketeer
A multi tenant event ticketing platform: per event storefronts, WhatsApp ticket delivery, and on site QR scanning, with an isolated ticketing instance behind each organizer.
The problem
Ticketing that organizers can actually run
Event organizers in our market juggle a storefront, payments, a guest list, and door check in, usually across separate tools that do not talk to each other. Generic global ticketing platforms take a heavy cut and are a poor fit for local payment habits and the way tickets actually reach attendees here, which is messaging, not email.
The result is manual reconciliation, tickets that get lost in inboxes, and a check in process that falls back to paper and spreadsheets when the internet is slow at the venue.
The approach
A tenant per organizer, on a proven ticketing core
Rather than build a ticketing engine from scratch, we run a hardened fork of the open source Alfio reservation system as the per tenant core, and wrap it with our own provisioning, billing, and delivery layers. Each organizer gets an isolated instance from a standard container image, so one tenant cannot affect another.
Around that core we built our own services: a Node and Express API that handles tenants, clients, and admin, a React customer app and an admin dashboard, a WhatsApp sender for delivery, and a mobile scanner for the door. The pieces are separate services so each can be deployed and scaled on its own.
What it does
Features
Multi tenant provisioning
Each organizer gets an isolated ticketing instance, provisioned from a standard container image rather than a shared database row.
Per event storefronts
Public attendee pages for browsing events, reserving, and paying, served per tenant.
WhatsApp delivery
A dedicated sender service delivers tickets and messages over WhatsApp instead of relying on email alone.
On site scanning
A mobile scanner app validates QR tickets at the door and lets sponsors collect contacts.
Organizer dashboard
An admin surface for events, orders, and tenant settings, backed by role based access.
Payments
Card payments wired through Stripe on the attendee checkout.
Tech stack
Status and roadmap
Where it stands
Ticketeer is in production. The API, the customer app, the admin dashboard, the per tenant ticketing core, and the scanner are all built and deployed, served from the theticketeer.com domains. The mobile scanner is on its established build, with a newer rewrite in progress. The WhatsApp sender is live, and we are tightening its integration with the ticketing core.
[TODO: confirm with Nour the public production scale, active organizer count, and which scanner build is current, before publishing any numbers. Also confirm the live ownership and org for each repo, since the inventory shows both Blue202Labs and MyClicx remotes.]
Running an event and tired of stitching tools together
Tell us how you sell and check in today, and we will show you how Ticketeer handles it end to end.
More from our portfolio