Your cameras, from anywhere. Your video, nowhere else.
openIVR Cloud makes a self-hosted NVR reachable from your phone or laptop without a fixed IP, port forwarding or VPN. The relay carries encrypted packets and stores none of them.
Works behind CGNAT, 4G/5G and double NAT. Nothing to open on your router.
Three steps, no network knowledge required
Install openIVR
Run the open-source NVR on your own hardware: a mini PC, a Raspberry Pi 5, a server. Your cameras and recordings stay there.
Create a site in the portal
Sign in to the portal, add a site and get a pairing code. It is valid for ten minutes and used once.
Paste the pairing code
In openIVR, open Settings → Remote access, paste the code. The NVR opens an outbound connection and your site gets a public address.
What stays local, what transits
Stays on your hardware
- Every recording and every export
- AI detection, zones, events
- Your user accounts and camera credentials
- Backups and configuration
Transits through the relay, encrypted
- Interface and API requests, relayed in memory
- WebRTC signalling (offer and answer)
- Media packets via TURN when a direct path is impossible, DTLS-SRTP end to end
- Recording downloads and backup exports are refused by the relay
No frame is ever written to disk on the relay. The tunnel counts bytes in memory; TURN does not record.
Built for people who keep their own data
Works behind CGNAT
The NVR dials out; the relay never needs to reach in. IPv4-less connections, mobile links and double NAT all work.
Two locks, not one
The relay asks for its own session and an active subscription before your request reaches the NVR. Your NVR login applies after that.
Ephemeral TURN credentials
Media credentials are scoped to one site and expire. There is no shared secret anyone could reuse.
Your own address
Each site gets a stable public address on openivr.cloud with a valid TLS certificate. Nothing to renew.
Off in one click
Unpair from openIVR and the site is revoked. Unpaired, the NVR dials nothing at all.
Open source NVR
openIVR is AGPL-3.0 on GitHub. The relay agent, the pairing screen and the tunnel protocol are public.
One subscription, no bandwidth surprises
Questions people ask before subscribing
Do you ever see or store my video?
No. Media packets are encrypted end to end between your NVR and your browser (DTLS-SRTP). When a direct path is impossible, the TURN relay forwards the encrypted packets in memory and forgets them. Recording downloads are refused by the relay altogether.
Do I still need openIVR Cloud if I have a fixed IP?
Not necessarily. openIVR works fully self-hosted, and the cloud module does nothing unless you pair it. openIVR Cloud is for the majority of connections that sit behind CGNAT, or for people who prefer not to expose a port.
What happens if the relay is down?
Your NVR keeps working on the local network: recording, detection, the local interface. Only remote access is affected while the relay is unreachable. The agent reconnects with exponential backoff.
Can I cancel at any time?
Yes. Subscriptions are monthly or yearly and stop at the end of the paid period. Unpair from openIVR whenever you like.
Is this compatible with Home Assistant?
openIVR exposes its API and streams locally; the relay only carries them. Integrations that talk to the NVR directly keep working unchanged.
Which hardware do I need?
Anything that runs openIVR: a mini PC, a Raspberry Pi 5, a NAS with Docker. The relay adds no CPU or GPU load on your side.
Ready to see your cameras from anywhere?
Install openIVR on your own hardware, create a site in the portal, paste the pairing code. Nothing to open on your router.