The door
Queues build while a desk retypes names from a printed list, and badges are handwritten because the system that made them cannot reach the venue.
Registration to entry, on one attendee record.
Configure the event, take registrations, deliver signed QR tickets on WhatsApp and email, scan at the door, print the badge. Nothing re-typed between stages.
- Signed QR tickets
- Offline check-in
- WhatsApp delivery
- Badge printing
- Exhibitor leads
The console
Six screens, one attendee record.
Every screen below is the real console — the same one your team signs into on the day.
Great events, invisible results.
The floor
A booth conversation ends with a business card in a pocket. By Monday half of them are gone, and none of them are searchable.
The report
A sponsor asks what their stand actually got them. What you have is anecdotes, not a number tied to a scan.
How it works
Configure
Set up the event, its branding and its registration form.
Register
A visitor submits the form and verifies their email or phone.
QR ticket
A signed ticket goes out on WhatsApp and email — nothing re-typed.
Scan
The door reads the code, online or with the venue Wi-Fi down.
Badge
The desk sends the badge to the print queue; it turns around in seconds.
Entry recorded
The scan, its outcome and its reason are logged against that attendee.
One attendee record underneath all of it.
Built for three people at the same event.
Organisers
Set up the event, run the doors, and leave with a report instead of anecdotes.
For organisers →Exhibitors
A booth-scoped login, no scanner rental, and every lead your own to keep.
For exhibitors →Sponsors
What is provable today about your stand and its traffic, and what is coming.
For sponsors →What's built, what's next
Every capability, honestly labelled.
Nothing below is claimed without a mechanism behind it. Anything not yet shipped carries a Roadmap tag — here, and everywhere else on this site.
Event setup and branding
Configure venue, dates and organiser branding once; every page and ticket inherits it.
Registration form builder
Build a registration form once per organisation and reuse it across every event.
Public event pages
A public landing page per event, from a preset or your own HTML in a sandboxed frame.
Email and phone verification
OTP on email and phone before a registration submits, so the record is real.
Signed QR tickets
HMAC-SHA256, per-event keys; a leaked key forges nothing for another event.
Pre-printed badge batches
Import a CSV of visitors and print their badges before the doors open.
Offline entry scanning
Scans queue in IndexedDB when the venue Wi-Fi drops and sync once, by idempotency key.
Check-in desk
A staffed desk screen for manual lookups when a ticket will not scan.
Badge designer and print queue
Design the badge layout once; the desk sends jobs to a dedicated print role.
Exhibitor directory
Add and manage your exhibitor list per event — contacts, booth details and products, in one record.
Booth lead capture
Booth-scoped logins scan into one exhibitor’s lead list only, never another’s.
Scan and audit logs
Every scan and privileged action logged with outcome and reason, forgeries included.
WhatsApp ticket delivery
Signed QR tickets sent on WhatsApp and email the moment a registration is approved.
Operator console
Role-based screens, scoped to one event per assignment, guarded per route.
AI concierge
An assistant for attendee questions, being built on the record that exists today.
AI matchmaking
Suggested exhibitor-visitor matches, being built on the record that exists today.
AI follow-up
Automated post-show follow-up messages, being built on the record that exists today.
Audience engagement
Live polls and Q&A during sessions, being built on the record that exists today.
Booth analytics
Per-booth traffic and conversion numbers, being built on the record that exists today.
Visitor analytics
Attendee-level engagement reporting, being built on the record that exists today.
Executive dashboards
Sponsor and organiser dashboards, being built on the record that exists today.
Sessions and speakers
Session and speaker scheduling — there is no session or speaker model yet.
SSO and SAML
Enterprise single sign-on, being built on the record that exists today.
SCIM provisioning
Automated user provisioning from an identity provider, not yet built.
SOC 2 and ISO 27001
Formal security certification — not yet undertaken, and not yet claimed.
Outbound webhooks and CRM connectors
Pushing events to your CRM automatically, being built on the record that exists today.
Wallet passes
Apple and Google Wallet tickets, being built on the record that exists today.
Attendee app
A dedicated attendee mobile app, being built on the record that exists today.
Built to survive procurement, not just a demo.
Isolation in the database
Row-level security with FORCE, under a runtime role that does not own the tables — enforced by Postgres, not just the application.
Signed QR tickets
HMAC-SHA256, per-event derived keys. A leaked key forges nothing for another event.
Scoped roles
Per-route permission guards, and every staff assignment scoped to one event.
Audit trail
Every privileged action logged, on a screen gated by its own permission.
What you can verify in a demo.
We do not have a metrics wall to point at yet. We would rather show you the mechanism than ask you to trust a number.
Cross-tenant isolation, demonstrated live
We query another organisation’s data with your credentials and show you the database refuse it — not the application layer, the database.
A forged QR rejected at the door
We hand-edit a ticket and scan it. The scanner rejects it and logs the attempt, reason included.
A scan taken with Wi-Fi off
We switch the venue Wi-Fi off mid-scan, then back on, and watch the queued scan sync itself once.
Questions organisers actually ask.
What happens if the venue Wi-Fi drops during check-in?
The scanner keeps working. Each scan queues in the browser’s own storage (IndexedDB) and syncs once the connection returns, matched by an idempotency key so a scan already recorded is never counted twice.
How do tickets reach an attendee?
On WhatsApp and email, automatically, the moment a registration is approved — the same signed QR code either way, so there is no second version to keep in step.
Can we print badges before the doors open?
Yes. Import a CSV of visitors and their badges print in advance; each one binds to whoever scans it first at the door.
What stops someone forging a ticket?
Every QR code is signed with HMAC-SHA256 using a key derived per event. A key leaked from one event forges nothing for another, and a forged or altered code is rejected at the scanner and logged with the reason.
Can we self-host it?
Yes — it ships as containers with a documented runbook, and the event and WhatsApp APIs each publish their own OpenAPI definition, rather than as a hosted-only product.
What on this site is not built yet?
Anything carrying a Roadmap tag — AI features, analytics dashboards, session and speaker management among them. We would rather label a gap than paper over it with a mockup.
What does it cost?
Packs are priced in rupees, ex-GST, per event — see the pricing page for the current figures and what each pack includes.
Run your next event on it.
See it configured for a show your size, on a call or over WhatsApp.