Install Avistio Edge

• A working Frigate installation
• A Docker and Docker Compose capable machine for Edge
• Network access from Edge to Frigate and browser access to Edge

Edge and Frigate can run on different machines.

Avistio authenticates to Frigate. Use its authenticated API endpoint where available, for example http://<FRIGATE-IP>:8971, with a Frigate username and password.

Live stream names and WebRTC

Required: Avistio currently expects the camera name and its primary go2rtc stream name to match. A camera named frontdoor needs a stream named frontdoor; frontdoor_main will not be Live-ready. Avistio Test connection reports available stream names.

go2rtc:
  streams:
    frontdoor:
      - rtsp://<USERNAME>:<PASSWORD>@<CAMERA-IP>/stream
  webrtc:
    listen: :8555
    candidates:
      - <FRIGATE-HOST-IP>:8555
      - stun:8555

cameras:
  frontdoor:
    ...

For Live, the browser must reach Frigate/go2rtc on 8555 TCP/UDP as appropriate. The candidate is normally the Frigate host address, not the Edge address. Do not expose this port publicly just for Avistio.

Create a directory, save this as compose.yaml, then start it.

services:
  config-init:
    image: ghcr.io/d-aro/avistio:latest
    entrypoint: ["/config-init.sh"]
    environment:
      CONFIG_INIT_DATABASE_ONLY: "true"
    volumes: [avistio_config:/config]
  avistio:
    image: ghcr.io/d-aro/avistio:latest
    restart: unless-stopped
    ports: ["3000:3000"]
    volumes: [avistio_config:/config]
    environment: { TZ: ${TZ:-UTC} }
    depends_on:
      config-init: { condition: service_completed_successfully }
      database: { condition: service_healthy }
  database:
    image: postgres:17-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: avistio
      POSTGRES_USER: avistio
      POSTGRES_PASSWORD_FILE: /config/postgres-password
    volumes: [postgres_data:/var/lib/postgresql/data, avistio_config:/config:ro]
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U avistio -d avistio"]
      interval: 5s
      timeout: 5s
      retries: 10
volumes: { avistio_config: {}, postgres_data: {} }

mkdir avistio && cd avistio
docker compose up -d
docker compose ps
docker compose logs -f avistio

Docker volumes retain Edge configuration and its database. Do not delete them during normal updates.

Open http://<EDGE-IP>:3000, create the first administrator, then enter Frigate URL, username, password, and timeout. Test connection checks API authentication, camera discovery, go2rtc inventory, and camera-to-stream readiness.

A result such as 0 of 1 cameras ready for Live means Frigate connectivity works but the stream mapping needs attention. Server-side validation cannot guarantee browser ICE connectivity. Before pairing, verify Dashboard, Cameras, Live, Events, and Recordings locally.

Create or sign in to your Avistio Cloud account. In Cloud, open My Sites, choose Add site, give the site a name, and select Create pairing code. On Edge, open Avistio Cloud, enter the short-lived pairing code, and choose Connect Avistio.

Confirm the site is connected in Cloud, then verify its cameras, Live, Events, and Recordings as available.

The technical Edge installation is the same. In Cloud, create a Partner organization and use Add customer site to generate a pairing code. After local verification and pairing, create a customer claim link. The customer accepts the claim to become owner; installer status access never grants cameras, recordings, alarms, users, or configuration access.

docker compose pull
docker compose up -d
docker compose ps

Frigate connects but is not Live-ready: use Test connection and match the camera name to its go2rtc stream. Live stays Connecting: verify the go2rtc listener, 8555 reachability, and browser-reachable Frigate candidate. Edge will not start: run docker compose ps, docker compose logs avistio, and docker compose logs database.