Choosing where to put databases on a small home server
A small home server can become harder to manage when many self-hosted apps each need their own database. The example setup is one repurposed with one CPU, 8 cores, and 32GB of memory, running Proxmox with separate and containers for Docker.
About 15 services run on it, including Immich, Paperless, bookmark tools, ArchiveBox, and other small apps. The practical question is whether all databases should live together in one separate database , or whether services should be grouped into different with their own databases.
The operator makes small changes, uses one Portainer setup with agents across different , and wants the server to stay a useful tool rather than a full-time hobby. The best answer needs to balance simplicity, backup work, and failure risk.
Key points
- The setup is a single small server running about 15 self-s.
- Many of those services need their own database.
- The main choice is one shared database or separate databases grouped by service.
- The operator wants a simple tool, not a complex home lab project.
- For a , database layout should be planned around backups and recovery, not only .