One platform. Total confidence.
XipherOne runs inside your network. XipherCloud runs in ours. Same hardware, same credentials, same policy model — pick the one that fits your risk appetite, and change your mind later.
One screen for every door, camera and alarm you own.
XipherOne runs inside your own network and unifies access control, video and sensors into a single operator view. Built for organisations that need their identity data to stay on their infrastructure, and that keep adding sites.
Doors, live video, alarms and visitor traffic on one timeline, with drag-and-drop layouts per operator.
From one building to a thousand doors across regions, with clustered servers and no per-door licence traps.
REST and gRPC APIs, a device SDK and certified integrations with HR, ERP and building management systems.
TLS 1.3 in transit, AES-256 at rest, signed firmware and role-based access with full audit history.
One console, every event type
Zero on-prem. Every site, from one browser tab.
XipherCloud puts the same biometric engine in a managed cloud tenancy. No servers to rack, no VPNs to maintain, and new branches come online the day the reader is mounted.
Readers connect outbound over TLS. Nothing to expose, nothing to patch on site.
Group branches into regions, delegate administration locally and keep one global policy.
Face, fingerprint, mobile, QR, RFID and PIN, mixed freely across the same estate.
Firmware, analytics models and features roll out continuously with no maintenance window.
One console, every event type
On-premise or cloud?
Most organisations already know which side they are on. This is the honest version of the difference.
XipherOne vs XipherCloud
| Where identity data lives | XipherOne: your servers. XipherCloud: our managed tenancy, pinned to a region you choose. |
|---|---|
| Infrastructure you run | XipherOne: servers, backups, patching. XipherCloud: none. |
| New site onboarding | XipherOne: server or VPN link required. XipherCloud: mount the reader, it appears. |
| Offline behaviour | Identical. Controllers decide locally and backfill events when the link returns. |
| Hardware | Identical. The same readers and controllers register to either platform. |
| Upgrades | XipherOne: scheduled by you. XipherCloud: continuous, no maintenance window. |
| Typical fit | XipherOne: data centres, government, single large campuses. XipherCloud: multi-branch retail, schools, growing estates. |
Open by default, not by exception
A security platform that cannot talk to your HR system becomes a second HR system. Ours is documented, versioned and stable, so your team can automate the parts that should never be manual.
- REST and gRPC APIs with published OpenAPI specifications
- Device SDK in C, Java, .NET and Python
- SCIM and LDAP directory synchronisation
- Webhooks for every event type, with retry and signing
- OSDP v2, ONVIF and BACnet on the device side
Need more information?
Tell us about the site, the doors and the standards you have to meet. A Xipheredge specialist will come back within one business day — no obligation.