Free Sizing Tools
Size it before you buy it
Two calculators built from the sizing work we do on real deployments — surveillance storage retention and RAID usable capacity. No sign-up, nothing emailed to you, the arithmetic is shown.
NVR Storage & Retention Calculator
How much storage a camera estate needs, or how many days a given array will hold. Then the chassis, drive count, drive size, bandwidth and NIC that actually carry it.
- Six resolutions, four codecs, motion-recording duty cycle
- RAID 5 and RAID 6 sized side by side, 8 to 60 bays
- Flags an array that fits on capacity but not on throughput
RAID Capacity Planner
Usable capacity for RAID 1, 5, 6, 10 and ZFS RAIDZ1/Z2/Z3 — what the drives are labelled, what the operating system will report, and what the filesystem takes off the top.
- Seven RAID levels including the ZFS parity variants
- Decimal TB against binary TiB, shown side by side
- Per-filesystem overhead for ext3/4, XFS, NTFS, ReFS and ZFS
GPU & AI Server Sizing Calculator
What an AI workload actually needs: VRAM, GPU count, system RAM and NVMe, from the model size, precision, concurrent users and the context they need.
- Chat, coding, reasoning, RAG, agents, vision and fine-tuning
- KV cache sized properly — usually the term that decides the answer
- Every step of the arithmetic shown, with adjustable headroom
Video Analytics GPU Sizing
How many GPUs a camera estate's analytics needs — stream density by detector, resolution and frame rate, capped to what a chassis holds.
- Object, people, LPR/ANPR, behaviour, crowd and transformer detectors
- Density anchored on NVIDIA's published VSS benchmarks
- Scales by adding servers, never by overfilling a box
Face Recognition GPU Sizing
Both stages sized separately: extraction against new faces per second, matching against a 10K to 10M enrolled database — the larger one is the answer.
- Recognition sized per face, not per frame — the usual over-sizing error
- Matching cost scaled by enrolled database size
- Names which stage is binding, because the remedy differs
VM Density & Host Sizing
Enter your virtual machines row by row. Get the host count, their shape, the failover capacity N+1 really needs, and what HA requires from network and storage.
- Unlimited rows — a real heterogeneous estate, not an average VM
- CPU overcommit 1:1 to 1:3; memory always 1:1, never overcommitted
- Names whether CPU or memory is the binding ceiling
Both run entirely in your browser. Nothing you type is sent to us, and there is no sign-up — if the numbers are useful, they are useful whether or not you ever talk to us.