Independent-minded guidance for choosing, deploying and operating the applications your team depends on.
Roles and workspaces can control everyday access, but they are not the same as an independent deployment. Use this framework to decide when a shared self-hosted application is appropriate, when separate instances provide a clearer governance boundary, and when another delivery model is a better fit.
Read guide
A database backup is often not enough to recover a self-hosted application. Use this framework to inventory uploads, attachments, exports, media and temporary data, then choose persistent volumes, object storage or another supported storage design with recovery and migration in mind.
Read guide
A practical framework for choosing between separate local accounts, a shared identity provider, or a hybrid model across a growing self-hosted application stack.
Read guide
Background workers keep long-running and scheduled tasks out of the interactive request path. Use this framework to decide whether your self-hosted application needs workers, what dependencies to verify, and when a single-server design is still the sensible choice.
Read guide
Transactional email is a core dependency for self-hosted applications, not a checkbox. Learn how to inventory essential messages, choose a sending model, authenticate your domain, protect SMTP credentials and prepare for delivery failures.
Read guide