// Deployment Blueprint

8-Camera Edge AI Deployment Blueprint

Last updated: March 2026

This blueprint covers a complete 8-camera PoE deployment with local inference, bounded storage retention, managed VLAN networking, UPS protection, and a practical day-0 to day-2 rollout pattern. It balances cost, operational visibility, and reliability for production edge AI nodes.

8 PoE cameras

~344 GB/day at 4 Mbps

150W+ PoE budget

Managed VLAN design

Quick Answer

An 8-camera edge AI deployment is a coordinated system: PoE switch powers cameras, managed switch provides VLAN isolation, Jetson-class compute runs inference, NVMe holds 3–7 days of footage, and UPS protects against data corruption during power loss. This blueprint covers balanced configurations for teams deploying 6–10 cameras to a single local node with on-premise inference.

Use the Power Budget Planner and Full Deployment Planner to validate your exact camera draw, storage needs, and network bandwidth. See the BOM and sizing sections below for concrete component selection.

Planning Takeaway

Successful 8-camera deployments treat the system holistically: cameras, PoE budget, compute throughput, storage endurance, VLAN isolation, and UPS runtime all interact. Optimize any one component in isolation and the others fail. Size the entire stack together, validate under burn-in, then lock down the configuration.

Who This Page Is For

Teams deploying 6–10 PoE cameras to a single on-premise edge compute node
Engineers needing local inference and bounded storage retention (no cloud dependency for core operation)
Operators planning long-term, maintainable deployments with infrequent on-site access
Architects comparing budget / balanced / industrial build configurations and learning design tradeoffs

Overview

When to use this blueprint

Deploying 6–10 IP cameras feeding a single on-premise edge compute node
Running continuous inference (object detection, tracking, classification) on live streams
Environments requiring local data retention — no cloud dependency for core operation
Locations with constrained power (sub-500W total system budget) or limited rack space
Projects where long-term maintainability, drive endurance, and UPS coverage matter

Key constraints

Power: PoE switch budget, compute TDP, and UPS headroom must all be planned together
Thermals: Fanless or semi-fanless compute in a sealed enclosure requires careful thermal derating
Bandwidth: 8 × 1080p streams at 4–6 Mbps each generates 32–48 Mbps — uplink and internal switching capacity matters
Storage endurance: Continuous 24/7 writes to SSD from ring buffer workloads can exhaust low-endurance drives within months
Maintenance windows: Edge deployments often have infrequent on-site access — design for remote management from day 1

Architecture Diagram

  [Camera 1–8]
       |
       | (PoE, Cat6)
       v
  [PoE Switch]  <-- managed, VLAN-capable, 150–250W PoE budget
       |
       | (Gigabit uplink)
       v
  [Edge Compute Node]  <-- Jetson-class or x86, NVMe + optional HDD/NAS
       |
       | (Ethernet)
       v
  [Router / Firewall]
       |
       v
  [Optional: Cloud / Remote Monitoring]

Cameras: IP cameras with PoE power; source of all video streams
PoE Switch: Powers cameras over Cat6 and aggregates traffic onto a Gigabit uplink
Edge Compute Node: Runs inference, records video to local storage via ring buffer
Router / Firewall: Network boundary for outbound traffic, VPN access, and security isolation
Optional Cloud: Metadata sync, alert forwarding, or remote OTA — not required for core operation

Bill of Materials (BOM)

Characteristics are specified rather than exact models to remain vendor-neutral. See official vendor specs and standards when cross-checking datasheets.

Component	Recommended spec	Typical range	Notes
IP Cameras (×8)	1080p or 4MP, H.265, PoE (802.3af/at), 6–15W draw	$60–200 each	Confirm max power draw per camera; PTZ cameras draw more
PoE Switch	8+ PoE+ ports, managed, 150–250W total PoE budget, Gigabit uplink	$150–400	Budget > sum of camera watts + 25% headroom; see PoE sizing section
Edge Compute	Jetson Orin Nano/NX (40–100 TOPS) or x86 mini PC with discrete NPU/GPU	$250–900	Match TOPS to number of streams and model complexity
NVMe SSD	M.2 2280 NVMe, 1–4 TB, ≥600 TBW, pSLC or MLC NAND preferred	$80–200	Endurance critical for 24/7 ring buffer writes; check TBW rating
HDD / NAS (optional)	NAS-rated HDD for long-term archive tier, 4–12 TB	$80–250	Use as secondary archive, not primary ring buffer; survives power cycles better with NAS-rated drives
UPS	750–1500 VA, pure sine wave output, USB or serial management port	$100–300	Size for full system load + 20 min runtime; pure sine required for active PFC PSUs
Router / Firewall	Gigabit WAN/LAN, VLAN support, VPN capable	$60–250	Camera VLAN isolation strongly recommended
Enclosure / Rack	Wall-mount rack or IP54+ industrial enclosure depending on environment	$80–400	Consider thermal management; fanless compute in sealed enclosures needs heatsink sizing
Cabling	Cat6 for PoE runs, 23 AWG solid core; limit runs to 90m for PoE+ reliability	$0.20–0.60 per foot	Label all cables; document port assignments at installation

Power & PoE Budget Sizing

Example calculation for 8 cameras at 12W each:

  Camera load:      8 × 12W = 96W
  Switch overhead:         10W
  Subtotal:               106W
  Headroom (25%):     +26.5W
  Recommended budget:   ≥133W  →  choose 150W or 180W tier

Use the Power Budget Planner to calculate this for your exact camera wattage and headroom preference.

Per-port vs total budget: A switch rated "30W per port" with 8 PoE ports does not have a 240W PoE budget. The total budget is a separate, typically lower value listed in the spec sheet. Both limits must be satisfied simultaneously.

Storage Sizing (Retention + Endurance)

Retention example

Assuming 8 cameras at 1080p, H.265, average 4 Mbps per stream:

  Per camera per day:  4 Mbps × 86400 sec / 8 = ~43 GB/day
  8 cameras per day:   8 × 43 GB = ~344 GB/day
  7-day retention:     344 × 7  = ~2.4 TB
  14-day retention:    344 × 14 = ~4.8 TB
  30-day retention:    344 × 30 = ~10.3 TB

Raw math suggests that a 2 TB NVMe holds ~7 days of footage. However, real usable retention is lower due to filesystem overhead (ext4 typically reserves ~5%), reserved partitions for logs and system state, and intentional over-provisioning to extend SSD life. Plan for ~6 days usable retention with a 2 TB drive.

For longer retention, use an HDD archive tier: keep 3–7 days on NVMe (hot storage) and archive older footage to a NAS-rated HDD. A ring buffer strategy overwrites oldest footage automatically once capacity is reached.

Endurance estimate

At ~344 GB/day writes, a drive accumulates ~125 TB/year. A 600 TBW drive provides roughly 4.8 years of write life at this rate — adequate with margin. A 300 TBW consumer drive may exhaust in ~2.4 years.

Use the Storage Endurance Tool to calculate expected lifespan for your specific workload. See SSD endurance ratings for detailed TBW/DWPD guidance.

Networking Notes (Practical)

Camera VLAN: Isolate all cameras on a dedicated VLAN. This prevents cameras from accessing the corporate network, reduces broadcast traffic, and simplifies firewall rules.
Uplink capacity: 8 × 4 Mbps streams = ~32 Mbps minimum. A Gigabit uplink from switch to compute provides more than adequate headroom. Avoid 100 Mbps uplinks if you plan to record at higher bitrates or add cameras later.
Compute-to-router link: The edge compute node should connect to the router/firewall on a management VLAN separate from the camera VLAN. This keeps inference traffic local and only forwards alerts or metadata upstream.

Use the Network Bandwidth Tool to validate bandwidth for your cameras and codec settings. See Edge AI Networking: VLANs, PoE, and Bandwidth Math for a full walkthrough.

Deployment Checklist (Day 0 → Day 2)

Day 0 — Hardware: Verify all PoE ports negotiate at expected wattage using switch management interface
Day 0 — Hardware: Label all cables with port assignments before closing enclosure
Day 0 — Hardware: Confirm UPS powers on cleanly and compute node performs a clean shutdown on simulated power loss
Day 0 — Software: Update OS, JetPack/driver stack, and all inference dependencies before going live
Day 0 — Software: Configure camera VLAN and verify cameras cannot reach the internet directly
Day 0 — Software: Set up SSH key access; disable password auth
Day 1 — Burn-in: Run inference pipeline at full load for 24–48 hours; monitor CPU/GPU temperature under sustained workload
Day 1 — Burn-in: Verify ring buffer is rotating correctly and storage usage stabilizes at expected level
Day 1 — Burn-in: Confirm all camera streams are available after a simulated power outage and restore
Day 2 — Operations: Set up monitoring for CPU/GPU temps, disk usage, and inference latency (Prometheus, Grafana, or similar)
Day 2 — Operations: Enable automated OS security updates or schedule regular update windows
Day 2 — Operations: Document firmware versions, IP addresses, and hardware serial numbers
Day 2 — Operations: Configure log rotation to prevent log writes from consuming ring buffer storage
Day 2 — Operations: Test remote access (VPN or jump host) from an off-site location before declaring production-ready

Hardware builds overview: For a structured comparison of starter, balanced, and industrial configurations, see Recommended Edge AI Builds (2026).

How to Use This Blueprint in a Real Deployment

Confirm actual camera watt draw and bitrate: Measure or obtain from camera datasheets. H.264 at 1080p/15fps typically runs 3–5 Mbps; H.265 typically runs 1.5–3 Mbps. Plan for the higher bitrate if cameras auto-adjust.
Size PoE budget with headroom: Use the Power Budget Planner to calculate total load (cameras + switch) and select a switch with 25–30% headroom above measured requirements.
Size retention and SSD endurance: Calculate daily writes based on your bitrate and use the Storage Endurance Tool to estimate drive lifespan. Plan replacement based on calculated TBW consumption and site maintenance windows; many 24/7 deployments target roughly 3–5 years.
Validate VLAN and uplink design: Use the Network Bandwidth Tool to confirm Gigabit uplink capacity. Verify switch VLAN support. Test inter-VLAN routing and camera isolation in a lab before deployment.
Run 24–48 hour burn-in and power-loss recovery test: Before declaring the system production-ready, run continuous inference at full load and simulate a power failure. Verify graceful shutdown completes, storage integrity is maintained, and all streams resume cleanly. Use the Full Deployment Planner to validate the complete stack sizing before burn-in.

Variants

Budget variant

Cameras: 1080p PoE (802.3af, ~6–8W), no PTZ
Switch: Unmanaged or basic managed PoE+, 120W total budget
Compute: Jetson Orin Nano 4GB or entry x86 mini PC (no dedicated NPU)
Storage: 1–2 TB consumer NVMe (verify TBW ≥ 360 TBW for 3-year margin)
UPS: 750 VA line-interactive, basic USB management
Tradeoff: Lower inference throughput, less visibility into PoE faults, shorter drive life at high bitrates

Balanced variant

Cameras: 4MP PoE+ (802.3at, 10–12W), optional IR
Switch: Managed PoE+ with VLAN support, 150–180W total budget, Gigabit uplink
Compute: Jetson Orin NX 16GB or Orin Nano 8GB
Storage: 2 TB NVMe (≥600 TBW) + 6 TB NAS-rated HDD for archive
UPS: 1000 VA pure sine wave, NUT or SNMP management
Tradeoff: Good balance of cost, inference headroom, and operational visibility

Industrial variant

Cameras: 4MP–8MP, IP67-rated, PoE++ capable, wide operating temp range
Switch: DIN-rail industrial managed PoE, −40°C to 75°C rated, 250W+ budget
Compute: AGX Orin or ruggedized x86 platform with redundant storage
Storage: Industrial NVMe with pSLC NAND (≥1200 TBW), RAID-1 or mirrored NAS
UPS: 1500 VA pure sine wave with extended battery module, SNMP managed
Tradeoff: Significantly higher cost; justified for 24/7 outdoor or factory deployments with multi-year SLAs

Frequently Asked Questions

How much PoE budget do 8 cameras really need?

8 cameras at typical 10–12W each draw 80–96W. Add ~10W for switch overhead. A recommended budget is 150–180W. Always verify per-port limits (typically 15W–30W) do not exceed total budget, which is often lower than the sum of per-port ratings.

Is Gigabit enough for 8 cameras?

Yes. 8 cameras at 4 Mbps each = ~32 Mbps total. A Gigabit link provides 900+ Mbps usable capacity, giving plenty of headroom for protocol overhead, uplink traffic, and future expansion.

Should I keep all footage on NVMe?

Keep 3–7 days of footage on NVMe (2 TB, ~600 TBW) and archive older clips to a NAS-rated HDD. This balances fast local inference access, SSD endurance, and long-term retention. NAS drives survive power cycles better and handle archive workloads.

How much UPS runtime is enough?

5–10 minutes allows graceful shutdown with NUT automation. A properly configured shutdown sequence flushes buffered video to disk and stops cleanly, preventing filesystem corruption. Avoid counting on runtime for extended operation.

Can one Jetson handle all 8 streams?

A Jetson Orin NX (40 TOPS) or Orin Nano 8GB (40 TOPS) can run 8 streams at 1080p with typical object detection models. For higher-resolution or more complex models, step up to Jetson AGX Orin (275 TOPS). Always validate inference latency under load during burn-in.

What if my site has sporadic power?

A UPS with NUT automation and graceful shutdown is essential. UPS protects during outages; graceful shutdown prevents filesystem corruption. Without both, edge nodes are vulnerable to data loss and pipeline crashes. Consider a larger battery if outages are frequent.

The Bottom Line

A successful 8-camera edge deployment is not just about selecting the right compute hardware. It is a coordinated design across PoE budget, storage endurance, VLAN isolation, UPS protection, and burn-in validation. Size the entire stack together using tools like the Power Budget Planner and Full Deployment Planner, run at least 24–48 hours of burn-in at full load, and lock down the configuration before declaring the system production-ready. Small oversights in any layer — undersized PoE budget, consumer-grade SSD, missing UPS automation, or skipped VLAN isolation — will cause expensive failures in the field.