Protect private records
Photos, documents, messages, identity data, and account records need restricted access and tested backups.
Check the access and data choices before you deploy.
Self-hosting moves responsibility for access, updates, and backups to the operator. The catalog marks services that need extra review.
Review host control
A privileged container, host networking, or Docker socket access can affect more than one application.
Keep the default boundary
A standard label means the recorded stack avoids the high-risk runtime flags. You must still review passwords, routes, and storage.
Back up persistent data
Back up application data and databases before upgrades. Test that you can restore them.
Use the technical checks before deployment
Every stack README lists its configuration and verification steps. The repository also documents shared networks, secrets, monitoring, and troubleshooting.
Read the deployment guide