Product and backend / Current
Event teams often combine forms, payment links, spreadsheets, ticket files and separate event-day tools. That fragmentation makes it harder to keep inventory, transactions, attendee state, internal documents and operational decisions consistent as an event moves from setup to live execution.
eventOS is live at eventos.ng. It has hosted paid events, earning revenue for the platform and for the organisers, and its door scanning has run offline at real venues. Two other live sites, Kilogbede Records and Same House Records, sell their tickets through its headless API. I am its principal architect and wrote most of the code.
Walkthrough
Captured from the live public site: discovery, search, an event record, the event calendar and the organiser offer. Internal and financial operations screens are not shown.
My part
Decisions
A payment counts only when the payment provider's verified notification says so. The page a buyer lands on after paying is feedback, not proof. If the same notification arrives twice, the second one changes nothing.
Checkout reserves the ticket or seat first and releases it if payment does not complete in time. Two people cannot buy the last ticket, and an abandoned checkout does not lock it forever.
Each ticket keeps the design and terms that applied when it was issued. Editing the event later does not silently change tickets people already hold.
Door staff scan from a protected copy of the guest list on the device. Scans are recorded locally, synced when the connection returns, and duplicate admissions are flagged.
A partner site may be allowed to request something its plan does not include. Both are checked, so technical access and commercial terms cannot be confused.
Doing routine work, starting a sensitive action and approving it are separate responsibilities, so the platform can be run day to day without giving everyone unrestricted access.
Screens
Phone screens
SYSTEM ARCHITECTURE
Web, embed and partner checkout
Web, mobile, SDK, embed and MCP
Identity, inventory, transactions and permissions
Verified callbacks and reconciliation
Immutable ticket snapshot, QR and PDF
Encrypted offline manifests and sync
Built with
Links
More work
XcroTrustEngineered a four-surface escrow product across public web, consumer mobile, backend services, and operational administration, implementing a supplied design while keeping transaction outcomes and intervention paths server-controlled.Pre-launchNutrifluxA Nigerian-first nutrition mobile app and API combining deterministic health state, structured AI planning, offline-resilient writes, social features, reminders, observability and review-gated safety controls.Pre-launchKilogbede RecordsDesigned and built Kilogbede Records' production platform across the public label site, roster and release storytelling, media infrastructure, events, commerce connections, and a purpose-built operational CMS.Live in production