Security and fit

Use this page to decide whether a public RTSP rollout should move forward at all, not just whether the stream technically plays.

The main security question is not browser compatibility. It is whether a publicly reachable RTSP flow matches the security posture, operating model, and ownership model of the rollout you are about to launch.

Answer these before you approve the rollout

  • Should this camera or stream really be reachable from the public internet?
  • Are camera credentials reviewed and no longer left on default values?
  • Are you looking for browser playback and embed, rather than an internal surveillance system?
See if public RTSP fits Support and what to expect

Move forward when

  • Public camera pages, company websites, storefronts, event pages, and similar browser-facing scenarios.
  • Fast validation of a public RTSP/RTSPS stream before publishing it.
  • Simple embed use cases where you need browser playback without building your own player.

Stop or redesign when

  • Internal-only CCTV environments that should not expose RTSP to the internet.
  • Deployments that require recording, retention, user management, or advanced monitoring.
  • Scenarios where opening camera access publicly is not acceptable.

What the decision-maker actually needs to know

  • If making the stream publicly reachable is a hard no, the default RTSP.RUN flow is the wrong fit.
  • If you need a safer pre-check before trying the product, use the fit-check contact path instead of forcing a rollout.
  • If you need recording, analytics, or internal CCTV governance, evaluate a different class of product.