SecureWatch — record on site. Replay when you need it.
Edge nodes keep continuous video where the cameras are. The cloud relays playback.
- Attach IP cameras to the site edge node as stream sources (including RTSP URLs).
- Licensed by how many cameras and sites you run.
- Continuous record on local disk; operators replay through the cloud relay.
Record on the edge. Replay through the cloud.
Continuous video stays on the site node. Operators reach it through the cloud relay. Plans are licensed by cameras and sites.
Edge nodes record on site
Cameras stream to a node at the site. Continuous record is written to local storage. A WAN outage does not stop the disk.
Cloud orchestrator relays playback
Operators review clips through the orchestrator. It relays from the node that holds the video — it is not a second copy of every frame.
Continuous record
Keep writing video on the edge while operators replay through the cloud when they need a clip. Caps follow cameras and sites on your plan.
Retention tiers
How long a site keeps video is a licensed tier, not a hope. Larger plans add retention on top of the free shape.
Keep recording if the WAN drops
Control and relay traffic are encrypted. The node dials out — you do not open a special inbound video port on the site firewall.
Keep working the site if the cloud is down
Each node has its own local admin. You can still work the site when the orchestrator is unreachable.
Updates from Rubix Hub
Published node updates are delivered through the Hub. You do not rebuild a fleet by hand for a routine upgrade.
Licensed by cameras and sites
Plans are sold in cameras and sites — not users or domains. Plan limits are cameras and sites — not seats.
One console, many sites
Reach every licensed site from the orchestrator without standing up a central NVR that ingest every camera.
Node-locked licences
A Hub license key is bound to the node ID. You receive an activation code first; the key exists after the node does.
Start small, grow the fleet
Start on the free shape for a single site. Raise camera and site caps when the fleet grows.
Support that knows the product
Sales and support are on this site. Paid plans include email support; the fleet plan is the recommended multi-site choice.
Edge record, then relayed playback
The disk is at the site. The cloud is how you reach it.
Deploy an edge node at the site
The node takes the camera streams and writes continuous record to local storage. Local admin stays on the node. Recording does not wait on the cloud.
The node dials the orchestrator
Control and relay use encrypted transport between node and orchestrator. You do not open a special video port on the site firewall.
Operators replay through the cloud
When someone needs a clip, the orchestrator relays playback from the node that holds it. Retention and camera/site caps follow the licensed plan.
Sites record. The orchestrator reaches them.
Each box is an edge node that records on site. The cloud in the middle relays playback when someone needs a clip.
warehouse-north
4 cameras · recording · local disk
yard-gate
2 cameras · recording · local disk
office-lobby
3 cameras · replay · local disk
Orchestrator
Relays playback · encrypted transport · Hub updates
Traffic between node and orchestrator is encrypted. Operators watch through the relay; they do not pull raw camera URLs across the WAN.
Keep the recording at the site
Video is written on the edge node. The cloud relays playback — it is not a vault holding every frame.
Encrypted control and relay
Node-to-orchestrator traffic is mutually authenticated TLS. The node dials out, so the site firewall does not open a video port.
The disk is at the site
Video is written on the edge node. A compromise of the orchestrator does not hand over the archive. Local admin stays on the node.
Node-locked licences
A Hub key is signed for one node ID. Nobody receives a key before the node exists. Re-activating the same node returns the same key.
Honest scope
This is not a consumer camera app and not a compliance certificate. It is encrypted transport, local record, and a relay you can describe to a reviewer.
A node at the site. An orchestrator in the cloud.
That is the whole topology. Plans cap cameras and sites, not abstract "users".
Edge node per site
One node takes the cameras at that site, writes continuous record, and keeps local admin on the node itself.
Cloud orchestrator
One orchestrator relays playback for every licensed site. Operators do not VPN to each NVR to review a clip.
Hub-published updates
Node software updates come from Rubix Hub. Routine upgrades do not need a truck roll.
Sites that need the recording more than the dashboard
A warehouse that cannot lose a shift
The node keeps recording when the WAN drops. Playback waits for the link. The archive does not.
A few sites, one operator
Cover a handful of cameras across a few sites. Replay is relayed. You do not stand up a separate NVR at each site to watch them.
A fleet that has to explain itself
Scale cameras and sites under one licence a reviewer can map to hardware. Encrypted transport, local admin on the node, archive on the edge.
Cameras and sites
Soft plan shape only — licensed by how many cameras and sites you run. Request access or notify us — interest capture only.
Starter
Four cameras, one site — continuous record and replay.
- Continuous record on the edge node
- Relayed playback through the orchestrator
- Encrypted control and relay
- Local admin on the node
- Four cameras · one site
- Community support
Team
Sixteen cameras, three sites — retention tiers and relayed playback.
- Everything in Starter
- Retention tiers
- Relayed playback across sites
- Sixteen cameras · three sites
- Signed updates via Rubix Hub
- Email support
Business
Sixty-four cameras, unlimited sites — the recommended fleet plan.
- Everything in Team
- Sixty-four cameras · unlimited sites
- Fleet-scale retention
- Priority support
- The recommended multi-site plan
Interest capture only — no Hub checkout on this site yet. Talk to sales.
Record on site. Replay when you need it.
Tell us cameras and sites. We follow up on activation — interest capture only while Hub commerce stays off.
Or email sales@secure-watch.io