Hardware
Readers for your postures
Countertop, handheld, or POS-integrated readers for the pilot locations, provisioned to your organization and activated on-site with time-boxed codes.
Pilot program
Prove the boundary at your own counter.
A Laurel pilot is a scoped, time-boxed deployment at real checkpoints: readers in staff hands, aggregate reporting in the portal, your security team inside the architecture, and success metrics both sides agree to before anything ships.
01 · The pilot package
Everything a real evaluation needs. Nothing performative.
Software
Full portal access
Fleet health, trust-material status, and aggregate verification reporting, with role-scoped access for owners, operators, installers, and viewers.
People
Deployment & support
Site profiling, installer runbooks, staff quick-reference training on the three-outcome vocabulary, and a direct operational contact for the pilot’s duration.
Security
Security review
The documentation package and a working session with engineering — the trust center pathway is a standard pilot leg, not an add-on.
Evidence
Agreed success metrics
Defined during qualification and reviewed at the end: check completion, fallback rates, throughput at the checkpoint, and staff confidence.
Exit
A decision, either way
The pilot ends in a written readout against the metrics. Rolling out is a decision you make on evidence — not a subscription you forgot to cancel.
02 · How a pilot runs
Qualification to readout, step by step.
-
Qualification
One conversation, driven by the form below: your settings, jurisdictions, hardware environment, and what you need the pilot to prove. You get a scoped plan and a quote.
Credential check We confirm mobile-ID coverage for your jurisdictions against the current issuer landscape before anyone commits.
-
Security & site readiness
Your security team gets the review package and session; your locations get site profiles covering posture, mounting, and network.
-
Deployment
Readers arrive registered to your organization. Installers activate them with expiring codes; staff train on the three outcomes — usually minutes, not days.
-
Live operation
Real checks at real checkpoints. The portal shows fleet health and aggregate outcomes; day-level buckets stay suppressed below k=3, as they will in production.
-
Readout
A written review against the agreed metrics and a commercial proposal sized by what actually happened — or a clean stop.
03 · 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
readers & portal Laurel — hardware, software, provisioning, support
site access You — counter space, power, outbound HTTPS connectivity
staffing You — staff at the checkpoint; Laurel — their outcome training
fallback procedure You — your existing manual age check remains yours throughout
metrics & readout Shared — defined together at qualification, reviewed together at exit
04 · Hardware & credentials
The pilot matrix.
| Posture | Best for | Mobile-ID path | Physical-ID path |
|---|---|---|---|
| Countertop | Registers, podiums, service counters | On-device check | Your manual fallback |
| Handheld | Lines, floors, festival gates | On-device check | Your manual fallback |
| POS-integrated | Age-gated sales inside checkout | On-device check | Your manual fallback |
Credential coverage (ISO/IEC 18013-5 mobile IDs by jurisdiction) is confirmed during qualification — see supported mobile IDs.
05 · Before you ask
Pilot questions, answered straight.
How long does a pilot run?
Long enough to see your real traffic patterns — typically a small number of locations over several weeks, scoped precisely at qualification. Short enough that the readout arrives while the decision still matters.
What does it cost?
Pilots are quoted per engagement — locations, postures, and duration set the number, and qualification produces the quote before you commit. See how pricing works.
What if patrons don’t 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 part of the value of piloting now.
Will our security team have enough to review?
Yes — the architecture overview, the field-by-field data classification, and the privacy-boundary specification, plus a session with engineering. The trust center outlines the pathway.
What data will we see during the pilot?
Exactly what production shows: fleet health and aggregate outcome counts. No patron identity, no per-check records, and day-level buckets suppressed below k=3. The pilot does not run in a looser data mode.
06 · Qualification
Tell us about the checkpoint.
Enough context to scope honestly — settings, sites, and what you need proven. Do not include patron identity or other sensitive personal data.