The Vendor Demo Problem
You're sitting in a Verkada demo. The UI is slick. Cloud backup is automatic. No on-site server to manage. The sales rep shows you a three-building campus, all cameras streaming to one dashboard, retention priced per camera per month. Facilities loves it. IT nods along. Then you get back to the office and start calculating actual costs for a 60-camera deployment across two states, with network uplink constraints at each site, and suddenly the math breaks.
Verkada works beautifully when you have:
- Solid, redundant internet at every location (10+ Mbps upload minimum)
- Budget for per-camera SaaS licensing (typically $8-$25/camera/month depending on retention)
- Tolerance for cloud-only storage (no local failover without a paid add-on)
- IT teams comfortable with all video data leaving the building
But that's not every job. And it's definitely not most jobs in retrofit or cost-sensitive environments.
The Real Alternatives Breakdown
Axis and Open ONVIF Stacks
Axis cameras paired with open-source or mid-market VMS (Milestone, Genetec, or even Frigate on Linux) gives you hardware flexibility and lower per-unit licensing. You buy cameras once. You buy or self-host software once. Retention lives on-site or in your own cloud account.
Trade-off: You own the architecture. Multi-site failover, redundancy, and remote access require actual network design. IT will need to participate in deployment, not just sign off on a vendor contract. Uptime depends on your NVR hardware and your backhaul connectivity, not Verkada's infrastructure.
Works best for:
- Organizations with in-house IT ops or a systems integrator on retainer
- Sites with constrained uplink (under 10 Mbps available for video)
- Shops that already run Milestone or Genetec for other reasons
- Deployments where footage cannot leave the premises for compliance
Eagle Eye Networks (EEN)
Eagle Eye sits between Verkada and a traditional NVR. Cloud-first like Verkada, but with optional on-site edge recording (a local NVR or appliance that buffers if internet drops). Per-camera licensing, but usually lower than Verkada. Dashboard is functional, not flashy.
The edge recorder approach is the real difference. If your uplink fails, the camera keeps writing to local disk. Once connectivity restores, footage syncs to the cloud. No dropped video, no angry facilities manager.
Works best for:
- Multi-site chains (retail, hospitality, warehouses) with flaky or metered internet
- Customers who want cloud convenience but need local failover
- Budgets tighter than Verkada but not DIY-on-Linux tight
Rhombus (AI-Forward Cloud)
Rhombus is newer, cloud-native, and aggressively priced on per-camera licensing. They push AI analytics (person detection, loitering, package theft) as bundled features, not add-ons. Strong in retail and quick-service restaurant chains.
Catch: Still cloud-first. Uplink requirements are similar to Verkada. Less mature than Eagle Eye or Axis on multi-site ops and failover. Better if you want AI and don't need local recording redundancy.
Hybrid Recording (Your Own NVR + Cloud Backup)
Build a local NVR (Hikvision, Uniview, Milestone-licensed hardware) at each site. Record everything locally to disk. Send key events or snapshots to cloud storage (AWS S3, Azure Blob, or a cloud VMS). Remote access via VPN or a cloud proxy.
This is what most integrators actually deploy on real jobs, even if they don't advertise it that way. It costs less per camera than pure Verkada. It survives internet outages. It gives you control over retention and storage location.
Trade-off: Requires more planning. Each site needs UPS, disk replacement strategy, and local IT touch. Multi-site search and correlation is clunky (you're logging into three different NVRs, not one dashboard). But it works, and it's predictable.
The Checklist: What Actually Matters
- Uplink at each site: Measure it. Don't assume. Under 10 Mbps? Cloud-first systems struggle. 10-50 Mbps? Manageable, but budget for peak load. Over 50 Mbps? Verkada-class platforms have room to breathe.
- Retention requirement: 30 days? 90 days? One year? Cloud licensing gets expensive fast at 90+ days. Local NVR disk is cheap; cloud egress and storage are not.
- Internet reliability: One ISP or dual backhaul? If single ISP and it fails often, edge recording or local NVR is non-negotiable.
- Compliance or data residency: Does footage stay on-site? If yes, cloud-primary is a non-starter.
- Multi-site correlation: Do you need to search across all locations from one pane of glass? Verkada and EEN do this well. Hybrid NVR stacks do not.
- IT involvement tolerance: Can you hand off to a cloud vendor? Or do you need hands-on control? Affects licensing, support model, and long-term cost.
- Camera count and growth: Verkada's per-camera licensing makes sense at 20-50 cameras. At 200 cameras, the math shifts to on-premise or hybrid.
Common Mistakes on the Job
Mistake 1: Assuming Verkada is cheaper because "no server." You're not buying a server; you're buying SaaS. Over five years, 50 cameras at $15/month each costs $45,000 in licensing alone. A used Milestone NVR and local storage cost $8,000 upfront, then $500/year in maintenance. Do the math for your customer's actual retention and camera count.
Mistake 2: Underestimating uplink constraints. A 4MP camera at 30 fps, H.264, moderate bitrate = 2-3 Mbps. Twenty cameras = 40-60 Mbps. Most commercial internet is 50-100 Mbps down, 10-20 Mbps up. You can't saturate the uplink with 20 cameras and expect business-as-usual traffic to flow. Oversizing the internet is cheaper than picking the wrong platform.
Mistake 3: Picking cloud-first without a local failover plan. Internet outages happen. Planned maintenance happens. If your system goes dark every time the ISP hiccups, you'll spend your margin on support calls and customer goodwill.
Mistake 4: Treating multi-site like single-site. Three buildings with three different ISPs, three different network closets, three different IT contacts. Verkada makes this look easy in the demo. In reality, you need to design redundancy, failover, and remote support at each node. Budget for it.
The Decision Path
Start here:
- Measure uplink and reliability at each site. Document it.
- Calculate total cost of ownership (hardware + licensing + maintenance) over 5 years for at least two options (cloud-first vs hybrid).
- List non-negotiables: failover behavior, data residency, remote access, analytics, retention length.
- If uplink is solid, budget is flexible, and you want minimal operational overhead, Verkada or EEN is defensible.
- If uplink is constrained, retention is long, or compliance requires local storage, hybrid NVR or Axis + open VMS is more honest.
- If you're unsure, spec a hybrid system with cloud backup. It's the safest middle ground and almost always cheaper than pure cloud on larger deployments.
Don't let vendor UI or your customer's budget anchor you to the wrong platform. The platform that fails over gracefully and scales predictably is the one that keeps you out of margin hell and your customer happy.
If you're evaluating platforms for a specific site profile or comparing licensing across your typical customer base, send over the specs. We can run the numbers and help you build a comparison matrix.