Gates & entry
One place for every gate.
Nokē, BearBox, PTI Cloud, OpenTech and Paxton — one place to see and control the gates at every one of your sites. Overdue units will lock themselves, and unlock the minute a customer pays — no more driving over with a padlock. We work with the gate hardware you already own; the connections are what comes next.
◐ Vendor connections — coming soon
01 / Your hardware, our software
We work with the locks you already own
Each site can run a different gate brand and you'll still see them all in one place, working one way. We never sell you hardware. Nokē is next on our build order; the other connections follow.
Illustration of planned functionality: five sites each running a different access-control vendor — Camden Lock on Nokē, Bristol Docks on BearBox, Leeds North on PTI Cloud, Glasgow East on OpenTech and Cardiff Bay on Paxton via a site bridge — presented as one console, with Nokē named as the next vendor connection to be built.
Nokē◐ Coming soon
Smart-entry credentials + access events.
BearBox◐ Coming soon
Smart-entry / site controllers.
PTI Cloud◐ Coming soon
PTI StorLogix Cloud access control.
OpenTech◐ Coming soon
OpenTech INSOMNIAC access control.
Paxton◐ Coming soon
Paxton Net2, via a per-site bridge.
02 / Gate codes that will look after themselves
Access will follow the agreement, automatically
Once a vendor is connected, a move-in will get their gate code without anyone visiting the site, a move-out will lose it, and nobody will ever have to remember to change a PIN.
Issue
A credential is created at move-in, the moment the agreement is signed and the first payment clears — no gate-code errand, no spreadsheet of PINs.
Suspend
Overdue past the rule you set, and the credential is suspended rather than deleted — so restoring it is instant, and the history stays intact.
Revoke
Move-out revokes it in the same minute the agreement ends, so a former customer never keeps working access to a unit they have left.
03 / No more padlock runs
Someone pays at 9.41pm — the gate will open itself
The timing is already worked out today: exactly when an overdue unit should lock, and exactly when it should unlock again. Once a vendor is connected, that decision will reach the lock on its own — not a job on anyone's list.
Illustration of planned functionality: the schedule that decides an overlock — invoice issued on day zero, payment due day five, reminder and late fee day ten, overlock decision day fourteen — then the event chain where an overdue invoice opens a collections case and applies an overlock through the site's vendor, and a collected payment releases it the same minute.
04 / Every gate, one view
One timeline, not five different consoles
Every gate code issued, every entry, every lock and unlock — across every brand you run — will land in one place, in order, instead of five separate vendor screens.
Illustration of planned functionality: five separate vendor consoles, each with its own event vocabulary, contrasted against one normalised StoreBay timeline where access grants, an overlock, a site-bridge outage and a restore all appear in one feed with a consistent event name.
05 / Common questions
What operators ask about gates & entry
The honest answers, including the ones about what is not built yet.
No obligation · UK-based support · migrations handled