Fanatically PRIVATE video tech
LANcams turns the devices you already own into a live camera system for your home. Point a spare phone at the bird feeder, the driveway, or the front door — then watch from any browser on your network. No apps, no accounts, no subscriptions. Or open a room and share cameras with people anywhere.
1 — Watch your own place. Open this page on any device at home. Tap Add+ on a spare phone pointed at the bird feeder or the front door; every screen in the house can now watch it. That's the whole setup.
2 — A room: your own tiny video meeting. Tap the room tile, hit the dice for a random room name, and send the link (or show the QR code) to anyone, anywhere. Everyone who opens it lands on the same shared wall of cameras — a funny little conferencing tool with no accounts, no downloads, and no time limits. Joining a room never shares your camera until you choose to; leaving is one click, and leaving always stops your cameras first.
Your video streams directly between your own devices over your local network (WebRTC). This site only performs the introductions; the video itself never reaches our servers, is never stored, and is never visible to anyone outside your household (or your room). That's not a privacy promise you have to trust — it's how the plumbing works.
LANcams is open source, and the whole thing can run on a machine on your own LAN — handy if your internet is down or you simply prefer it. But because the design keeps video local anyway, you don't need to self-host to get the privacy; using this site is the same plumbing with less setup.
This server is in private beta. If someone invited you, open the invite link they sent you — or paste the invite code here:
Running…
This page fetched its own files, hashed them, and compared the hashes against the signed release manifest; the server also reported a self-check of its files. The honest caveat: this verdict is rendered by code delivered by the very server being audited — a malicious server could serve a page that lies about all of this. In-page verification catches accidents, stale deploys, and lazy tampering; it cannot catch a coherent lie. (The Node runtime, OS, TLS stack, and your browser are likewise out of scope: they are trusted.)
Run the same audit from your own machine, where this server can't touch the verifier. It can't know when it's being sampled — which is what makes lying risky:
Fully independent version: clone the (AGPL) repo, check
out the release tag, and run sh public/audit.sh <site-url>
from the checkout — then the verifier itself came from the repo, not
from this server. The signing key's fingerprint is published in the
README.
Changes go straight to the device over a direct connection — they do not pass through the server. A camera may clamp or override what you ask for; the values shown are what it actually reports.
This server sees your address as: …
Not connected to the signaling server yet, so this page doesn't know which group it's in. (If this persists, check the connection dot in the header.)
Cameras are only visible to devices that connect from this same public address — in other words, devices behind your own router. Different households can never see each other's cameras, and the server refuses to carry connection setup between them.
This server is running on your local network: anyone who can reach it can watch and share cameras. The trust boundary is your LAN.
LANcams can live on your home screen or dock like any app — same page, its own icon and window, nothing downloaded from an app store. Installing changes nothing about privacy: the app is this page, loaded fresh from the network every time (the integrity audit still covers exactly what runs). On iPhone or iPad: tap the Share button, then Add to Home Screen. Elsewhere, look for an install icon in the address bar.
How LANcams works, what the server can and cannot see, the security model and the known incompatible setups are all the same for everyone, so they live on their own page: questions & answers · about LANcams.
Anyone in this room can ring this device — even with the page closed.
Your browser makes a push address; the server stores it sealed with the room's name, which it never learns. Turning the bell off deletes it; 60 days without a visit expires it. The push service (Apple, Google or Mozilla) sees only that a small encrypted message arrived — never the room. Your lock screen says just "a room you keep is ringing".
On this device, ringing only works once LANcams is installed (push notifications need the real app).
Applies to every tile on this page and is remembered on this device. Browsers reveal device names once a camera or microphone permission has been granted; on browsers that cannot switch outputs, the 🔈 button does not appear at all.