Enterprise
For codes you cannot recall.
At scale the risk stops being design and starts being governance: who is allowed to change where a printed code points, whether that change is recorded, and what happens to a hundred thousand pieces of print when somebody gets it wrong.
SAML single sign-on
Authenticate against your existing identity provider, with enforced two-factor and session policy set centrally rather than per user.
Roles with real boundaries
Seven roles across thirty-two permissions. A designer can restyle a code but cannot repoint a live one; an analyst can export but cannot modify. Enforced on the server for every request — never by hiding a button.
Audit log
Who changed what, when, and what it was before. Every destination change on a printed code is recorded, which is usually the question being asked when something goes wrong.
Your own short domain
Serve codes from a domain you own, with certificates issued and renewed automatically, so the link people see belongs to you rather than to us.
Data handling you can sign off
No visitor IP addresses stored, no cookie set on a scan, geolocation resolved on our own servers so no third party sees your traffic. A data processing agreement is available.
Multi-brand and multi-location
Separate workspaces per brand or region, client records with scoped access, brand kits, and per-workspace reporting that cannot leak across boundaries.
Commercial terms
Enterprise agreements are priced by arrangement rather than published, and can include a contractual service level with credits, invoiced annual billing, a signed data processing agreement, and security review before purchase. The published plans cover everything below that.
Be aware of where the product currently is: the hosted application is built but not yet running on public infrastructure, so this is a conversation about a deployment rather than a sign-up today. We would rather tell you that now than during procurement.