Laurel Secure
Sign in Start a pilot

Deployment

Fits the counter you already run.

Laurel pilot deployment is scoped around the checkpoint and operational environment you already run. The available device posture, hardware, and integration path are confirmed during qualification; Laurel is not an MDM or a replacement POS.

Plan a pilot deployment How Laurel fits your stack

01 · Hardware postures

Start with the place where the check happens.

Kiosk

Fixed checkpoint

A register, door podium, or service counter may be a fit. Exact device and hardware availability are confirmed for the pilot before deployment.

Handheld

Mobile checkpoint

A moving line, floor, or door may require a mobile posture. This is a qualification question, not a claim of supported hardware.

POS integration

Existing-system adjacency

Any POS or integration path must be reviewed and approved for the specific pilot; no POS compatibility is promised here.

02 · Rollout

From kickoff to a live counter, deliberately.

  1. Site profile

    We map each location: where checks happen, who staffs them, which posture fits, and what the network and mounting environment look like.

  2. Reader provisioning

    Devices are registered to your organization in the portal, then activated on-site with a time-boxed activation code by your staff or an installer role scoped to exactly that job.

    Activation model Activation codes expire on a schedule you set; the portal tracks every reader from pending to active.

  3. Verification goes live

    The decision is made on the reader, locally. The platform connection carries outcomes and device health — it is not in the loop for the verification itself.

  4. Operate from the portal

    Fleet health, trust-material status, and aggregate outcome reporting live in one operations portal, scoped by role — owner, admin, operator, installer, viewer, support.

03 · Network & environment

Light demands, made explicit.

The reader’s platform traffic is a narrow, outbound-only vocabulary: outcome counts, health signals, and configuration state. The verification decision itself never depends on a round-trip to the cloud.

Requirement What it means on site
connectivity Outbound HTTPS from the reader — no inbound ports, no VPN
decision path On-device; not dependent on platform availability
power & mounting Standard counter or podium placement per posture; confirmed in the site profile
device management Laurel does not replace an existing MDM. Specific device-management compatibility must be confirmed during qualification.

04 · Operating questions

What operators ask before a rollout.

What happens if the network drops mid-shift?

Verification keeps working, because the decision is made on the reader. The platform connection is for reporting and fleet health, and reconnection is handled without staff intervention.

Who racks and activates the hardware?

Either your team or your installer of record. The portal has a dedicated installer role: enough access to activate a specific reader with a time-boxed code, and nothing else.

Does Laurel manage or replace our POS?

No. Laurel answers the age question next to — or inside — the flow you already run. It is not a POS, not an MDM, and not a system of record for anything except verification outcomes in aggregate.

Next step

Profile your first site.

Pilot qualification starts with the counter, the posture, and the jurisdiction.

Start a pilot Ask a deployment question