Sections written: - Getting Started (what-is-openacp, for-users, for-developers, for-contributors) - Platform Setup (Telegram, Discord, Slack) - Using OpenACP (commands, sessions, agents, permissions, voice, files) - Self-Hosting (installation, configuration, daemon, security, logging, updating) - Features (tunnel, context-resume, usage, persistence, handoff, doctor, assistant) - Extending (plugin-system, building-adapters, adapter-reference, contributing) - API Reference (CLI commands, REST API, config schema, env vars) - Troubleshooting (Telegram, Discord, Slack, agent issues, FAQ) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.0 KiB
1.0 KiB
Self-Hosting
Everything you need to run OpenACP on your own infrastructure.
OpenACP is designed to be self-hosted: you own the process, the config, and the data. There are no cloud accounts required beyond the messaging platform bots you configure. All state lives in ~/.openacp/.
In this section
- Installation — System requirements, global install via npm, first-run setup wizard, and running from source.
- Configuration — The full config schema, interactive editor, environment variable overrides, and backward compatibility guarantees.
- Daemon Mode — Running as a background process, PID/log file locations, and autostart on boot.
- Security — User allowlists, session limits, API bearer token authentication, and best practices.
- Logging — Log levels, file rotation, per-session logs, and structured JSON format.
- Updating — How to update, automatic config migrations, and the backward compatibility guarantee.