Planning your installation

Start with one camera, live video and recording. Add more devices, AI and remote storage once that works, so you can identify which change causes a problem.

Choose an installation method

Your environment	Installation	Check first
Always-on Linux host or NAS	Native program or Docker	CPU architecture, writable data directory and free disk space
Windows PC	Native program	Private-network firewall access; disable automatic sleep for continuous operation
Mac	Native program	Choose Apple silicon or Intel; AI needs Apple silicon and macOS 14+
Linux ARM64 board	ARM64 native program	AI needs glibc 2.34+; video decoding uses the CPU, so measure one camera first

See Install Rerinku View for packages, startup and automatic startup. FFmpeg and recognition components on supported platforms ship with the program. The Docker image currently supports amd64.

Prepare one camera

• Have its LAN IP, username and password ready. Camera credentials are managed separately from your Rerinku Cloud account.
• Prefer ONVIF when available for multiple streams and PTZ. Add a camera manually if it only has an RTSP URL.
• Test browser playback with H.264 first. H.265 needs browser support; MJPEG needs transcoding on Rerinku View.
• USB cameras require Linux and H.264, H.265 or MJPEG output.

See Connecting cameras for GB28181, SDK devices and phone cameras.

Plan recording storage

The default recording limit is 100 GiB, with at least 2 GiB left free. Rerinku View removes the oldest footage according to the retention policy. These settings do not guarantee a fixed number of days.

Estimate continuous video at bitrate in Mbps × 10.8 GB per camera per day. A 4 Mbps stream needs about 43.2 GB a day; four streams for seven days need about 1.21 TB, plus audio, previews and free space. This assumes a sustained bitrate; actual use depends on the camera. GB here is decimal; GiB in the settings is binary.

Check the disk mount and the service user’s write permissions. Persist /data in Docker. Remote storage still needs local disk to receive footage first; see Recording and playback.

Check the network

Connection	Purpose	Check
Browser or phone → Rerinku View	Console and playback	Host port 8080/TCP is reachable
Rerinku View → camera	Connect and receive streams	Correct IP, protocol ports and camera credentials
LAN ONVIF devices ↔ Rerinku View	Discovery	Same subnet, multicast and UDP 3702 replies; otherwise add manually
Browser ↔ Rerinku View	WebRTC live video	The media connection is reachable as well as the web port

For SDK, GB28181 and WebRTC ports, see the Configuration reference. Test on your LAN before setting up Remote access.

Check AI requirements when needed

AI has stricter platform requirements than live video and recording. Hardware video decoding and model inference are separate jobs. Read AI recognition, start with one camera and check the measured performance in settings before adding more.

Continue to Install Rerinku View, or Quick start if it is already installed.