Labs / L-01 · Product system · Active
eventOS
The operating system for events.
DZND Labs’ event platform. It carries one event from setup and ticket sales, through the door on the night, to the audience work afterwards, and lets partner websites sell tickets through it.
Create. Sell. Admit. Settle.
01 / The system
One event file. Every operational layer.
The problem
eventOS started from the practical problem of publishing and selling access to events. The product now carries organiser workspaces, public discovery, ticket state, admission, refunds, audience communication and settlement context.
The concept
The public event experience and organiser workspace are different surfaces of the same system rather than disconnected tools.
Not a ticketing website
Ticketing is one stage of four. The same record is created, sold, admitted at the door and settled afterwards, and it changes as the room fills.
02 / The lifecycle
Four stages, one record.
Choose a stage. Each is shown on the product itself.
Configure the event and its commercial structure.
- Event creation
- Ticket tiers
- Promo codes
- Guest lists
- Capacity setup
- Source tracking
03 / Two sides of the same ecosystem
For organisers.
Control, configuration, sales, analytics and operations, in one workspace.
Every organiser task in one place, from verifying the account to running event day and reading the payout.
Customise your events
One identity, uploaded once and carried through the event page, tickets, wallet passes, emails, social assets and the scanner. Four event types, as the product shows them:
For attendees.
Discovery, tickets, saved events, reminders and a personal calendar of the events you care about.
Discover
Search by event, artist or venue, then narrow by category, city and date.
Your tickets
Open a ticket by its reference, then download, transfer or present its signed QR at the gate. Ready without the network.
Your calendar
Save eventOS events or add any event from the web. Going, watching, maybe and saved; private notes; in-app, email and push reminders; export to the device calendar.
04 / Event day
Uninterrupted check-ins, even when venue internet becomes unreliable.
01
Valid
Access confirmed. VIP, main room, guest 428.
02
Already used
Ticket scanned earlier. First entry recorded at 20:31.
03
Wrong event
Access not permitted. The ticket belongs to a different event.
04
Manual review
Operator decision needed. Guest record found with a name mismatch.
eventos.ng / Door operations, the four responses a scan can return
05 / Infrastructure
Use the product, or integrate its API.
Run eventOS end to end, or keep your own website and app while eventOS powers ticketing, payments, event operations and attendance through scoped APIs and signed webhooks.
In use
Kilogbede Records, whose platform DZND built, sells its tickets through eventOS.
Growth network
Affiliates get a private referral workspace, tracked attribution and earnings, and configurable settlement windows.
06 / DZND’s role
Conceived and crafted by DZND Labs.
eventOS is DZND’s own product: not a website made for a client, but a product DZND conceived, shaped and runs, live at eventos.ng.
- Product strategy
- From the practical problem of selling access to events, to an operating model for before, during and after the event.
- Product design
- Organiser workspaces, public discovery, ticket state, admission, refunds, audience communication and settlement, as one product.
- Experience architecture
- The public event experience and the organiser workspace as surfaces of the same system, not disconnected tools.
- Interface design
- Dense operational screens and calm attendee surfaces, in a day and a night theme.
- Design system
- Reusable interface states, so new event workflows can be added over time.
- Brand system
- One identity, built for a poster and for a dense organiser screen.
Living Pages
