Own the operating boundary.
Connect only what you intend.

Run the complete web-operated VMS on Windows or Linux, keep recording close to the cameras, and add private-cloud or cross-site coordination where the workload calls for it.

Choose by operating model, not by buzzword.

Each shape changes where services run, who operates them and how sites trust one another. Media and scale are qualified against the real camera estate.

One site, one local operating plane.

Package cameras, media services, storage and the web console inside a single customer-controlled site. A practical fit for a single facility or a deliberately compact installation.

Local operation without a cloud dependency
Windows or Linux server/web stack
Focused Windows-native viewers available

Separate service roles inside your network.

Place API, streaming, recording, monitoring, PostgreSQL and storage roles on infrastructure governed by your organization. Use the web console as the primary operations surface.

Customer-specific network and identity boundary
Linux web + services or Windows web + services
Service and storage placement planned per workload

Connect independent sites through explicit trust.

Keep local recording and credentials at each site while granting exact resources to trusted peers. Federation is site-to-site coordination—not a shared, anonymous media plane.

Explicit site trust and revocation
Exact resource delegation
Server-held connection credentials

Coordinate qualified sites from a central view.

Create a customer-specific monitoring tier for site health, events and authorized resources across multiple locations. Remote media paths, resilience and capacity are qualified before rollout.

Multi-site operational visibility
Local media continuity at connected sites
Architecture and failover scoped per program

Full web operations on both server platforms.

Native viewing stays intentionally Windows-specific. The web console is the primary operations and administration interface everywhere.

Windows: web, focused native viewers and services

Install the backend and media services, operate through the web, and use dedicated Live Grid and Video Wall clients where direct native rendering is required.

Linux: web and complete server stack

Run API, streaming, recording, monitoring, media/event services, PostgreSQL and FFmpeg as a full web-operated VMS.

Camera count alone is not a sizing model.

Codec, resolution, frame rate, recording policy, retention, concurrent live walls, storage throughput and network shape all change the deployment.

Camera and codec mixRetention and schedulesConcurrent live viewsStorage throughputSite connectivityRecovery objectives

Show us the sites and the retention target.

We’ll turn them into a deployment boundary, role placement and qualification plan.

Plan the deployment

Own the operating boundary.Connect only what you intend.