How the pieces fit together
Frigate
Connects cameras, records video, and detects events.
Avistio Edge
Runs at your location and connects securely to Frigate.
Avistio Cloud
Connects your site for authorized remote access and management.
Frigate and Avistio Edge may run on the same computer or on separate computers.
Before you start
You will need:
- A computer, mini PC, NAS, or server that supports Docker and Docker Compose.
- An installed, working Frigate system with at least one camera.
- The local IP address of the Frigate host.
- A Frigate username and password.
- A browser on the same local network as Avistio Edge.
New to Frigate? Start with the official Frigate getting started guide.
Prepare Frigate
First, open Frigate and make sure your camera appears and its live picture works. Avistio checks that Frigate camera names have matching go2rtc stream names. This is a current Avistio Live-readiness requirement.
Correct
Camera: frontdoor
go2rtc stream: frontdoor
Not ready for Live
Camera: frontdoor
go2rtc stream: frontdoor_main
The connection check can confirm this name mapping on the server. It does not test whether a browser can establish a video connection. For the full configuration and network details, see Configure Frigate for Avistio.
Install Avistio Edge
Open a terminal on the computer that will run Edge. Create an installation folder, then save the Compose example below as compose.yaml inside that folder.
mkdir avistio
cd avistio
# Save the compose.yaml shown above in this directory.
docker compose up -d
docker compose psservices:
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
healthcheck:
test: ["CMD", "wget", "--quiet", "--tries=1", "--spider", "http://127.0.0.1:3000/_nginx-health"]
interval: 10s
timeout: 5s
retries: 3
start_period: 10s
networks:
- avistio
database:
image: postgres:17-alpine
restart: unless-stopped
depends_on:
config-init:
condition: service_completed_successfully
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
networks:
- avistio
volumes:
avistio_config:
postgres_data:
networks:
avistio:
name: avistioThis is the production deployment: it runs Edge, a PostgreSQL 17 Alpine database, and a one-time configuration initializer. The initializer creates installation secrets automatically and stores them in the persistent avistio_config volume. PostgreSQL waits for initialization and passes its health check before Edge starts.
Start the services and confirm they are running:
docker compose up -d
docker compose psA successful startup shows the avistio and database services running, and config-init completed successfully. The database may take a short time to become healthy on its first start.
Open Avistio Edge
On a browser connected to your local network, open http://192.168.1.20:3000. The address 192.168.1.20 is only an example; replace it with the local IP address of the computer running Edge.
Create the first administrator account when prompted. Then enter the Frigate connection details:
- Frigate URL
http://192.168.1.10:8971- Username
- Your Frigate username
- Password
- Your Frigate password
- Timeout
- Keep the default initially
Here 192.168.1.10 is an example Frigate host address. The URL must be reachable from the Avistio Edge container; if Edge and Frigate are on different computers, use an address and port reachable between them.
Choose Test connection. Edge checks Frigate API connectivity, authentication, camera discovery, go2rtc stream inventory, and whether each camera has a matching stream name.
Verify local monitoring
Open each area and confirm the information you expect is available:
- Dashboard: cameras and current status.
- Cameras: discovered cameras and local live playback.
- Events: event summaries when Frigate is producing events and the data is available.
- Recordings: historical video when Frigate recording is enabled, configured, and has retained footage.
For a missing camera or stream, use the Troubleshooting guide.
Connect Avistio Cloud
Pairing links this Edge installation to a Cloud site. Pairing codes are short-lived; generate a fresh code if one expires.
A · In Avistio Cloud
- 1Open app.avistio.app.
- 2Sign in or create an account.
- 3Open My Sites, choose Add site, enter a site name, and generate a pairing code.
B · In Avistio Edge
- 1Open the Cloud section in Avistio Edge.
- 2Enter the pairing code.
- 3Choose Connect Avistio.
C · Verify
- 1Return to Cloud and confirm the site is connected.
- 2Check camera discovery and try remote Live playback.
Update Avistio Edge
Run these commands from the directory containing compose.yaml:
docker compose pull
docker compose up -d
docker compose psThe persistent Docker volumes retain your installation settings and database while Docker replaces the application image.
For update or connection problems, continue to Troubleshooting Avistio Edge.
Partner installations
Partner installers use the same Edge deployment. In Cloud, create a Partner organization, then use Add customer site to create the site and generate its pairing code. At the customer location, install Edge using the steps above, verify its local Frigate connection, and pair it with that code.
After pairing, create a customer claim link from the Partner site page and give it to the customer. The customer accepts the claim to take ownership of the site.

