Skip to content
Camzify
Guide

How to add sites and cameras

Everything in Camzify hangs off a site: a physical location that groups its cameras. This guide covers creating one, connecting cameras to it over RTSP or HTTPS, and confirming the stream works before anything is built on top of it.

  1. 1

    Create the site first

    A site is a physical location that groups its cameras, a warehouse, a campus, a storefront. Create it with a name, address and an optional contact number before adding anything else. Getting sites right early matters more than it looks: site is the unit that access, reporting and notification filtering are all organized around later, so a fleet dumped into one site is hard to delegate afterwards.

  2. 2

    Add the camera and give it a name someone will recognize

    Add each camera against its site, name it, and set its resolution. Name it for the place rather than the hardware, "Loading Dock B" tells a guard reading an alert at 2am where to go, and "Cam 14" does not. The name follows the camera into patrol reports and alerts, so it is worth a moment.

  3. 3

    Choose the stream type

    HTTPS covers HLS and WebRTC sources, which play directly. RTSP covers camera URLs; a publicly reachable RTSP stream is pulled straight from its URL. RTMP is the third option, where the camera or encoder pushes to an ingest address that Camzify generates for it.

  4. 4

    For cameras on a local network, install the Connector

    If the camera sits behind a router or firewall with no public route, install the Camzify Connector on a Windows, macOS or Linux machine on that network. It makes an outbound connection and relays the stream, so no port has to be opened and the camera is never exposed to the internet. It carries PTZ control for those cameras too.

  5. 5

    Verify the stream before you depend on it

    Use Test Stream in the camera form, then check the tile in live streaming to confirm footage is actually flowing. Do this before building patrol sequences on the camera. A stream that authenticated once but drops is the failure that quietly empties a patrol report later.

The one thing worth deciding up front is how you split sites, because site is the unit that access control, reporting and alert filtering all use. Splitting a large building into two sites later means revisiting every sub-user’s access; doing it at setup costs nothing.

Next: run a patrol round on the cameras you just added, or read about the Camzify Connector and which cameras work.

FAQ

Frequently asked questions

No. A static IP or an existing public route lets an RTSP stream be pulled directly, which is the simplest case. Everything else goes through the Camzify Connector, which connects outward from inside your network, no port forwarding, no inbound firewall rule, and no static IP.

Yes. A site or camera can be edited after it is created, name, address, contact number, resolution and stream URL. Nothing about the initial setup is permanent, so it is better to get cameras connected and adjust the organization afterwards than to delay connecting them.

Framing and lighting matter more than pixel count. The practical test is whether a person reviewing the feed can identify a person or vehicle at the distance you care about, if they can, the detection models have enough to work with. A 4K camera pointed at a wide car park can be worse than a 1080p camera framed on the entrance.

It depends on the machine and the upload bandwidth available, since each camera consumes roughly 2 to 4 Mbps at standard resolution. Plan the bandwidth first, that is the constraint that bites, not the software.

Ready to patrol your site 24/7?

Book a 15-minute demo and see a live patrol run on your own cameras.

This site is being updated

We are rebuilding pages as you read this, so an image, a link or a section may look unfinished for a while. The product itself is unaffected. If something important is broken, tell us at the contact page and we will fix it.