Estimates only — actual figures vary by camera, scene, and firmware.
Required = raw recording data (server sizing); Total = + RAID + headroom (HDD procurement).
Validate against camera specs before deployment.
OPTIONS
PROJECT SETTINGS
Recording, management and database all run on a single server. Best for single sites.
Operators viewing live/reports at peak. Drives app-tier RAM + CPU sizing. 0 = unknown.
Per-server capacity is benchmark-based — newer CPUs / multi-instance archiving allow
more cameras/server. Contact LENSEC for current figures.
~20% extra on H.265 streams (≈50% total vs H.264). AV1 already efficient; H.264 unaffected.
1 secondary per site — reduced spec (~50% compute), records ALL cameras for the failover window.
%
Storage only — extra space on top of RAID for future growth. Doesn't affect camera capacity.
Distributed Mode: Sizing below covers video streaming and storage only.
For deployments involving 3rd-party integrations (access control, POS, analytics engines),
contact LENSEC for a complete system design.
CAMERA GROUP CONFIGURATION
Edit mode — modifying row .
Click Update to save.
Above the measured data ceiling (16MP) — bitrate/storage extrapolated by megapixel count. Budgetary estimate; confirm against the camera datasheet.
15
Extrapolated — measured table data available up to 30 fps
AUTO
Peak (nominal): — Mbps |
—
High-motion scenes (crowds, traffic, PTZ) can exceed this — raise the bitrate for busy sites.
High-activity scene: VBR cameras may spike 40–60% above the nominal bitrate during peak events. Validate actual bitrate with your camera manufacturer.
VIDEO ANALYTICS (OPTIONAL)
Budgetary estimate only. Analytics capacities are generic LENSEC estimates —
not vendor-validated specs. Each engine (Rekor, Innovatrics, Vaidio, TechnoAware, …)
publishes its own server requirements: always confirm with the vendor's datasheet before quoting.
INTEGRATIONS (OPTIONAL)
Access control, fire, intrusion or BMS integrations → SMOC.
Integrations also grow the SQL event database.
Licensing & Edition (optional)
Pick the capabilities this project needs — refines the edition recommendation below.
RECOMMENDED SOLUTION
Total Cameras
0
0 groups
Total Storage (for HDD buy)
0 GB
Recording Throughput
0 Mbps
Switch / Backbone
— Mbps
recording + viewing + 10% mgmt
CAMERA GROUPS
#
Group Name
QTY
Resolution
Codec
Quality
FPS
Scene Type
Activity
Bitrate (peak)
Retention
Storage
Throughput
Actions
No camera groups added yet. Configure a group and click Add.
SERVER REQUIREMENTS
Camera count warning
Hardware-agnostic — compatible with any server brand
External storage: recording server sized for compute only. Effective throughput derated by 20% (NAS overhead). Requires 10 GbE NIC minimum.
Calculating recommendation…
Distributed Deployment — 2 server types required:
① Management Server + ② Recording Server(s)
① MANAGEMENT SERVER
(1 required — application tier & database, no video storage)
② RECORDING SERVER(S)
Reference Only — Lensec OEM models shown for convenience. Any server meeting the requirements above is compatible.
FAILOVER SIZING
Export Sizing Report
Licensing — Select Features
Optional. Tick the capabilities this project needs and we'll
recommend the correct edition. Cameras, integrations, analytics and failover are already taken from
your inputs in the tool — these toggles add the licensing-only capabilities.