Full portal access
Fleet Health, device lifecycle controls, version enforcement, and aggregate reporting, with role-scoped access for owners, operators, installers, and viewers.
Pilot program
Thirty days. One location. A decision either way.
A pilot is scoped so it can fail cleanly and cheaply. That is what makes the result worth anything.
01 · The shape
The default pilot, in numbers.
These are defaults, not limits. A different footprint is a scoping conversation — but starting here keeps the first one honest.
30 days
Long enough for a full traffic cycle, short enough to stay urgent
1 location
One real site with real staff, not a lab or a back office
2–5 verifiers
Enough to cover your checkpoints and to test a fleet, not one device
Weekly
A standing review, so problems surface in week one rather than week four
02 · What is included
Everything a real evaluation needs.
Deployment support
Site profiling, installer runbooks, device creation and activation, and configuration — done with your team rather than handed to them.
Operator training
Three outcomes, three actions, and the fallback. Staff training takes minutes on purpose; anything longer would not survive a real shift.
Security and privacy review
The full documentation package plus a working session with engineering. Your reviewer gets the limitations as well as the controls.
Defined success metrics
Agreed during qualification and reviewed at the end: check completion, fallback rate, mobile-ID share of traffic, throughput at the checkpoint, and staff confidence.
A rollback plan
Written before the pilot starts: how devices are revoked, how the floor returns to your existing procedure, and what happens to your records.
03 · How it runs
Qualification to readout.
-
Qualification
One conversation, driven by the form below: your setting, your jurisdictions, your hardware environment, and what the pilot has to prove. You get a scoped plan and a quote.
Credential reality check We confirm mobile-ID coverage for your jurisdictions against the current compatibility matrix before anyone commits. If your locations are outside a supported jurisdiction, we say so here rather than later.
-
Security and site readiness
Your security team gets the review package and a session with engineering. Your location gets a site profile covering checkpoint posture, charging, and network.
-
Deployment
Devices are created in the portal, activated with single-use codes, configured, and confirmed present in Fleet Health. Then a real credential is verified at the real counter.
-
Live operation
Real checks at real checkpoints for thirty days, with a weekly review. A deliberate connectivity-interruption exercise is part of it, because that is the test that matters.
-
Readout
A written review against the agreed metrics, and a proposal sized by what actually happened — or a clean stop with the rollback plan you already have.
04 · Who does what
Small asks, clearly divided.
A pilot succeeds when both sides know their side of the counter. This is the whole division of labor.
Responsibility Owner
verifiers and portal Laurel — provisioning, configuration, and support
site access You — counter space, power, outbound HTTPS
staffing You — staff at the checkpoint; Laurel — their training
fallback procedure You — your existing manual check stays yours throughout
metrics and readout Shared — defined together, reviewed together
rollback Shared — written before the pilot starts
05 · Before you ask
Pilot questions, answered straight.
How long does a pilot run?
Thirty days by default, at one location with two to five verifiers. Long enough to see a full cycle of your real traffic, short enough that the readout lands while the decision still matters.
What does it cost?
Pilots are quoted per engagement. Locations, device count, and duration set the number, and qualification produces the quote before you commit to anything.
What if our patrons do not carry mobile IDs yet?
Then the pilot measures exactly that: the mobile-ID share of your real traffic, with your manual fallback untouched for everyone else. Adoption data from your own counters is usually the single most valuable thing a pilot produces.
Will our security team have enough to review?
Yes. The privacy architecture, the security architecture, the data inventory with retention, the subprocessor list, and a printable security overview, plus a working session with engineering. The security review is a standard pilot leg, not an add-on.
What data will we see during the pilot?
Exactly what production shows: fleet health and aggregate outcome counts, with rows suppressed below a minimum group size of three. There is no looser data mode for pilots.
What happens if we decide not to continue?
The rollback plan agreed at the start runs: verifiers are revoked and their credentials retired, and your organization and staff records are removed on request. There is no patron data to unwind, which makes exiting genuinely simple.
06 · Qualification
Tell us about the checkpoint.
Enough context to scope honestly — where the check happens, in which jurisdictions, and what you need proven. Please do not include patron identity or other sensitive personal data; the form rejects it.