OwnPilot.
GitHub
Your first flightInstall OwnPilot, connect a model, and give your assistant its first task.InstallationDocker, source development, prerequisites and first-run checks.A system you can understandFollow a request from your interface through the gateway to models, tools and storage.Meet your working crewChat agents, Claw runtimes, Soul identities and multi-agent crews.Give your AI useful handsBuilt-in tools, MCP servers, extensions, skills and your own CLI tools.Your choice of intelligenceCloud providers, aggregators, local models and routing strategies.From a request to a routineVisual workflows, scheduled tasks, triggers, plans and proactive autonomy.Talk where you already areWeb chat, Telegram, WhatsApp, voice and real-time feedback.A memory for your working lifeNotes, tasks, goals, contacts, custom tables and persistent memory.Ownership, with clear boundariesData flow, authentication, tool approvals, isolation and deployment responsibilities.Make it your ownEnvironment variables, Config Center, model settings and safe defaults.Give OwnPilot a reliable homeVolumes, HTTPS, authentication, backups and upgrading a self-hosted instance.Build around the gatewayHTTP APIs, streamed responses, WebSocket events and MCP.
OWNPILOT DOCUMENTATIONESC to close
Documentation/Operate
THE OWNPILOT FIELD GUIDE

Make it your own

Environment variables, Config Center, model settings and safe defaults.

OwnPilot v0.8.3 · Source-verified guide

Two places, different purposes

The .env file configures the server, database and deployment-related settings. Config Center manages provider API keys and service settings in PostgreSQL. Use Settings in the web interface after the server is running.

Database connection

For source development against the bundled database, use 127.0.0.1 and port 25432. Inside the Compose network, the gateway uses the postgres service on port 5432. Keep a strong POSTGRES_PASSWORD in .env.

.env · host development
POSTGRES_HOST=127.0.0.1
POSTGRES_PORT=25432
POSTGRES_USER=ownpilot
POSTGRES_DB=ownpilot
# Set POSTGRES_PASSWORD to a strong, unique value.

Provider credentials

Add credentials through Config Center rather than placing provider API keys in the database connection string or website. The product CLI also writes configuration to the same database. Restrict who can access your configuration interface.

Keys and backup continuity

Keep OWNPILOT_ENCRYPTION_KEY consistent across restarts if you supply it. If you use the generated key, back up the data directory that contains it. Changing or losing encryption key material can make stored credentials unreadable.

Review the complete template

Server ports, CORS origins, rate limits, MQTT, logging and security options are documented in the product’s .env.example and gateway-specific template. Read the source for the product revision you actually deploy.

FOLLOW THE SOURCE

Based on the product’s documented behavior. Check the source for your deployed version.

Product READMEEnvironment template
PreviousOwnership, with clear boundariesUp nextGive OwnPilot a reliable home