Event access control software for controlled operators.
Nox-Tickets is event access control software: QR validation, scanner device management, staff roles, and post-event operational reporting for events, venues, and amusement parks.
It is shaped for operators who need QR-driven entry with device approval, ride-group permissions, and clear audit trails rather than a public self-serve ticket marketplace.
Available now and currently running for 1 PaaS client; early enough for direct implementation support and proven enough to run real event operations.
Public list pricing is available on the pricing page; this page describes the access-control workflow in more depth.
Audience
What the product is shaped for
Verified product screenshots
Screenshots from the current Nox-Tickets admin surfaces. These are the same surfaces you would see on the day of the event.
Admin sign-in screen in the current browser surface.
Mobile admin sign-in for scanner operators.Hardware is separate. White-label implementation starts from ₹75,000; unusually large usage is quoted based on the agreed operating scope.
- Rollout scoping and device review (first week)
- Project, ride groups, and staff setup (week 2)
- Live event with on-call support (event day)
- Post-event operational review (week 4)
Event scope, devices, and deployment support are confirmed in writing before any rollout invoice.
Process
- Rollout scoping. We review the event scope, expected attendance, gate count, and the device inventory you plan to use.
- Project setup. We configure the project, ride or entry groups, ticket batches, and staff assignments before the event.
- Live event. We support the event day with a runbook, on-call coverage, and the operational dashboard for live visibility.
- Post-event review. We review attendance, rejection reasons, device reports, and offline sync so the next event is tighter.
What is and is not in scope
- In scope: QR validation, scanner device approval, staff roles with ride-group permissions, live operational dashboard, post-event reporting.
- Out of scope: public self-serve ticket marketplace, hardware procurement beyond supported scanner devices, or a universal offline-resilience guarantee before rollout validation.
- Public list pricing applies within the published limits; custom usage, hardware, and implementation are confirmed before onboarding.
Frequently asked questions
Is Nox-Tickets available for public events?
Yes. Nox-Tickets is available now and currently runs for one PaaS client. It is operator infrastructure, not a public ticket marketplace.
Can it detect duplicate scans?
Yes. Duplicate-scan detection is part of the product workflow, with clear outcomes for valid, duplicate, expired, invalid, and wrong-group scans.
Can devices be approved or rejected for scanning?
Yes. Scanner device visibility and approval are part of the planned operational workflow and are confirmed during rollout scoping.
Does Nox-Tickets issue tickets or only scan them?
The current workflow includes ticket batches, ticket issuance foundations, QR validation, scanner teams, devices, and event reporting. We confirm the exact issuance flow before deployment.
How does offline scanning handle duplicate tickets?
Offline behaviour is rollout-scoped and depends on the device and sync workflow. Disconnected scanners can create reconciliation risks, so conflict handling and duplicate prevention must be tested for each event before deployment.
What devices can run the scanner?
Nox-Tickets is being tested on supported Android scanner devices. Device registration, approval, Android version, and camera performance are checked during rollout onboarding rather than promised as a universal hardware guarantee.
How is post-event reporting handled?
Scan summaries, rejection analysis, staff activity, device reports, and CSV exports are part of the post-event operational review.
Book a consultation
Tell us the workflow you run today. We will confirm whether this is a sensible fit and what to do next.