Access control hardware

Doors that honor the booking — with or without a network.

An offline-first door-access appliance: touchscreen kiosk, RFID cards and reservation codes, relay-driven locks. Every open/deny decision is made locally at the door, so outages never lock out a paying client.

Reference deployment: Business Avenue — six branches across four provinces.

PearlAccess kit — touchscreen tablet appliance, controller unit and magnetic lock
Pi 5Raspberry Pi 5 at the core
7"touchscreen kiosk
0network needed to open a booked door
39automated tests on the device service

Engineered for the failure mode, not the demo

Most access control works until the internet doesn't. PearlAccess was designed in Iraq, for Iraq — the outage is the starting assumption.

Decisions live at the door

A Python device service keeps a synced local cache of reservations, cards and schedules — and makes every open/deny decision on the spot, in milliseconds. The backend synchronizes; it is never in the permission path.

  • Offline-first: local decisions against a SQLite cache
  • Sync, events and heartbeat loops when the network allows
  • Events queue locally and reconcile after outages
Inside the PearlAccess appliance — touchscreen, controller board and RFID coil

Two ways in, both accountable

Members tap an RFID card; guests type the reservation code from their booking on the kiosk. Either way the door logs who, when and on which booking — no shared master codes, no mystery entries.

  • USB RFID reader for member cards
  • On-screen reservation codes for guests
  • Full entry log, reconciled to the booking system

Built as a fleet, not a one-off

Pairing, provisioning and updates are designed for many doors: Ansible and systemd turn a fresh device into a hardened kiosk identically every time, and updates arrive over the air. Door twelve installs exactly like door one.

  • One-time pairing to your management dashboard
  • Over-the-air updates across the fleet
  • Hardened kiosk OS — locked down, self-restarting
Exploded view of the PearlAccess electronics and casing layers

The case and the power are ours too

The enclosure is designed for the hardware — not adapted to it — and a companion UPS keeps the door deciding through power cuts. White-labeled, so it carries your brand at your doors.

  • Custom-designed enclosure and mounting
  • Companion UPS unit for power continuity
  • White-label branding for your organization

Who PearlAccess is for

Anywhere a door should obey a schedule or a booking instead of a key.

Serviced offices & coworking

Meeting rooms billed by reservation — the door enforces the calendar, entry disputes end. This is the reference deployment.

Buildings with booking systems

Clinics, studios, training rooms, sports facilities — if it's reservable, PearlAccess can hold the door to it.

Operators who need offline

Sites where connectivity or power can't be assumed — the appliance is engineered for exactly that reality.

Scoped per deployment

PearlAccess ships as a deployment, not a box: devices, installation, integration with your booking backend, and an operate plan for monitoring, support and updates. Every site is scoped in writing — device count, doors, integration effort — before any commitment.

  • Written scope and fixed deployment price
  • Integration with your reservation or management system
  • Operate plan: monitoring, OTA updates, support

White-label and multi-branch fleets supported — the reference fleet spans six branches.

Questions, answered

Does it work with our existing booking system?

That's the integration step of the deployment: the device speaks to a backend API for sync and events, and we build the bridge to your reservation system — the same way it was paired to Business Avenue's management platform.

What exactly happens when the internet goes down?

Nothing, at the door. Decisions come from the local cache, entries keep logging locally, and everything reconciles when the connection returns. A power cut is covered by the companion UPS.

Can we see it working before committing?

Yes — ask for a demonstration. The device runs the full kiosk experience against a demo backend, and the Business Avenue case study shows the production fleet.

Who maintains the devices after installation?

We do, under the operate plan: monitoring, over-the-air updates, support through your client portal — the same operational model as everything else PearlFibers runs.

Put a PearlAccess on the door.

Tell us about the site — doors, bookings, network reality — and you'll get a written deployment scope with a price on it.

All products