Choosing access control architecture

Physical access control is not one-size-fits-all. Before you pick an integration, it helps to map your requirements to hardware and network reality. This page is a practical buying-style guide: concepts and trade-offs, not a substitute for vendor manuals or certified design.

No rip-and-replace required

OpenApp does not require you to buy new access-control hardware. Whenever it is practical, reuse what you already have—many deployments can integrate a legacy or existing system instead of replacing it outright.

Paths people use include Home Assistant as a universal bridge, plugging into an already-connected vendor cloud or hub that OpenApp integrates with, or bringing offline controllers onto the network (for example Wi‑Fi, Ethernet, cellular, or a local automation hub) in a way that fits your safety and ops model.

If you are unsure what applies to your site, get in touch—we provide support and are open to adding integrations that are not in the catalog yet.

Price and what you are paying for

Solutions span a wide cost range. Very low-cost options (for example microcontroller boards such as ESP32-based designs) keep BOM (bill of materials) and experimentation cheap. Higher-priced commercial gear often buys you stronger mechanical packaging, certifications, longer vendor support, richer firmware, and sometimes a vendor cloud that lets you operate or diagnose devices out of band from OpenApp—useful when you need a fallback control path or remote troubleshooting that does not depend on your OpenApp stack.

Look for your own sweet spot: upfront cost vs operational stability, warranty, firmware updates, and whether a separate vendor portal is acceptable in your threat model.

Connectivity

Devices differ by how they reach the network:

• Wi‑Fi — common for single-door controllers; depends on stable WLAN coverage and configuration.
• Ethernet / PoE — wired links are often more predictable than wireless for dense or critical installs.
• Mesh or IoT radios (e.g. Zigbee / Z-Wave) — useful where Wi‑Fi is undesirable; usually mediated by a gateway or automation hub.
• Cellular (3G / 4G / LTE) — independent of the building’s LAN; strong where there is no reliable local internet or where you want the access path decoupled from office or home Wi‑Fi. Range and subscription costs are part of the trade-off.

Your integration choice should match where the device can live on the network and who maintains it.

Number of doors and cost per opening

One controller per door is simple to reason about but can get expensive when many doors sit side by side (typical offices). Multi-channel relay boards or central switchboard-style controllers drive much lower price per door and a single wired attachment (for example Ethernet + PoE) back to the network closet—often more stable than many separate wireless devices.

Balance: wiring effort and a single point of failure vs fewer moving parts in the radio layer.

Physical locking hardware

Software and integrations sit above the actuator. Plan the lock or strike itself: electric strikes, electromagnetic locks, motorized locks, gate operators, and dry-contact inputs/outputs each have electrical, fail-safe vs fail-secure, and mechanical constraints. OpenApp orchestrates commands; your installer should size power, wiring, and hardware for the opening.

Compliance is on you

OpenApp does not design, certify, or enforce your local access-control, fire, life-safety, or building codes. Requirements vary by jurisdiction (for example fire egress, emergency release, accessibility, alarm interlocks). You and your installer are responsible for meeting all applicable rules. Treat compliance as a first-class design input, not an afterthought.

For a product-level view of how OpenApp combines integrations, devices, users, delegation, invitations, and audit into one access-control model across different sectors, see Access control model by sector.

Continue reading

• Fallback when phones and networks fail, and why the weakest parallel path sets real risk — when your primary app path is down, and how extra entry methods combine.
• Access control model by sector — how one modular model maps to homes, apartment buildings, offices, rentals, hotels, and campuses.
• Suggested integration directions (non-exhaustive) — many doors, Wi‑Fi, cellular, DIY, and Home Assistant as a bridge.

---

For wiring an integration after you choose an architecture, continue with Getting started and the Integrations catalog.