Terms of use
This page describes the practical rules for using RTSP.RUN as a self-service browser player and embed utility for publicly reachable RTSP/RTSPS streams.
The point is to make the product boundary clear before a team starts assuming a broader operational model than RTSP.RUN is designed to support.
What you should confirm first
- Decide whether the camera or stream can be publicly exposed at all.
- Verify the camera credentials, public network reachability, and correctness of the RTSP/RTSPS address.
- Be clear that RTSP.RUN is for playback and embed, not for recording or CCTV management.
What the user is responsible for
- Deciding whether the camera or stream may be made public at all.
- Verifying camera credentials, network reachability, and the correctness of the RTSP/RTSPS address.
- Making sure the stream is intended for public browser playback or website embed.
What RTSP.RUN does not promise
- It does not promise that every camera, network, and rollout will fit this model.
- It does not promise recording, analytics, retention, or internal CCTV workflows.
- It does not promise that every rollout can be forced into this model just because a camera streams somewhere.