Synology Surveillance Station: Complete 2026 Guide

Synology surveillance platform

Synology Surveillance Station: Complete 2026 Guide

Surveillance Station can turn a compatible Synology NAS or DVA appliance into a local video management system, but a dependable deployment is more than installing the package. Camera protocol support, device licenses, aggregate bitrate, retention, storage redundancy, remote access, notification paths and recovery all affect whether the system remains useful when something goes wrong. This guide treats those layers separately and gives you a planning tool before you buy cameras or drives.

Quick answer

Start with cameras, bitrate, retention and recovery

For most homes and small businesses, a current Plus-series DiskStation can run Surveillance Station while also serving normal NAS workloads. Dedicated DVA appliances become more compelling when deep video analytics, local HDMI monitoring or a surveillance-first operating model is central to the project. Always verify the exact camera count and stream profile with Synology’s current NVR Selector.

Live Amazon products

Hardware and licenses relevant to this surveillance decision

This Sprint 9G catalogue tracks the Synology NAS, DVA appliances, cameras, license packs and selected Reolink examples used by these pages. Surveillance hard-drive cards are read from Cloudzat Storage Price Intelligence in read-only mode. Product cards support planning but never override Synology's live compatibility list, NVR Selector, license rules or camera firmware requirements.

Checking the dedicated Synology surveillance catalogue…

Technical decision

Choose the architecture before choosing the drive size

A good surveillance design starts with the number and type of cameras, the bitrate actually configured, how many hours are recorded each day, the retention target, whether edge or server-side analytics are required, and what happens if the NAS is unavailable. Those inputs determine the server, licenses, storage capacity and network design much more accurately than simply asking which Synology NAS is “best.”

Interactive surveillance tool

Surveillance Station System Planner

Use this as a planning aid. It applies the inputs you provide, but final camera limits, compatibility, licensing, package behavior and cloud plan details must be checked against Synology's current documentation and the exact hardware/firmware in use.

Deployment checklist

Four checks before a surveillance rollout

Prove the camera path

Verify the exact model, firmware and protocol in Synology Camera Support before buying or rolling out a large fleet.

Calculate licenses

Count actual device channels, multi-lens streams and special devices, then subtract only the licenses included with the chosen recorder.

Size by bitrate

Use configured Mbps, recording hours and retention days. Resolution alone is not a reliable surveillance-storage number.

Test recovery

After setup or upgrade, verify new recordings, playback, notifications, remote access and the procedure for retrieving critical footage.

01

What Surveillance Station actually does

Surveillance Station is the VMS layer for live view, recording, playback, camera management, events, users and multi-site workflows on supported Synology systems. Define which of those functions must continue during maintenance and which can tolerate a short outage.

What Surveillance Station actually does: Define which of those functions must continue during maintenance and which can tolerate a short outage. Surveillance Station is the VMS layer for live view, recording, playback, camera management, events, users and multi-site workflows on supported Synology systems.

02

Camera support comes before camera count

A camera can be reachable on the network yet still lack native feature support, so Synology’s support list and ONVIF profile matter before scaling a deployment. Test one representative camera with the exact firmware, audio, codec, PTZ and event features you intend to use.

Camera support comes before camera count: Test one representative camera with the exact firmware, audio, codec, PTZ and event features you intend to use. A camera can be reachable on the network yet still lack native feature support, so Synology’s support list and ONVIF profile matter before scaling a deployment.

03

Licenses are part of system cost

Most cameras and supported surveillance devices consume device licenses, while some multi-channel devices and transaction devices can consume more than one. Count required device channels, subtract the licenses included with the chosen Synology server, then price only the additional packs needed.

Licenses are part of system cost: Count required device channels, subtract the licenses included with the chosen Synology server, then price only the additional packs needed. Most cameras and supported surveillance devices consume device licenses, while some multi-channel devices and transaction devices can consume more than one.

04

Bitrate drives storage more than resolution labels

Two 4K cameras can consume very different storage if codec, frame rate, scene complexity and bitrate controls differ. Use measured or configured Mbps per camera when estimating retention instead of assuming every camera at one resolution produces the same daily data.

Bitrate drives storage more than resolution labels: Use measured or configured Mbps per camera when estimating retention instead of assuming every camera at one resolution produces the same daily data. Two 4K cameras can consume very different storage if codec, frame rate, scene complexity and bitrate controls differ.

05

Retention policy changes the disk plan

Continuous recording for thirty or ninety days is a different storage problem from event-only recording even with the same cameras. Write the retention objective first, then calculate raw recording capacity plus operational headroom and RAID or SHR redundancy.

Retention policy changes the disk plan: Write the retention objective first, then calculate raw recording capacity plus operational headroom and RAID or SHR redundancy. Continuous recording for thirty or ninety days is a different storage problem from event-only recording even with the same cameras.

06

NAS models and DVA models serve different priorities

Plus-series DiskStations combine surveillance with general NAS services, while DVA appliances add dedicated deep-learning analytics capacity and more included device licenses. Choose DVA when server-side analytics are a requirement, not merely because the model name sounds more surveillance focused.

NAS models and DVA models serve different priorities: Choose DVA when server-side analytics are a requirement, not merely because the model name sounds more surveillance focused. Plus-series DiskStations combine surveillance with general NAS services, while DVA appliances add dedicated deep-learning analytics capacity and more included device licenses.

07

Networking must handle aggregate streams

Camera traffic is continuous and predictable enough to calculate, but live views, remote playback and backups can add bursts on top of recording. Keep cameras on reliable wired links where practical, calculate aggregate ingress, and leave margin for management and playback traffic.

Networking must handle aggregate streams: Keep cameras on reliable wired links where practical, calculate aggregate ingress, and leave margin for management and playback traffic. Camera traffic is continuous and predictable enough to calculate, but live views, remote playback and backups can add bursts on top of recording.

08

Recording storage should be treated as operational data

Surveillance disks see sustained write activity and retention rotation rather than the bursty pattern of ordinary file storage. Use drives suited to the workload, monitor temperature and health, and replace warning drives before the array loses more redundancy.

Recording storage should be treated as operational data: Use drives suited to the workload, monitor temperature and health, and replace warning drives before the array loses more redundancy. Surveillance disks see sustained write activity and retention rotation rather than the bursty pattern of ordinary file storage.

09

Remote access needs a threat model

Remote viewing is useful, but exposing management services casually can turn a convenience feature into an avoidable security risk. Prefer supported secure access methods, strong authentication and least-privilege user roles instead of direct broad port exposure.

Remote access needs a threat model: Prefer supported secure access methods, strong authentication and least-privilege user roles instead of direct broad port exposure. Remote viewing is useful, but exposing management services casually can turn a convenience feature into an avoidable security risk.

10

Notifications need testing, not assumptions

A motion rule or health alert is only valuable if the right person receives it and understands what action is required. Generate test events after configuration changes and periodically verify push, email or webhook paths from camera to operator.

Notifications need testing, not assumptions: Generate test events after configuration changes and periodically verify push, email or webhook paths from camera to operator. A motion rule or health alert is only valuable if the right person receives it and understands what action is required.

11

Backups protect configuration and critical evidence

RAID keeps recording online after some disk failures, but it does not create an independent copy of footage that must survive theft, deletion or array loss. Identify which recordings truly require off-system retention and back up those events or archives according to legal and business needs.

Backups protect configuration and critical evidence: Identify which recordings truly require off-system retention and back up those events or archives according to legal and business needs. RAID keeps recording online after some disk failures, but it does not create an independent copy of footage that must survive theft, deletion or array loss.

12

Scale by proving one repeatable camera pattern

Large camera deployments fail when a single untested camera template is copied across dozens of endpoints with hidden codec or feature differences. Prove one camera model and one recording profile, document it, then expand in controlled batches while watching bandwidth and storage growth.

Scale by proving one repeatable camera pattern: Prove one camera model and one recording profile, document it, then expand in controlled batches while watching bandwidth and storage growth. Large camera deployments fail when a single untested camera template is copied across dozens of endpoints with hidden codec or feature differences.

Questions people ask

Surveillance Station questions

Is Synology Surveillance Station free?

The Surveillance Station package can be installed on supported Synology systems, but camera/device capacity is governed by included and purchased surveillance device licenses.

How many cameras can Synology Surveillance Station handle?

The supported count depends on the exact NAS or NVR model and the resolution, codec, frame rate and bitrate profile, so use the current Synology NVR Selector.

Does Surveillance Station work without the internet?

Local camera recording and management can operate on the local network, while remote services, notifications, updates or license activation may require internet access depending on the workflow.

Can I use non-Synology cameras?

Yes, Synology supports a very large camera catalogue and ONVIF devices, but the exact feature set varies by camera model and integration method.

Do Synology cameras need licenses in Surveillance Station?

Current Synology camera documentation lists a Surveillance Device License as required when the camera is used with Surveillance Station.

Should I use a DiskStation or DVA appliance?

Use a DiskStation when general NAS services and recording share one box; consider DVA when deep video analytics or surveillance-first operation is a primary requirement.

How much storage does surveillance need?

Storage depends on cameras, bitrate, recording hours, retention days and event percentage, not resolution alone.

Is RAID a surveillance backup?

No. RAID and SHR are availability mechanisms; evidence that must survive total system loss needs a separate protected copy.

Can I mix camera brands?

Yes when each device is supported through a suitable native, ONVIF or RTSP path, though feature consistency can vary across brands.

What should I test after setup?

Test live view, continuous/event recording, playback, alerts, remote access, retention rotation and a representative recovery procedure.

Official references and methodology

Verify the exact camera, recorder, package build and licensing state

Cloudzat treats Synology’s current product specifications, Surveillance Station release notes, compatibility list and NVR Selector as the authority for camera limits and feature support. The calculator uses bitrate arithmetic as a planning estimate and intentionally adds headroom rather than claiming a vendor-certified capacity.

As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, camera firmware, product availability, license rules, Surveillance Station behavior and cloud-service plans can change. Verify the exact Synology model, camera support entry, package release notes and current service terms before purchasing hardware or changing a production surveillance system.

Scroll to Top