Give OwnPilot a reliable home

Start from a tested local setup

Get the Docker setup working locally before placing it behind a public domain. The Compose gateway serves the UI and API on port 8080; PostgreSQL uses persistent named storage.

A public endpoint needs more configuration

Terminate HTTPS at a reverse proxy, configure API authentication and a UI password, and review CORS and WebSocket behavior. Restrict direct access to your database. Set the documented production encryption configuration.

The database port is bound to loopback by the bundled Compose file. Keep optional MQTT access restricted and configure broker credentials before using edge devices.

Persistence and backups

Compose defines gateway-data and postgres-data volumes. Preserve both the application data and database, including encryption key material. Follow the product’s backup/restore guidance and verify restores in an isolated setup.

Updates deserve a checkpoint

Read the release notes, back up your data, and review configuration changes before updating source or rebuilding the container. Pin a tested release for reproducible operations; the website describes v0.8.3 and the documented source snapshot.

Keep this website separate

This product site exports static HTML through Next.js and is deployed to GitHub Pages. It never hosts the OwnPilot API, agents or database. Deploy the assistant separately on a machine capable of running its gateway and PostgreSQL.