The dedicated ticket and gate-operations deployment that ran entry control for a live client. Its batch, QR, scan, and device model is still sold and run as a scoped dedicated deployment. There is no ticketing in the current NoxOrigin application, so it is not a NoxOrigin area and not part of any NoxOrigin plan.
This is a dedicated deployment, scoped separately from the standard plans. It is not an area of NoxOrigin, it is not included in any NoxOrigin plan, and you do not get it by subscribing to NoxOrigin.
Nox-Tickets was built because a real operation needed it, and it is still built because that operation is still real. Some work genuinely needs its own environment and its own release cadence, and forcing it into a shared workspace would be a downgrade. That is the whole reason it is offered as scoped custom scope rather than as a NoxOrigin area.
It keeps the shape that made it work. Everything below is delivered as a scoped engagement with its own environment, its own agreement, and its own support window.
Runs in its own dedicated environment, not inside a NoxOrigin workspace
Batches, QR codes, scan points, and device status, kept as one operational record
Live entry reporting for the people running the door on the day
Scoped deployment with its own agreement — never bundled into a NoxOrigin plan
No, and this page is explicit about it. Nox-Tickets is still built, still sold, and still run for clients — but as a scoped dedicated deployment with its own environment, not as an area inside the current NoxOrigin application. No NoxOrigin plan includes it.
The dedicated ticket and gate-operations deployment that ran entry control for a live client. Its batch, QR, scan, and device model is still sold and run as a scoped dedicated deployment. There is no ticketing in the current NoxOrigin application, so it is not a NoxOrigin area and not part of any NoxOrigin plan.
Yes, and it is scoped separately from the standard plans rather than sold as a different product. Integrations, data migration, white-label or customer-branded deployments, and dedicated environments are all handled as custom scope — see the custom-scope note on the pricing page.
Yes, and that is the common case. The dedicated deployment keeps running in its own environment, and it can be integrated with NoxOrigin so the records that matter flow between them. The two are quoted together as custom scope, because the integration is the part that has to be designed, not picked off a shelf.
Because the name is still in search indexes, in old emails, and in the vocabulary of people who dealt with us. Deleting the page would waste that. Rewriting it honestly is more useful than pretending the name never existed.