SnapKey for iLOQ

A control and orchestration layer on top of the iLOQ S50 system you already own. Mobile keys, sensors and NIS2/CER documentation — without replacing a single cylinder.

Book a demo

Official iLOQ integration partner

Built for iLOQ S50

NIS2 & CER documentation

Off-grid — no mains power

Keep every cylinder

SnapKey runs on top of the iLOQ system you already own. No locks replaced, no re-keying, and no second lock estate to maintain alongside the first.

Keys that travel by phone

Share a key from the app, by SMS or by e-mail. It returns itself when the period ends, and can be revoked the moment plans change.

Answers for the auditor

Every opening ties to a person, a key and a time. Signed reports and incident records cover what NIS2 and CER ask you to evidence.

Eyes on doors that have none

Wireless, battery-powered sensors report doors left open, forced entries and low batteries — from sites with neither mains power nor a network.

From iLOQ system to mobile keys

1
Connect

Link your existing iLOQ system to SnapKey. We are listed as an integration partner by iLOQ, so the connection is supported rather than improvised.

2
Sync

Locks, people, keys and security groups synchronise both ways. Your iLOQ structure stays the source of truth.

3
Issue

Hand out mobile keys with time limits, geofences and approval requirements — to staff, contractors and visitors.

4
Document

Openings, incidents and approvals accumulate as they happen, ready to export the day supervision asks.

Where it earns its place

Unmanned sites

Pumping stations, substations and plant rooms with no power and nobody on site. Off-grid access that still produces a log.

Contractors at short notice

A key that exists for one Saturday afternoon and returns itself — instead of a master key that never comes back.

Preparedness changes

When the preparedness level changes, access can roll out automatically rather than through a phone tree.

What the administrator gains

The things an iLOQ system cannot do on its own, added without disturbing how it is already set up.

Mobile key sharing with automatic return

Instant key deletion and revocation

Key distribution by SMS and e-mail

Safety instructions confirmed before access is granted

Two-factor approval for critical doors

What the field gains

Fewer trips, fewer keys, and a record that writes itself while the work happens.

One key on the phone instead of a bunch on the belt

Access that works without mains power or a network

Check-in with a stated purpose, so presence is known

Door sensors that catch what a lock cannot see

No trip to the office to collect or hand back a key

Questions about the iLOQ integration

No. SnapKey runs on top of the iLOQ system you already own. The cylinders, the locking plan and the investment behind them stay exactly as they are.

The integration is built for the iLOQ S50 platform in the iLOQ 5 Series.

Yes. SnapKey is listed as an integration partner on iLOQ's own website, so the integration is supported rather than reverse-engineered.

Existing iLOQ keys keep working. People, keys and security groups synchronise both ways, so you can move to mobile keys at your own pace instead of in a single cutover.

It is the most common reason for connecting the two. NIS2 requires access control policies and incident handling; CER requires preventive measures and evidence of who reached critical functions. Both need documentation a mechanical key cannot produce.

See it on your own iLOQ system

We will walk through what connects, what stays exactly as it is, and what you would be able to document afterwards.

Book a demo