Questions, answered.

On site. SecureWatch records your cameras to storage at your location. When you watch remotely, the video is relayed from that site. It isn’t a second copy of every frame stored in our cloud.

Yes. Recording happens locally, so it keeps going during an internet interruption. Remote playback for that site resumes when the connection comes back, and the local admin is still available on site.

Yes. When your site is connected, you can review its footage remotely through SecureWatch. The connection is encrypted and started by your site, so you don’t open a video port on your firewall.

Yes. Each location runs its own copy of SecureWatch, and you reach all of them from one place. The Team plan covers up to 3 locations and the Business plan covers unlimited locations.

Request early access with a few details about your cameras and locations. SecureWatch isn’t generally available yet, so we’ll email you when it opens, recommend a plan and walk you through setup.

Your network (IP) cameras, plus a computer at each location to run SecureWatch. It needs to reach your cameras, have storage for footage, and have an outbound internet connection for remote playback. We’ll share sizing guidance when you get access.

No. Recording happens on the SecureWatch recorder at your site, and that is where your footage lives. The SecureWatch cloud relays playback when you want to watch remotely.

By cameras and locations, not users. Starter covers 4 cameras at 1 location, Team covers 16 cameras across 3 locations and Business covers 64 cameras with unlimited locations.

Each location has its own local admin screen on site. The SecureWatch console is for reaching footage across locations; it doesn’t replace the local admin.

Not yet. Ask to be notified and we’ll reach out when the first release is ready.

No. It’s built for businesses that run their own network cameras at one or more locations.