Requirements and limits

Use this page to decide early whether the rollout belongs in RTSP.RUN at all.

RTSP.RUN is intentionally narrow: public RTSP/RTSPS playback and website embed. The point here is to prevent teams from spending time on setup work that can never satisfy the real requirement.

Qualify the rollout before setup work

  • The stream must use `rtsp://` or `rtsps://`.
  • The camera or stream must be reachable from the internet, not only from a local LAN or vendor app.
  • Private/internal IP-only streams are not supported in the default public flow.
See if public RTSP fits Support and what to expect

Proceed when

  • You have a valid RTSP or RTSPS URL.
  • The stream is reachable from the public internet.
  • You need live playback in a browser or a simple website embed.

What usually means the rollout is not ready

  • The camera is visible in a local app, but not actually reachable from the internet.
  • The team wants a website embed, but nobody has validated the RTSP URL, public reachability, or port setup.
  • The use case quietly depends on recording, analytics, or internal-only access that RTSP.RUN does not provide.

If these limits break the use case

  • Do not force the default public flow into an internal CCTV use case.
  • Use the fit-check contact path if you need help deciding whether the product is worth pursuing.
  • Treat these limits as an early qualification step, not as a promise that every camera setup can be made to fit.