Blue Iris infrastructure cornerstone
Blue Iris Surveillance System Calculator: Storage, PoE & UPS
A complete Blue Iris system is a chain: cameras need network ports and power, streams need uplink bandwidth, recordings need sustained storage, evidence needs a recovery path, and the recorder plus switch need protected power. This calculator brings those dependencies into one plan so the infrastructure is sized together instead of as unrelated purchases.
Quick answer
Size the path from camera to disk to backup
Enter the camera workload, recording policy, PoE watts, network viewers, backup target and protected power load. The result identifies the storage, switch, Ethernet and UPS classes that deserve attention.
Live Amazon infrastructure
Current hardware for this Blue Iris decision
Sprint 7B owns PoE switch, PCIe NIC, UPS, DAS and NAS classes. Surveillance HDD cards are read from Sprint 7A without writing to its catalogue, so Blue Iris recording drives are not duplicated. Accessory-only, USB-NIC, replacement-battery and wrong-product listings are rejected.
Buying decision
Fix the narrowest failure path before adding faster hardware
A powerful recorder cannot compensate for an undersized PoE budget, saturated switch uplink, full recording disk or unprotected camera power. Use the result as a checklist for the whole surveillance path.
Interactive decision tool
Blue Iris Surveillance Infrastructure Calculator
Use measured camera bitrate, equipment watts and the retention policy you actually need. The tools use direct unit conversion and planning headroom; they do not invent camera throughput, PoE draw, disk speed or UPS runtime. Verify exact product specifications before purchase.
Compatibility checklist
Four checks before buying surveillance infrastructure
Measure streams instead of guessing
Use actual camera Mbps for storage and network planning. Resolution and codec labels alone do not determine bytes written or link utilization.
Count PoE ports and watts separately
A switch needs enough powered ports and enough total power budget. Night IR, heaters and PTZ movement can change the worst-case load.
Do not convert VA directly into runtime
UPS runtime depends on the exact battery system and connected watts. Use manufacturer runtime data after the protected load is calculated.
Backup must survive a different failure
A second copy is useful when it has an independent retention and recovery path. RAID or another folder on the same recorder is not the same protection goal.
Camera streams define both storage and network baselines
The same measured bitrate drives two different infrastructure calculations. On the network side, every live stream contributes to recorder ingress. On the storage side, only the fraction actually recorded contributes to disk growth. Keeping those formulas separate prevents event recording from being mistaken for lower camera-network load.
Retention converts continuous traffic into a capacity requirement
Once aggregate recorded Mbps is known, direct unit conversion produces daily terabytes. Multiply by retention days and add the chosen free-space reserve. The result is a planning capacity rather than a promise of exact usable disk space, because formatting, filesystem behavior and real camera bitrate variation still have to be accommodated.
PoE ports and PoE watts are separate constraints
The switch must have enough powered ports for the cameras and enough total power budget for their maximum draw. The calculator adds camera watts and recommends a port class with spare capacity. It does not infer watts from camera resolution or claim a switch budget unless the exact product listing provides evidence.
The switch uplink should be sized from aggregate traffic
Dozens of low-speed camera ports can converge on a much busier uplink. Compare camera ingress plus viewer traffic with the speed of the shared link from camera switch to recorder. If that link is the bottleneck, replacing only the recorder NIC will not create additional end-to-end capacity.
Recorder Ethernet tier should include export and backup bursts
A Blue Iris system can fit ordinary recording inside 1GbE while still benefiting from 2.5GbE or 10GbE during large exports and NAS backups. The calculator therefore separates steady camera traffic from secondary transfer requirements. Choose the network tier that supports the busiest routine workflow, not the most impressive adapter specification.
Recording storage and backup storage serve different recovery goals
Primary surveillance HDDs retain footage for fast search, while DAS or NAS copies can preserve selected evidence or recorder state. A second device should have an independent retention policy if the goal is recovery. Simply copying the rolling archive with the same deletion behavior may not preserve an incident that is discovered later.
UPS sizing begins with the protected watt load
Add the recorder, switch electronics, camera PoE power and any router or ONT that must remain available. The tool calculates a watt target with headroom and the battery watt-hours that would theoretically support the requested runtime. Exact UPS runtime must then be checked against the selected model's manufacturer data.
Distributed camera switches need distributed reliability planning
A remote switch in a garage or another floor may lose power even when the central recorder rack remains on battery. Map each switch, its uplink and its power source. High-priority cameras can be placed on protected switches while lower-priority areas use shorter runtime, reducing battery cost without pretending every camera has identical availability requirements.
Managed networking can make surveillance faults easier to isolate
Per-port statistics, VLANs and PoE controls are valuable once the system has enough cameras that unplugging cables is no longer a practical diagnostic method. Management does not replace good documentation, but it can show link state, errors and power behavior remotely. Verify the exact feature set on the switch rather than assuming every managed label includes the same tools.
Chassis bays, PCIe slots and cooling connect the infrastructure layers
A storage or network recommendation can be impossible if the Blue Iris PC lacks the physical expansion space. Check the number of 3.5-inch bays, PCIe lanes, slot height, power connectors and airflow before purchasing additional HDDs or 10GbE NICs. The recorder platform from Sprint 7A and this infrastructure sprint should be evaluated as one machine.
Growth planning should use the expected final camera count
A surveillance system often expands after the first successful installation. Size switch ports, uplinks, storage bays and UPS headroom for the plausible final estate, while still buying only the capacity that makes economic sense today. Planning expansion paths early prevents a small initial switch or sealed chassis from forcing a premature platform replacement.
Commission the system with failure tests and measurements
After installation, measure daily storage growth, peak NIC utilization, PoE consumption and protected UPS load. Simulate a controlled power interruption, restore a configuration backup and open selected footage from the secondary target. Those tests validate the assumptions made by the calculators and reveal weak links that product specifications alone cannot show.
Questions people ask
Blue Iris Surveillance System Calculator FAQs
What does the Blue Iris surveillance system calculator size?
It combines recording capacity, PoE ports and watts, network tier, backup capacity and UPS protected load into one infrastructure plan.
Does it choose a Blue Iris CPU or GPU?
Sprint 7A handles recorder compute sizing. Sprint 7B focuses on storage, networking, power and recovery around that recorder.
Can one gigabit handle my cameras?
Possibly. The calculator uses the entered camera bitrates and viewers to estimate aggregate network demand before recommending a faster tier.
How does it size PoE?
It counts powered cameras and multiplies the entered maximum watts per camera, then adds port and power headroom.
How does it calculate storage?
It converts aggregate recorded Mbps into TB per day, multiplies by retention and adds the selected reserve.
Does it calculate exact UPS runtime?
No. It calculates protected watts and battery-energy requirements. Exact runtime must come from the chosen UPS model and manufacturer data.
Does the backup target need to match primary capacity?
Only if the policy requires a full duplicate archive. Selected evidence and configuration backup can require far less capacity.
Should the PoE switch and recorder share one UPS?
They can, but distributed switches may need separate local protection. Size each protected failure domain intentionally.
Why are surveillance HDDs reused from Sprint 7A?
The 7B plugin reads accepted 7A surveillance HDD records without writing to that table, avoiding a duplicate hard-drive catalogue.
What should I verify after installing the system?
Measure real bitrates, storage growth, network utilization, PoE draw, UPS load and backup restoration, then update the plan with observed values.
Official references and methodology
Verify the exact Blue Iris and infrastructure behavior
The cornerstone combines direct storage and bandwidth math with user-entered power data. It does not invent CPU throughput, PoE draw or UPS runtime. Hardware cards come from the dedicated 7B catalogue plus read-only 7A surveillance HDD data when available.
- Blue Iris official site and system requirements
- Blue Iris official Version 6 updates
- TP-Link official PoE switch portfolio
- CyberPower official UPS runtime calculator
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, switch power budgets, NIC revisions, UPS battery behavior, enclosure bundles and marketplace conditions can change. Verify the exact model before purchase.