Unified cloud + edge, without the failure modes.
EntryOne is designed as a proprietary ecosystem: an edge device at the door paired with a protected‑side controller—managed from the cloud. The goal is simple: enterprise reliability on legacy infrastructure.
The per‑door “pair” model
Instead of one controller running many doors (a blast radius problem), each door becomes an independent cloud‑connected pair.
This “pair” model reduces single points of failure, enables door‑by‑door pilots, and isolates updates to a single doorway at a time.
Serverless cloud, regional by default
EntryOne Cloud is built on a serverless AWS stack—so deployments can be regional, elastic, and operationally lightweight.
- Spin up new regions for data residency or low‑latency requirements
- Elastic scale for events, video attachments, and fleet telemetry
- Per‑device TLS identity for secure provisioning and encrypted links
Why this matters
| Latency | Faster door events and quicker audit review when your stack is nearby. |
|---|---|
| Compliance | Regional options support residency and policy alignment. |
| Operations | No traditional servers to patch—updates flow through CI/CD and infrastructure‑as‑code. |
Distributed Edge Architecture 4‑wire lane isolation
Two lanes on the same legacy cable: one for IP/video and one for deterministic unlock.
Lane 1: IP + AI data
High‑bandwidth traffic for video, provisioning, and cloud telemetry.
Lane 2: Deterministic unlock token
A mission‑critical, low‑frequency path that remains responsive even when the network is noisy or busy.
2‑wire fallback mode
When the wire in the wall is degraded, the job should still be viable.
Use case
Legacy sites sometimes have only two usable conductors remaining. EntryOne can still deliver a cloud‑connected deployment using fallback strategies.
Concept
Power and data travel on the single pair, while the edge device can use an internal relay mode for actuation scenarios where the token pair is unavailable.
Deployment flow
A practical way to roll out in enterprises and communities.
- Bench test devices and confirm cloud visibility
- Pilot one door (prove performance on existing wire)
- Phase rollout door‑by‑door (no downtime)
- Enable advanced features (MFA, intrusion, LPR)
Next step
Tell us your environment (wire type, lock type, door count, and goals). We’ll propose a pilot layout and success criteria.