The right architecture protects the video you actually need.
The most useful question is not “Where should video live?” It is “Will the right people have usable evidence, for the required time, under the site’s real operating conditions?”
Describe the cameras and views first: scene detail, lighting, analytics, live monitoring, retention, export and who investigates events. Then compare how each architecture meets those needs. “Cloud” can describe management, recording, storage or remote access; those functions do not always live in the same place.
Cloud-managed
Management and some or all video services are delivered through a provider. Recording may still occur at an edge device or local bridge, depending on the product and configuration.
On-premises VMS
Recording and system services are hosted on customer-controlled site infrastructure, with local servers and storage sized for camera load and retention.
Hybrid
Local recording and cloud services can be combined for remote management, selected cloud retention, backup or other specified workflows.
Migration path
A phased plan may preserve supportable cameras or recording resources while changing management, storage or investigations over time.
These are design patterns, not promises about every vendor. Confirm actual behavior and licensing for the selected platform.
Questions to answer before selecting a platform.
| Decision | Cloud-managed questions | On-premises questions |
|---|---|---|
| Multi-site users | How are sites, roles and investigations administered centrally? What happens if the provider or WAN is unavailable? | How are multiple sites federated and kept current? Who manages remote access securely? |
| Retention | What is stored locally versus uploaded, at what quality, for how long, and at what recurring cost? | What server and storage capacity, redundancy, archive and backup arrangements are required? |
| Bandwidth | Which streams or events use the uplink? How do limited bandwidth and outages affect upload and playback? | What local network capacity is needed? What traffic is generated by remote viewers, exports and any off-site archive? |
| Maintenance | Who handles cameras, bridge hardware, subscriptions, updates and vendor support? | Who handles servers, storage, operating systems, VMS versions, backups and licenses? |
| Integrations | Which access control, analytics, incident and identity workflows have been verified for this product? | Which camera, access and third-party integrations are supported by the chosen version? |
Retention and bandwidth are calculations, not labels.
Document each camera’s intended resolution, frame rate, codec, scene activity, recording schedule and retention objective. Include growth, overhead, required redundancy and any evidence that must be preserved beyond ordinary expiration. Compare a typical day and a busy day where activity-based recording changes the bitrate.
A cloud system may upload continuous video, selected events or another subset; a local recorder can also use WAN bandwidth for remote viewing or off-site storage. Ask for a network-flow diagram and a per-site uplink estimate based on the actual deployment model.
Milestone’s documentation describes configurable recording and archive parameters, including retention and storage behavior for its VMS. Axis documents local and optional cloud storage in its product family. These examples show why a general term such as “hybrid” must be tied to a specific product configuration. See source notes.
Test the failures the owner will have to manage.
Write these behaviors as test cases. Avoid describing a system as “always recording” or “fully redundant” unless its actual architecture, capacity and procedures support that claim.
Compare the full lifecycle, not only the first purchase.
For both options, price the cameras, cabling, switching, installation, configuration, training and service. Then include the items that differ: server and storage refresh, operating-system and VMS upkeep, cloud subscriptions, per-camera licensing, uplink changes, support and warranty terms.
Ask for a multi-year total that identifies the owner of every component and shows assumptions about camera growth, retention, software changes and replacement timing. A lower installation price may be sensible, but it cannot be compared fairly with another proposal until recurring and refresh costs are visible.
Make the investigation workflow part of commissioning.
- Find a defined event using the roles and devices your staff will actually use.
- Verify playback at the required image quality for representative cameras and lighting conditions.
- Export footage, confirm timestamps and test the handoff to an authorized recipient.
- Check health alerts, retention settings and the response to one planned network or device outage.
- Receive camera inventory, network diagram, configured roles, license and support details, storage assumptions and an open-item list.
Questions buyers often ask.
Is cloud video automatically more secure?
No architecture is secure by label alone. Evaluate identity controls, updates, encryption options, network segmentation, access logging, data handling and who operates the system for the chosen product.
Will on-premises VMS work without the internet?
Local recording may continue during a WAN outage if the cameras, network, servers and power remain available. Remote users and cloud-connected functions can still be affected. Verify the actual design.
Can we reuse existing cameras?
Possibly. Check model support, firmware, image quality, protocols, security posture, licensing and whether the chosen architecture supports the desired features.
Is hybrid the safest choice?
Not automatically. It may combine useful local and cloud capabilities, but it adds interfaces and responsibilities that must be specified and tested.
Let the investigation requirement decide the architecture.
Terapixels can evaluate camera coverage, VMS options, server and storage needs, bandwidth, integrations, migration and support as one commercial video system. A recommendation should describe the actual recording path, the failure behavior and the owner’s long-term responsibilities.
Technical source notes
- Milestone Systems, XProtect Storage Architecture: configurable recording, archive and retention parameters.
- Axis Communications, AXIS Camera Station Edge feature guide: local storage and optional cloud storage in one product family.
- Platform behavior and pricing change. Verify the current architecture, licensing, firmware and terms for the exact proposed configuration.
Plan this with Terapixels.
Share your facility, existing systems and the decision you need to make. We will help identify the right scope and next step.
Discuss a project ↗