CSLB #472017, C-7 Low Voltage Systems

Guide · 9 min read

Cloud vs On-Premise Access Control: Choosing an Architecture for a Commercial Building

Cloud-managed, on-premise or hybrid: IT directors, property managers, architects and estimators deciding how a new or replacement access control system should be hosted can compare all three in this guide, along with the platforms commonly specified for each, what happens when the internet drops, and how the cost picture changes over a ten year life.

Published
September 12, 2026
By
Telelink Business Services
CSLB #472017 · Licensed C-7 contractor Person tapping an access card on a wall-mounted reader

The short answer

In a cloud-managed access control system, the door controller stays on site while the credential database and administration console are hosted by the vendor and billed as a per door subscription. In an on-premise system, both run on a server the owner controls, under a perpetual license plus an annual support agreement. Controllers on both architectures keep unlocking doors from a cached credential database when the network or the server is unavailable. So the practical difference is who patches the software, who backs up the database, and how the recurring cost shows up.

Key points
ArchitecturesCloud-managed, on-premise server, hybrid
Cloud platformsBrivo, Verkada, Avigilon Alta
Hybrid platformUniFi Access, local console with cloud access
Enterprise on-premiseGenetec Synergis, LenelS2 OnGuard and NetBox
MultifamilyButterflyMX video intercom and smart access
Equipment listingUL 294 access control system units
Reader protocolOSDP v2 with Secure Channel preferred over Wiegand

Three architectures: where the controller, database and admin live

Every access control system has four parts: a reader at the door, a controller that decides whether to unlock, a database of credentials and schedules, and an administration interface. The architecture question comes down to where the last two live.

In a cloud-managed system, the controller is on premises, in a telecom room or above the door, and it reports to a vendor-hosted service over an outbound internet connection. The database of record and the admin console live in the vendor’s cloud. Nothing on site needs a static IP or an inbound firewall rule.

In a fully on-premise system, the database and admin console run on a server the owner controls. That can be a physical server in the MDF, a virtual machine, or an embedded appliance. Controllers talk to that server over the building LAN, and nothing leaves the building unless the owner sets up remote access.

A hybrid system keeps the server and controllers on site and adds a cloud layer for remote administration, mobile credentials or multi-site reporting. Decisions and records stay local, and the vendor cloud acts as a relay for remote login.

The difference matters less at the door than in the IT department. The reader, door position switch, request-to-exit device, lock power and cabling are the same in all three cases. What changes is who patches the software, who backs up the database, and what the invoice looks like in year six.

Platforms commonly specified for each architecture

The table lists the platforms that show up most often on California Division 28 specifications. We install and configure ButterflyMX and DoorKing systems, and we install the others to the project specification. We don’t claim any certification, authorization or partnership with any manufacturer.

PlatformArchitectureTypical fitNotes on naming
Brivo AccessCloud-managed, controller on premisesMulti-site commercial, property portfoliosReader-agnostic controllers, Wiegand and OSDP
Verkada AccessCloud-managed, controller on premisesOffices, schools, sites with Verkada camerasOwn readers and controllers, per-door license terms
Avigilon Alta AccessCloud-managed, controller on premisesOffices, mobile-first credential programsFormerly Openpath; acquired by Motorola Solutions and rebranded. Older specs still say Openpath
UniFi AccessHybrid: local console, cloud remote accessSmall and mid-size commercial on UniFi networkingRuns on a local UniFi console; no recurring per-door license as of 2026
ButterflyMXCloud-managed intercom and accessMultifamily and senior housing entries, elevators, package roomsProperty-wide subscription; resident app and video intercom
DoorKing (DKS)On-premise controllers, optional cloud managementVehicle gates, telephone entry, parkingLong-standing gate and telephone entry line
Genetec Security Center SynergisOn-premise server, cloud options availableEnterprise, campus, public agency with IT operationsUnified with Genetec Omnicast video
LenelS2 OnGuard and NetBoxOn-premise server or embedded applianceEnterprise, healthcare, governmentOnGuard for large enterprise; NetBox for mid-size

Names change. Openpath became Avigilon Alta, Avigilon’s on-premise line became Avigilon Unity, and several manufacturers sell the same controllers under both a subscription and a perpetual license. Check the current name and licensing model before pricing.

Licensing: subscription, perpetual, and what each one buys

Cloud platforms are sold as a subscription, usually per door per year, sometimes per user or per site. The subscription covers hosting, updates, the admin console, support, and mobile credentials on most platforms. Some vendors sell one to ten year terms up front, while others bill annually. If you stop paying, administration stops after a grace period, although the doors keep working on the last downloaded database.

On-premise platforms are sold as a perpetual license plus an annual support agreement, priced as a percentage of the license. The license doesn’t expire. The support agreement buys upgrades, patches and vendor support, and most owners keep it current because an unsupported server on a corporate network is a liability. On top of that you have server hardware, an operating system license, database licensing on larger platforms, and a refresh cycle.

So you’re comparing one visible annual fee against a set of less visible annual costs. Over ten years, for a 20 door building, the two often land in a similar range. The subscription is easier to budget. The perpetual license is easier to defend where a server room and a patching schedule already exist.

What happens when the internet or the server goes down

Cloud-managed controllers on the platforms above hold a local copy of the credential database and schedules. When the internet fails, the controller keeps reading cards and unlocking doors on the last synced rules, and it buffers events until the link comes back. Two things don’t work during the outage. Console changes (a new hire, a revoked badge) don’t reach the door until the controller reconnects. And mobile credential modes that route through the cloud may fall back to Bluetooth or stop working.

On-premise systems behave the same way when the server goes down: controllers carry on with cached rules. The difference is who handles recovery. On a cloud platform, the vendor’s availability is in the contract. On an on-premise platform, getting the server back is the owner’s job, which means backups, a spare, and someone who knows the system.

Two habits cover both cases. Put controllers on a UPS so a power blip doesn’t reboot them in the middle of the day. And set the fail-safe or fail-secure behavior of each lock deliberately. Doors in the path of egress must allow free exit at all times, regardless of what the software is doing.

Credentials and readers: prox, smart cards, mobile, and OSDP

The 125 kHz proximity card that most buildings installed in the 1990s and 2000s transmits its number in the clear, and it can be copied with a handheld cloner. Replacing 125 kHz prox cards removes the easiest attack on the system.

13.56 MHz smart cards (MIFARE DESFire, HID Seos and iCLASS SE are the names you’ll see) store the credential in an encrypted application and authenticate with the reader before releasing it. Mobile credentials use Bluetooth Low Energy or NFC from a phone, and they’re issued and revoked from the console without printing anything.

Between the reader and the controller, there’s a second choice. Wiegand is a one-way, unencrypted interface that has been the default for decades. OSDP version 2 with Secure Channel is bidirectional and encrypted, supports reader supervision, and allows firmware updates over the same wires. We’d specify OSDP for new construction. On a retrofit, an OSDP reader on the existing wiring is usually possible.

Whatever the platform, specify UL 294 listed access control equipment. That’s what an inspector and an insurer are likely to ask about.

Integrating access control with video and intercom

The reason to pick a platform often has less to do with the controller than with what it connects to. Video association ties a door event to a camera clip, so an operator reviewing a forced door sees the person and not just the log entry. Platforms that make both cameras and controllers do this natively. Cross-vendor integrations exist through APIs, and they’re worth testing before the specification names them. On any project touching federal funds, the camera line must meet Section 889 and 2 CFR 200.216; see our NDAA compliant cameras guide.

Intercom integration lets a visitor call a resident or a front desk, and lets that person unlock the door from a phone or a station. In multifamily this is the core of the system. A ButterflyMX lobby panel calls the resident’s phone, the resident sees video and unlocks, and the same platform runs amenity keypads and elevator access. In commercial buildings, the intercom is more often a SIP device at a secured entry tied to the phone system. Our intercom and entry systems page covers both.

Elevator control, visitor management and identity provider sync (Microsoft Entra, Okta, Google Workspace) come next. Identity sync is worth pricing on any office project, because it deactivates the badge when HR closes the account.

IT security considerations the spec should state

An access controller is a network device with a web interface and a firmware version, so treat it like one. Require a dedicated VLAN for physical security devices (controllers, IP readers, cameras, intercom panels), segmented from the corporate network. The firewall rules should allow only what the platform needs: outbound HTTPS to the vendor for cloud platforms with nothing inbound, and server-to-controller LAN traffic for on-premise.

Require multi-factor authentication on every administrator account, single sign-on where it’s supported, and role-based permissions so a leasing agent who issues fobs can’t change door schedules. Require a firmware update policy too. Cloud platforms push updates, which the owner should be able to schedule. On-premise platforms leave the owner to apply them, so name who does it. Finally, require audit logging of admin actions, default credentials changed at commissioning, and a closeout package with the IP addressing, VLAN assignments and firewall rules as installed.

These items are often missing from Division 28 specifications, and they tend to get argued over at commissioning. Writing them into the spec moves that conversation to bid time.

Ten year cost view and a decision table by building type

The figures below are California commercial planning ranges as of 2026, not quotes. Door hardware, door count and existing pathways move them more than the platform choice does. Our access control installation cost guide covers installed cost per opening in detail.

Cost elementCloud-managedOn-premiseNotes
Installed cost per door (reader, controller share, cabling, labor)SimilarSimilarRoughly $2,000 to $6,000 per door before electrified hardware
Electrified door hardwareSameSameDivision 08 or C-28 scope, coordinated, not in the low voltage number
Software, year 1Per-door subscriptionPerpetual license plus first-year supportRoughly $150 to $600 per door per year, about $12 to $50 per door per month, by platform and term
Software, years 2 to 10Same subscriptionAnnual support, often 15 to 20 percent of licensePlus at least one server refresh in ten years
Server, OS, backups, staff timeNone on siteOwner’s costOwner cost, not invoiced by the vendor
Building typeUsual recommendationWhy
Multifamily and affordable housingCloud (ButterflyMX at entries, cloud or hybrid at staff doors)Resident turnover, remote management, no on-site IT
Senior and assisted livingCloud or hybridStaff doors and nurse call coordination; local decisioning is essential
Office, tenant improvement, multi-site businessCloudIdentity sync, mobile credentials, one console across sites
K-12 and higher educationFollows district or campus standardLockdown functions and existing standards outweigh preference
Government and public agencyOften on-premise or hybridIT security policy, data residency, procurement rules
Healthcare and clinicsSmall clinics cloud; hospitals on-premise enterpriseIntegration with existing enterprise systems
Industrial and warehouseCloud with DoorKing gate controlVehicle gates, shift schedules, remote sites

The smaller the on-site IT operation and the more sites in the portfolio, the stronger the case for cloud. The larger the existing security operation and the stricter the data policy, the better on-premise or hybrid fits. If you’re still deciding who should install it, our guide on how to choose a low voltage contractor in California covers what to ask.

Next step

Send us the door schedule, the building type and the platform you’re leaning toward (or ask us for a recommendation if you haven’t picked one) through request a bid. We’ll return a per-door scope that separates our work from the electrified hardware work, along with the network requirements and the licensing model. General contractors can find our standard exclusions on the for general contractors page, and the full service description is on our access control systems page.

FAQ

Questions we hear about this

Do doors stop working if the internet goes down on a cloud access control system?

On the platforms commonly specified, no. The door controller holds a local copy of the credential database and schedules, and it keeps making unlock decisions. What stops is administration. A badge you revoke during the outage isn't revoked at the door until the controller reconnects, and events are buffered until then.

Link to this answer
Is cloud access control more expensive than on-premise over the long run?

It depends on the door count and whether the on-premise server, patching and staff time are counted. A per-door subscription shows up on every invoice. An on-premise system carries server hardware, operating system patching, annual software support, backups and staff time. Over ten years, for a building with a few dozen doors, the two often land in a similar range, and which one comes out ahead depends on whether the server, the patching and the staff hours are costed honestly. At several hundred doors with an existing IT operations team, on-premise can be clearly cheaper.

Link to this answer
Can I keep my existing card readers and cards when moving to a cloud platform?

Often yes for the readers, if they use Wiegand or OSDP and the new controller supports that interface. Whether the cards carry over depends on the credential technology. Older 125 kHz prox cards can usually be read, but they're easily cloned, so a migration is a good time to move to 13.56 MHz smart cards or mobile credentials.

Link to this answer
Who owns the data on a cloud access control platform?

The contract decides that, and contracts differ. Most vendors treat cardholder records and door events as the customer's data and see their own role as hosting it. The terms that matter, though, are the ones that apply on the day you leave: what export format you get, how long the data survives cancellation, and whether any of it can be loaded into a competing platform. It's worth settling those in writing before a portfolio is standardized on one vendor.

Link to this answer
Does access control count as an alarm system in California?

Cameras and access control are installed under the C-7 classification. Burglar and intrusion alarm systems are a separate scope. Alarm monitoring requires a BSIS Alarm Company Operator license, so we don't offer monitoring and refer it to a licensed alarm company.

Link to this answer

Didn't find your question? Ask us, and you'll talk to someone who does this work.

Call (916) 340-7503Email usOr send drawings to bid
TelelinkBusiness Services, home

Ready to apply this to a real building?

Send over the drawings or describe the scope. We'll tell you what we'd take on, what we'd coordinate with other trades and what it will take to do it right.