Skip to content

FAQ

For personal and other noncommercial use, yes: no paid tier, no account, nothing held back. Commercial use, including use inside a business, needs a separate license. See License.

The code is public, but the PolyForm Noncommercial license restricts commercial use, so it is source-available rather than open source in the OSI sense.

A 64-bit x86 Linux machine with systemd that stays on: a mini PC, an old laptop or a virtual machine. Recording copies each camera’s stream instead of re-encoding it, so it is light; motion detection and object recognition are where processor time goes. See Requirements and sizing and Camera capacity.

Does it run on a Raspberry Pi, ARM, Windows or macOS?

Section titled “Does it run on a Raspberry Pi, ARM, Windows or macOS?”

No. Aperture runs on x86-64 Linux only. A Linux virtual machine on another system works.

Aperture installs as native systemd services with make install. The repository still has Docker files from an earlier setup, but they are not the supported way to run it.

Anything that serves an RTSP stream, which is most IP cameras. ONVIF is optional and adds picture controls. UniFi Protect cameras come in through their console for live view. Cloud-only cameras (Ring, Nest, Blink, most Arlo) have no local stream. See Add cameras and UniFi Protect cameras.

No. Recording, live view, playback, detection and alerts on your network all work offline. The optional outside calls are listed in What leaves your network.

No. Recording and motion detection run on any processor, and object recognition can run on the processor too. An NVIDIA card makes recognition much faster and lets it look at more cameras more often. See Object recognition.

It depends on your cameras’ bitrate: a camera at 4 Mbit/s fills about 43 GB a day, so four of them for two weeks need about 2.4 TB. Motion-only recording uses a fraction of that. Requirements and sizing has a table.

Yes, through a VPN such as WireGuard or Tailscale, which exposes nothing to the internet, or through a reverse proxy with HTTPS. Aperture runs no relay for your video or for remote access. (The iPhone app’s notifications go through a small push relay, encrypted so it cannot read them; see Privacy.) See HTTPS and remote access.

Why can’t I install it on my phone or get push notifications?

Section titled “Why can’t I install it on my phone or get push notifications?”

Phones only install web apps, send push notifications and use passkeys on secure (HTTPS) pages. Put Aperture behind a reverse proxy with a certificate. See On your phone.

Can I record only when something moves, or only at night?

Section titled “Can I record only when something moves, or only at night?”

Yes, per camera: continuous, motion only, on a weekly schedule, or off. Motion clips keep a few seconds before and after the trigger. See Recording modes and schedules.

No. Video is stored exactly as the camera sends it. Audio is converted to small AAC. Re-encoding video to save space is a per-camera option, off by default, and costs processor time. See Recording.

The oldest footage is removed first, by each camera’s retention and each destination’s limit, so recording never stops because storage ran out. See Storage.

Can some cameras keep footage longer than others?

Section titled “Can some cameras keep footage longer than others?”

Yes. Retention is set per camera, and a camera can mirror its footage to a second destination, such as a NAS, that keeps it for longer. See Storage.

Yes, if the camera sends audio. It is stored as AAC alongside the video. Audio detection is a separate option; see Motion and audio detection.

Not from Aperture itself. The example extensions in the repository add pan and tilt for Tapo and Eufy cameras. See Extensions.

Only accounts you create on your Aperture. Viewers can be limited to the cameras you choose. See Users, roles and camera access.

They never leave the server: the app shows each address with the login masked, and you replace it rather than read it. On the server, camera addresses are kept in the database and in go2rtc’s configuration, both readable only by their owner. Storage and other account passwords are encrypted at rest. See Security model and hardening.

Configuration backups (cameras, users, rules, settings) are one click. Footage is deliberately not part of them; keep it safe by mirroring to a NAS. See Backup and restore.

Where do I report a bug or a security problem?

Section titled “Where do I report a bug or a security problem?”

Bugs go to the issue tracker. For a security problem, see Security model and hardening for how to report it privately.