Baby monitors that don't send video to the cloud

Most video baby monitors sold today send the picture of your baby to a company's servers. Not as a bug or a dark pattern — as the design. That is how you watch from the office, how the app shows you last night's clips, and how the subscription justifies itself.

It also means a video stream of your child's bedroom exists somewhere other than your home, reachable by anyone holding the right credentials, retained under a policy you did not write and can change.

Some people are fine with that trade. If you are not, the question becomes how you tell the difference — because the marketing language is nearly identical on both sides.

What "cloud" actually means here

Three separate things get called the cloud, and only one of them involves your video leaving the house.

• Account and settings sync. Your login, your device list, your notification preferences. Almost every monitor does this, including local-only ones. It carries no video.
• Relayed live video. Your camera sends the stream to a server; your phone fetches it from that server. This is how remote viewing works. The video passes through infrastructure you do not control — even when it is encrypted end to end, the traffic goes through.
• Stored recordings. Clips and events kept on the company's servers so you can scroll back. This is the one subscriptions are usually selling.

A monitor can do the first without the second or third. "Local-only" should mean it does not do the second or third at all — not that it encrypts them.

Which parts genuinely need the internet

Being precise about this is the whole point, because vendors blur it.

Watching from the same house does not need the internet. Two devices on one Wi-Fi network can talk to each other directly. Your router does the work. If your broadband died right now, a well-built local monitor would keep working, because nothing it does crosses your front door.

Watching from outside the house does. There is no way around it. Your phone on mobile data and a camera in your living room cannot reach each other without something in the middle — a relay server, a hole punched through your router, or a VPN back into your home. Any monitor offering remote viewing is doing one of these, whatever it is called in the marketing.

Push notifications do. This one surprises people. An alert on a locked phone goes through Apple's or Google's push service, which means a small message leaves the house even on an otherwise local system. It should not contain video or audio — but it does travel.

Stored history does not have to. Events and snapshots can sit on the device that recorded them. Keeping them on a server is a product decision, not a technical necessity.

The trade you are actually making

A local-only monitor is not a strictly better monitor. It is a different one, and it is worth being clear about what you give up:

• You cannot check in from work. This is the big one. If being able to look at the crib from a restaurant matters to you, local-only is the wrong choice and no amount of privacy argument changes that.
• No scrollable cloud history. Whatever is kept is kept on the device, and it goes when the device goes.
• Losing the phone loses the data. There is no backup you did not make yourself. That is the same property that makes it private.
• Setup is on you. No account recovery flow can rescue a pairing that lives only on two devices.

What you get in exchange is simple: there is no copy of your baby's bedroom anywhere else. Not a well-guarded copy — no copy.

How to tell, before you buy

Marketing pages will not answer this. The privacy policy usually will. Four questions, in order of how much they reveal:

1. "Does live video work if my internet is down but my Wi-Fi is up?" If yes, local viewing is real. If the whole product dies with the broadband, everything was going through a server.
2. "Where are recordings stored?" Look for a plain answer. "Securely encrypted in our cloud" is an answer to a different question.
3. "Can I watch from outside the house?" If yes, video leaves your network. That may be worth it — but now you know.
4. "What happens to my footage when I delete my account?" A company with no footage answers this instantly. A company with footage answers it in paragraphs.

One more, if the answers feel slippery: ask what the monitor does when the company shuts down. Cameras that need a server to work are cameras with an expiry date.

How Bebrise does it

Two phones on your home Wi-Fi find each other directly — the bedside phone advertises itself on the local network and your phone connects to it there. The video runs over WebRTC, encrypted in transit, straight between the two devices.

The part worth explaining is what is missing. A WebRTC connection that needs to work across the internet requires relay infrastructure — STUN and TURN servers that help two devices find each other, and carry the traffic when they cannot connect directly. Bebrise ships with that server list empty. There is nothing to fall back to, which is exactly the point: it is not that we choose not to relay your video, it is that no relay exists to route it through. If the two phones are not on the same network, the picture does not appear.

The detection runs the same way. Cry recognition and the camera analysis happen on the bedside phone itself, so the audio and the frames never need to go anywhere to be understood — how that works is its own guide. Events and snapshots stay on the phone that recorded them.

What does leave: your account details, and push notifications through Apple and Google so an alert can reach a locked phone. Not video, not audio. The privacy policy lists it all rather than summarising it, including the parts most policies leave out.

And the cost, stated plainly: you cannot watch from outside your home. We have not built it, and if we ever do it will be something you switch on knowingly rather than something that arrives in an update.