Where Does MaxKB Store Config and Data?
MaxKB Docker deploy folder, env file and database volumes on Linux.
Last updated
MaxKB runs as a Docker stack from a compose file you keep. The file, its .env beside it and the named volumes carrying Postgres and uploaded documents are the install. There is no /etc service layout or home directory store.
Assistants, datasets, models and API keys live in the database volume, while endpoints, ports and credentials come from the compose file and env. Upgrades replace images and keep volumes, which is exactly why deleting volumes wipes everything. Treat the compose directory and its volumes as one unit in backups.
Where MaxKB stores this, by platform
docker-compose.yml, .env and volumes in your deploy folder
Whichever directory you deployed from. Inspect volumes with docker volume ls and confirm mounts with docker inspect before upgrading. Keep .env out of git; it holds database passwords and model keys.
Frequently asked questions
where are MaxKB documents and chat logs
In the Postgres volume of the compose stack, referenced by the datasets you created in the UI. Export datasets from the app for portability. The compose folder alone restores structure without content.
I lost MaxKB data after an upgrade, why
The volumes were recreated instead of reused, often from running compose in a different directory or pruning volumes. Always upgrade in the original deploy folder and never prune volumes holding the database.
Notice an outdated path? Let us know.