Skip to content

What leaves your network

Aperture has no cloud service for your video, no account and no telemetry. It does not check for updates or report usage. The one service of ours is a small push relay for the iPhone app’s notifications, which works only if you turn those notifications on (see The iPhone app). This page lists every connection it can make beyond your own network, taken from the code, with what each one sends and how to avoid it. Everything here is optional: recording, live view, playback and alerts on your network work with no internet connection at all.

Connection Made by Only when Sends
Open-Meteo weather the server a site location is set and weather history is on (default on) the site’s coordinates
Open-Meteo place search the server you search an address in Settings › Environment the text you typed
Open-Meteo time zone and elevation the server you move the map pin the new coordinates
OpenStreetMap map tiles your browser the map in Settings › Environment is on screen the map area you look at
STUN go2rtc live video over WebRTC a request for the server’s public address
Web push service the server you turned on push notifications an encrypted notification
Notification channels the server you set one up the notification text, a link, an image link
Webhooks and automations the server you set one up event details as JSON
Object recognition downloads the server you turn on local object recognition file requests to GitHub, NVIDIA, Hugging Face
External detector the server you set a Detector URL snapshots of events
Network storage the server you add an SMB or SFTP destination footage
Extensions the extension you install one with network access whatever it is written to send, to the hosts you approved
Eufy bridge the bridge service you set up the Eufy integration your Eufy account sign-in

When a site location is set under Settings › Environment, Aperture records the weather alongside your footage (internal/weather/weather.go). The server calls Open-Meteo:

  • api.open-meteo.com/v1/forecast with the site’s latitude and longitude (5 decimal places, about 1 m), every 10 minutes by default (Poll interval), and once after the first poll for a location to backfill the last 7 days;
  • geocoding-api.open-meteo.com/v1/search with the text you type in Search address or place;
  • api.open-meteo.com/v1/forecast with timezone=auto when you move the pin, to look up the time zone and elevation.

Open-Meteo needs no key and receives no account information, but it sees your server’s public IP address and the coordinates.

To stop it, turn off Record weather history in Settings › Environment, or do not set a location. Sunrise, sunset and moon phase are calculated locally and keep working. If you want weather but not your exact address, place the pin a few streets away.

The map on that page is drawn by your browser from tile.openstreetmap.org. Your browser, not the server, loads the tiles for the area on screen, so OpenStreetMap sees your browser’s IP address and that area. The map loads only while the page is open.

See Site and weather.

go2rtc’s WebRTC configuration includes the candidate stun:8555. With it, go2rtc asks a public STUN server for the server’s public IP address so that WebRTC can work from outside your network. go2rtc’s default STUN server is Google’s (stun.l.google.com:19302). The request contains no video and no camera information.

The browser side uses no STUN or TURN servers. The setting lives in go2rtc’s config file, /var/lib/aperture/go2rtc.yaml, under webrtc: candidates:. See Live streaming.

Push notifications to a phone or browser go through the push service of that browser’s vendor (Google for Chrome and Android, Mozilla for Firefox, Apple for Safari). The browser picks the service when you turn push on; Aperture sends to the address the browser gave it.

The message contains a title, the text, a link into Aperture and a link to the event thumbnail. It is encrypted for your device before it leaves the server (the Web Push standard), so the push service sees its size and timing, not its content. Keys are generated locally; Web Push uses no Aperture server. The iPhone app’s notifications work differently; see below.

The iPhone app’s notifications are delivered by Apple’s push service, which your server cannot reach on its own. So when you turn notifications on in the app, the app registers with a relay at https://push.aperturenvr.com, which Aperture’s author runs on Cloudflare. The relay gives the phone a random device id and a secret and hands them to your server. For each notification your server encrypts the message with a key only your phone holds (AES-256-GCM) and posts it to the relay, which passes it to Apple. The relay sees the random device id, the encrypted message and a random event id; it cannot read which camera, what was detected or when, and it never receives pictures or accounts. The phone decrypts the message and loads the picture directly from your server.

The relay stores, for each device, the random id, the secret, Apple’s push address for the device, the app’s identifier, whether it is Apple’s test or production environment, and when it was registered and last used. An entry is deleted when you turn notifications off or sign out, and after 180 days without a delivered notification. The privacy policy has the complete list, including what Cloudflare keeps.

Your server only sends to relays on its allow list, APERTURE_PUSH_RELAYS in /etc/aperture/aperture.env: a comma-separated list of base URLs, Aperture’s own relay by default. Set it to none to turn the relay off, or to your own relay’s address. Without a relay on the list, the iPhone app cannot register for notifications, and Web Push and the other channels below are not affected.

Each channel sends to the service you point it at (internal/notify/channels.go):

Channel Sends to What
ntfy https://ntfy.sh by default, or your own server title, text, link, image link
Telegram api.telegram.org title, text, link; with an image, Telegram fetches it from the image link
Discord your Discord webhook address title, text, link, image link
E-mail your SMTP server title, text, link, and the image as a link in the HTML
Webhook the address you enter title, text, link and image link as JSON

Notifications carry a link to the event’s thumbnail, not the picture itself: <APERTURE_PUBLIC_URL>/api/public/event-thumb?…, signed and valid for 24 hours. Whoever has the link can open that one thumbnail for that time. The service or app showing the notification fetches the image from your server, so the image appears only if that address is reachable from where it is fetched. With APERTURE_PUBLIC_URL set to a LAN address, external services get no image.

See Notifications.

Webhooks under Integrations › Webhooks and the webhook action of automations post event details as JSON to the address you enter: event id, camera id, type, times, score and recognised objects, plus a link into Aperture. The webhook from Integrations is signed with an HMAC; see The API and tokens. See Automations.

Local object recognition runs on your server. When you turn it on under Settings › Detection, Aperture downloads, once, the runtime and the model you chose (internal/ai/catalog.go), each pinned to a version and checked against a SHA-256 checksum before use:

What From
ONNX Runtime (CPU or CUDA build) github.com/microsoft/onnxruntime/releases
NVIDIA CUDA and cuDNN libraries, for the GPU build only developer.download.nvidia.com
YOLOX models github.com/Megvii-BaseDetection/YOLOX/releases
D-FINE models huggingface.co/onnx-community

The requests carry the user agent Aperture-NVR and nothing about your install. Frames are analysed locally and never uploaded. A model you add yourself is uploaded from your browser to your server and downloads nothing.

If you use an external detector instead (CodeProject.AI or DeepStack, set by its Detector URL in Settings › Detection), Aperture sends snapshots of each event to that address. If that server runs on your network, nothing leaves it. See Object recognition.

An SMB or SFTP destination receives footage, which is the point of it. If the destination is outside your network, your footage is too. See Storage.

A backend extension can reach only the hosts its manifest declares and you approved at install, plus Aperture’s own API. A panel can make outside requests only through Aperture, to those same hosts. Within that, an extension sends whatever its code sends. When you open the extension manager, Aperture checks the update address of each installed extension that has one. See Extension permissions and Extension security.

  • Home Assistant connects over MQTT to the broker you configure, by default the Mosquitto broker on the same machine. See Home Assistant.
  • HomeKit and the ONVIF provider work on your LAN. How Apple Home reaches your cameras when you are away is Apple’s design. See HomeKit and ONVIF and RTSP.
  • UniFi Protect streams come from your Protect console on your network. See UniFi Protect.
  • Eufy: the bridge service signs in to your Eufy cloud account, because Eufy offers no local control API. Aperture stores the account password encrypted and passes it only to the bridge.

Building and installing (make install) downloads Go modules, npm packages, distribution packages through apt, and the pinned go2rtc and Deno releases from GitHub, each checked against a checksum. That happens when you run the installer, not while Aperture runs. See Install and Updates.

What Aperture does not control is your cameras. Many cameras contact their manufacturer’s cloud on their own. Aperture never asks them to, and works fully without it. To keep a camera local, block its internet access in your router; a separate VLAN for cameras is the usual way. See Security model and hardening.

Related: Security model and hardening, Notifications, Site and weather.