A 32-camera clinic is the size where the cloud versus on-prem question gets real. At 8 cameras either model works fine. At 32 the numbers start to push on your internet circuit, your storage budget, and your compliance paperwork in ways that are easy to miss on a sales call. Here is how we walk a medical practice through the decision before anything gets ordered.
The two models, briefly
On-prem means a network video recorder (NVR) in your closet, recording to local drives. Hanwha, Axis, and similar platforms work this way. The footage lives on site, and you reach it over your local network or a secured connection you control.
Cloud means each camera, or a small on-site bridge, connects to a provider's data center, and you manage and watch everything through a web portal or app. Verkada and Eagle Eye are common names. Some cloud platforms record on the camera or the bridge and upload only what you view or flag. Others store the full recording in the cloud. That difference matters a lot for bandwidth.
Both can be done well. The right answer depends on your upload pipe, how long you have to keep footage, and how your compliance officer wants to handle access.
The upload pipe decides a lot
This is the first thing people underestimate. If you want full cloud retention, every camera's stream has to go out to the internet continuously, and most business circuits on the South Plains are asymmetric. You might have a healthy download number and a much smaller upload number, and upload is the direction that matters.
Rough math: 32 cameras at 1080p with H.265 can run 1 to 4 Mbps per camera depending on frame rate, motion, and scene. At 2 Mbps each, that is about 64 Mbps of sustained upload, all day. At 4 Mbps it is closer to 130. If your circuit only offers 20 Mbps up, full cloud recording will not fit, and it tends to fall behind when several cameras see motion at once.
Cloud vendors handle this with on-site storage, buffering, and selective upload, so it is not always a hard wall. Even so, cloud video at this scale wants real upload bandwidth, and on a thin circuit an on-prem NVR sidesteps the problem because the recording traffic never leaves the building. Before we recommend cloud at this scale, we look at your actual circuit and whether a fiber upgrade is realistic at your address.
Retention is where the cost shows up
HIPAA does not set a number of days for camera footage. Practices usually pick 30, 60, or 90 days based on their own policy and counsel. That choice drives storage, and storage is priced very differently in the two models.
On-prem, retention is mostly a drive purchase, sized once and owned. You can model it: bitrate in Mbps, divided by 8 for megabytes, times 86,400 seconds per day, times days, times cameras. At a constant 2 Mbps, 32 cameras for 90 days comes to roughly 62 TB before motion-based recording cuts it down. When you want more days, you add drives.
Cloud retention is a recurring line on every invoice for the life of the system, and longer retention usually means a higher tier per camera. Over several years the subscription can exceed the cost of owning hardware, especially at 32 cameras. In exchange, cloud bundles in maintenance, offsite copies, and updates that you would otherwise manage yourself. We put both on a multi-year basis so you are comparing total cost of ownership, not a hardware quote against a monthly fee.
HIPAA, audit trails, and access
For a clinic this part deserves real attention. Footage that can capture patients, check-in areas, or screens may fall under your HIPAA obligations, so how access is controlled and logged matters.
Cloud platforms generally have built-in audit logging: who viewed what, when, and from where, with clean exports. That helps in a compliance review. If footage may include patient information, ask whether the vendor will sign a business associate agreement (BAA), and get it in writing before you commit.
On-prem keeps the data physically in your control, which some compliance officers prefer, but access control and logging are only as good as the configuration. The HIPAA Security Rule expects unique user IDs and audit controls on systems that hold patient information. A local NVR with one shared admin password does not meet that. If you go on-prem, the build should include per-user accounts, role-based access, encrypted remote access, and real logging, designed in from the start.
Neither model makes a practice HIPAA compliant by itself. Either one can support your compliance program if it is set up and documented properly.
How we usually frame it
A thin upload circuit, a preference for owning your data, longer retention, and a tight long-term budget tend to point toward a well-configured on-prem NVR. Plenty of upload bandwidth, multiple sites to manage from one screen, limited IT staff, and a willingness to pay monthly for offloaded maintenance point toward cloud. Many clinics end up with a hybrid: local recording for bulk retention plus cloud access for the cameras that matter most remotely.
Who we are
West Texas Wi-Fi & Networking is a veteran-owned contractor in Lubbock. We design and install commercial Wi-Fi, cameras, access control, and cabling across West Texas, and we hold a Texas Department of Public Safety security license (B31108601) for the camera and access control work. If you want a second set of eyes on your building, book a free site survey or call (806) 370-9434.