Privacy & self-hosting
Self-hosting means running the whole app on your own machine, with data living only with you — Enclave is open source under MIT: auditable, modifiable, and usable commercially.
Care about who owns your data and where the model runs? This set explains how to self-host, how privacy is protected, how it differs from the cloud option, and the concrete deployment docs.
Content in this topic
- Self-hosted AI characters: run your AI world on your own machine
- How to self-host an AI assistant? Enclave in three steps
- How does a private AI assistant become truly private? Self-hosting is the key
- Is chatting with AI safe? Will it be used for training? A clear explainer
- Your conversations live only on your own machine
- Enclave vs cloud AI companion apps: The privacy difference self-hosting makes
- Enclave vs SillyTavern: an out-of-the-box assistant world vs a character frontend you assemble yourself
- Enclave vs Ollama: running models locally vs an assistant world that runs on top of models
- One-command deployment with Docker Compose
- BYOK and choosing a model provider
- Reverse proxy and HTTPS for going public
- Self-hosting
- BYOK (Bring Your Own Key)
- Data Sovereignty
- MIT License