The two architectures, in one paragraph
Edge AI runs the model directly on the camera or a small appliance next to the cameras. The video stays local; only events, thumbnails, and on-demand clips travel out. Cloud AI sends raw footage to a data center, runs the model there, and surfaces results in a web app. Both work, and the picking criteria are mostly about your physical sites, not your IT preferences. Across the Tec-Tel customer base, most production installs end up hybrid: analytics at the edge for workflows that have to survive a WAN outage, cloud-managed VMS for review, mobile access, and cross-site search. Nearly every modern platform supports both modes.
Bandwidth: the math that decides for you
A 4K H.265 stream runs roughly 4 to 8 Mbps continuous. A 32-camera site streaming everything to cloud burns 128 to 256 Mbps of sustained upload. Most retail, QSR, manufacturing, and multi-tenant residential sites don't have that on tap. Edge AI changes the math: the camera or local appliance runs the analytics, then ships out events, thumbnails, and on-demand clips, dropping the same 32-camera site to under 5 Mbps of upload most of the time, with a brief spike when an investigator pulls a clip.
The other half is reliability. When the cable provider drops at a remote site, edge AI keeps detecting and recording. Cloud-only AI goes blind for the duration. For anything mission-critical (loss prevention, after-hours intrusion, safety alerts), the edge layer has to keep running.
What each architecture does well
Edge AI shines on real-time decisions from a single camera's view: intrusion detection, person and vehicle classification, license plate recognition, PPE compliance, loitering alerts. The model fires in the camera's processor, the alert leaves the site as a small payload, and latency is sub-second. Most major manufacturers now ship mature edge-AI fleets with on-camera classification standard.
Cloud AI shines on cross-camera context, large-scale search, and rapid model updates: forensic search across 500 sites for a specific vehicle, plate matching against a fleet-wide hot list, behavior analytics over hours of footage, centralized retraining without touching every camera. Camera-agnostic cloud platforms (Dragonfruit AI, Intenseye) run on whatever cameras the site already owns and add cloud-scale analytics without a rip-and-replace, often the fastest path to AI for a mixed-vendor fleet.
The hybrid pattern most installs end up with
Three layers. Edge cameras handle real-time detection, recording, and the analytics that have to keep firing during a WAN outage. A cloud VMS aggregates events, thumbnails, and on-demand clips for cross-site review and mobile access. Cloud analytics (where applicable) run pattern-detection workflows that don't need sub-second latency. The bandwidth bill stays low, mission-critical analytics survive outages, and the corporate team gets a single pane of glass across every site. This is the architecture we deploy for QSR chains, multi-site retail, manufacturing networks, and self-storage operators across the country.
The decision framework, condensed
Three questions get a buyer 90 percent of the way:
- How many sites and how reliable is the WAN at each? Multi-site or unreliable WAN means edge-first.
- Which analytics have to keep firing during an outage? Loss prevention, intrusion, safety alerts almost always have to. Forensic search and pattern analysis usually don't.
- What's the existing camera fleet? Mixed-vendor existing fleet means camera-agnostic cloud analytics get you to AI fastest.
That's the framework. The free consultation puts your site count, bandwidth profile, and existing fleet against it and produces a written architecture recommendation.