Record your cameras on your own machine.
Aperture is a network video recorder for Linux. It records every IP camera that speaks RTSP, tells a person from a passing branch without sending a frame anywhere, and plays it all back in a fast web app on your phone or desktop. Footage stays on your disks.
$ curl -fsSL https://aperturenvr.com/install | sudo sh
A wizard checks the machine, asks two questions and shows every change before it makes one. Debian or Ubuntu on x86-64.
Every camera on one wall.
Live tiles for the whole site or one group, with recording state, the weather and what recognition sees. Beside them: storage, how many more cameras the machine can take, and the live bitrate.
Try it without installing.
A live Aperture with six cameras of sample footage and objects boxed as they move. Sign in with the guest account: it can watch, scrub and search everything and change nothing.
The demo sleeps when nobody is using it, so the first page can take up to a minute.
email guest@aperturenvr.com
password try-aperture
It keeps exactly what the camera sends.
One ffmpeg process per camera copies the stream to disk in ten-second files, indexed as they land. Nothing is re-encoded, so the picture is untouched and a small machine records many cameras.
If a camera stalls, a watchdog reconnects it. When storage fills, the oldest footage goes first, per camera and per disk, and recording carries on.
ffmpeg -rtsp_transport tcp -use_wallclock_as_timestamps 1 \ -fflags +genpts -i rtsp://127.0.0.1:8554/cam_<id> \ -map 0:v:0 -map 0:a? -c:v copy -c:a aac -b:a 32k \ -f segment -segment_time 10 -segment_format mpegts \ -strftime 1 recordings/<camera>/%s.ts
- Where it recordsThe local disk, an SMB share or an SFTP server, and a second copy to another place with its own retention.
- How longPer camera, in days. A camera at 4 Mbit/s fills about 43 GB a day.
- WhenAround the clock, only on motion, or on a weekly schedule you paint.
Drag through a day of footage.
The timeline follows your finger or cursor and the picture keeps up. Recorded hours, events and the live edge sit on one rail; click an event and playback opens there, with the weather at that moment.
A person, not a branch.
Motion is the trigger. Object recognition then runs on the same machine, on its processor or an NVIDIA card, and labels what it sees: people, vehicles, animals and, with the all-in-one model, parcels at the door. Boxes follow them on live video and every event keeps what was found.
Turning it on is one button: Aperture downloads the model you pick and checks it against a pinned checksum. You can also load your own ONNX model.
| Model | Download | Processor | NVIDIA |
|---|---|---|---|
| YOLOX-Tiny | 19 MB | ≈ 30 ms | ≈ 3 ms |
| YOLOX-M | 97 MB | ≈ 300 ms | ≈ 12 ms |
| D-FINE-X, all-in-one | 240 MB | – | ≈ 24 ms |
On your iPhone, as an app.
Aperture for iPhone connects straight to your server: every camera live, H.265 included, a timeline per camera you scroll with your thumb, and the detections your server made, filtered by type and camera. Sign in, or scan the pairing code from the web app, and it switches between your home and remote address on its own.
Notifications carry a snapshot. Your server encrypts each one with a key only your phone holds, so the relay that hands them to Apple can’t read them; the privacy policy has the details.
Get it on the App StoreFree. Needs iOS 18 and Aperture 1.4 or newer.
On Android, Aperture runs in the browser and installs to the home screen like an app: set it up in the browser.
Works with what you already have.
No camera brand lock-in and no hub to buy. If a camera serves an RTSP stream, Aperture records it.
| Cameras | Anything with an RTSP stream: Reolink, Tapo, Hikvision, Dahua, Amcrest, Axis, Hanwha, TP-Link VIGI and more. UniFi Protect cameras through their console, for live view. Eufy through a local bridge. |
|---|---|
| Smart home | Home Assistant over MQTT, with motion, recording and who or what is in view for each camera. HomeKit motion sensors and an arm switch. ONVIF, so Frigate, Blue Iris or Synology can use your cameras through Aperture. |
| Storage | Local disks, SMB shares, SFTP servers. Space you reserve for Aperture stays reserved. |
| Alerts | Web Push with a thumbnail, ntfy, Telegram, Discord, email and webhooks, with quiet hours and rules per camera. |
| Sign-in | Passwords, authenticator codes, passkeys and single sign-on through OIDC. Viewers can be limited to chosen cameras. |
| Hardware | A 64-bit x86 Linux machine with systemd: a mini PC, an old laptop or a virtual machine. An NVIDIA card is optional. |
One command, then a wizard.
The installer asks how you’ll open Aperture and where footage should go, then lists every step and every file before it changes anything. If it finds an NVIDIA card without a driver, it offers to install the right one.
Machine
System, memory, disk space, the ports Aperture needs, and an NVIDIA card if there is one.
Access
This machine’s address, your own domain with HTTPS, a reverse proxy you already run, or your Tailscale network.
Storage
Which disk keeps the footage, with how many days it holds at a typical bitrate.
Review and install
Every command and file, then the install with progress, then a test of the address the way a browser would open it.
Your account
The first administrator, then the address and a QR code for your phone.
What it won’t do.
Better to know now than after an evening of setup.
Not in scope
- No cloud relay. You reach it on your network, or through a VPN or a proxy you run.
- Cloud-only cameras such as Ring, Nest and Blink have no local stream to record.
- One site on one server: no clustering or multi-site management.
- x86-64 Linux only. A Raspberry Pi won’t do.
License
The source is on GitHub under the PolyForm Noncommercial license: free for personal and other noncommercial use. Commercial use, including inside a business, needs a separate license from the author. That makes Aperture source-available rather than open source.
Questions
Do I need an internet connection?
No. Recording, live view, playback, detection and alerts on your network all work offline. The only outside calls are ones you turn on: weather and the map search, push notifications, and the one-time download of a recognition model.
Do I need a graphics card?
No. Recording and motion detection run on any processor, and so can object recognition. An NVIDIA card makes recognition far faster, so it can look at more cameras more often.
How much storage do I need?
A camera at 4 Mbit/s fills about 43 GB a day, so four cameras for two weeks need about 2.4 TB. Recording only on motion uses a fraction of that.
Can I watch from outside my home?
Yes, through a VPN such as WireGuard or Tailscale, which exposes nothing to the internet, or through a reverse proxy with HTTPS. Nothing sits in between.
Is it free?
For personal and other noncommercial use, yes: no tiers, no account, nothing held back. Commercial use needs a license.
Can I try it without cameras?
Yes. The live demo needs nothing installed. To try it on your own machine without cameras, any RTSP source works, including a video file looped by a small RTSP server such as go2rtc or MediaMTX. The screenshots on this page were made that way.