EventOS turns a venue layout into live seat inventory, runs invite-only, free and paid registration, sends passes over WhatsApp in the guest’s own language, and clears every guest at the gate — online, or with no internet at all.
They experience seconds, taps and clarity. These nine numbers are the marketing, the demo script and the acceptance criteria at once — a phase does not ship while its number fails on a mid-range Android over 4G.
Reserved seating, QR check-in, badge printing — table stakes. We build them well and never lead with them. The four below are structural, and a funded competitor cannot ship them in a sprint.
Most Indian corporate, political, wedding and institutional events sell zero tickets. The agency bills the client. So we built client invoicing, vendor bills, cost sheets and margin — not a checkout.
The only event platform built for events that don’t sell tickets.Organization, then clients, then events, then subcontractors on scoped access that expires with the work order. Ticketing products have “organizers.” We have the hierarchy agencies really run on.
Every release ships to production on our own events before a customer sees it. Shadow mode first, then live, then live with full gate authority. Three internal events before the first design partner.
Tamil at launch beside English — booking pages, passes, WhatsApp templates, gate UI, the client report. For a political, temple, college or district event, the vernacular guest experience is the product.
Vendors attach to one event and one work scope, never to the organization, and access dies with the assignment. The printing vendor sees name, category, seat and pass status; mobile and email stay masked. Enforced server-side and again at the database with row-level security — frontend filtering is never isolation.
Platform
└── Organization — Madras Event Co.
├── Clients
│ ├── Client A ───────────────── Annual Awards 2026
│ │ Founder’s Day
│ └── Client B ───────────────── Dealer Meet, Coimbatore
├── Venues reusable templates, versioned
├── Staff
└── Vendors attached per event, never to the org
work orders on this event —
Registration → Vendor A guest list, registration no payments · no other events
Printing → Vendor B print queue, pass status mobile + email masked
Gate → Vendor C scan, attendance nothing else
Each device holds an encrypted pack — ticket token hashes, gate rules, a device key — so a scan resolves locally in under 200 ms with the venue Wi-Fi down. Every event carries its own theme from admin, so the pass and the scanner wear that client’s brand and no two events look alike — but nothing inside the scan result frame is themeable, which is what keeps operator training at zero. Switch events, cut the network, scan.
Pack v14 loaded — 1,840 tickets — last sync 18:02
Verdict layer locked. The brand reaches the event bar, the button and the pass — never the screen. Green, red and the VIP gold are the platform’s at every event, so an operator who worked a rose-red wedding last night already knows this gate. A brand sitting too close to either verdict hue is flagged in the theme editor before the event goes live.
Not to the tenant. One event serves a Tamil guest, a Hindi guest and an English-reading client at the same time, and the concierge answers in whatever language the guest writes in. A missing string falls back to English, never blocks the flow, and lands in the translation queue.
Wave 1 Phase 0.5 — Tamil, English Wave 2 Phase 4 — Hindi, Telugu, Kannada, Malayalam Wave 3 Phase 6 — Arabic (full RTL), then by demand Logical CSS properties from day one. Retrofitting RTL is the expensive path.
AI acts on its own for read-only questions and nothing else. Anything touching inventory, money, access or a message to a guest goes through this chain, with the proposal, the approver and the diff in the audit log. “The AI moved 40 VIP seats on its own” is how an agency loses a client — and how we lose the agency.
Phase 0 is unglamorous and everything rests on it. Phase 0.5 is the first shippable product: the complete operating loop for invite-only events — no payments, no GST invoicing, no refunds, no seat-selection race.
Tenant isolation with row-level security, idempotency keys, the outbox pattern, state-machine framework, seat inventory ledger, capacity invariants, webhook verification, audit log, device registry.
Guest list to WhatsApp invite to OTP to pass to gate to live dashboard to the auto client report. VIP Protocol alerts, offline packs, read-only copilot, and language Wave 1 — Tamil and English — all inside it.
Full venue and layout model, the seat engine with its template/instance split, booking engine with locking and holds.
Public registration, hardened OTP, ticket types and pricing, Razorpay with idempotent webhooks, and refunds end to end — request, approval, gateway, seat release, pass revoke, ledger.
Layout import from PDF, photo, CAD or sketch with mandatory human approval. Full pass designer and per-event theming across pass, scanner chrome and guest pages. The complete WhatsApp lifecycle, ops bot, guest concierge, constraint-based seat allocation.
Hardened offline engine, sync reconciliation, duplicate-scan fraud handling, live command centre, Event Readiness Score, gate anomaly watch, and language Wave 2.
Client approvals, subcontractor work orders, the printing agent, sponsor self-serve uploads, event cloning, instant-event onboarding.
Double-entry ledger, client invoicing, vendor bills, settlement runs, attendee identity graph, predictive arrival curves, and language Wave 3 with full RTL.
A monthly subscription arrives in your dead months and sits in your overhead. An event fee lands on the event cost sheet, next to venue, printing and security — so it passes through to your client with everything else. Nothing per ticket, ever.
First one freeRun your first event under 300 guests on us — whole loop, real gate, real report. No card. If it doesn’t survive an actual event night, you shouldn’t be paying for it.
Not the hall’s seat count, and not scans. Declare the band when you create the event; cross it and you’re billed the difference at settlement. We never block a gate on event night over money.
Commit to ten events inside twelve months and every one drops to the pack rate — any size, any client, sizes mixed freely. Unused events expire, and we tell you well before they do.
WhatsApp conversations, SMS, AI layout imports, print jobs, extra gate devices. A 200-guest VIP wedding in two languages still costs more per head than a 3,000-guest public event. Itemised on the cost sheet, so it passes through too.
Unlimited events at one venue. Your hall runs continuously, so continuous billing is the honest shape. Everyone else pays per event.
These bands stretch past the PRD’s ₹999–9,999 range at the top end, deliberately: at 10,000 guests this is under ₹2 a head on an event the agency bills in lakhs. And the standing caveat holds — every number here is a hypothesis until five design partners react to it.
A completed event where registration, passes, the gate and attendance all ran on EventOS. Stronger than tickets sold — and it counts the invite-only events that tickets-sold never would.