Decide whether self-hosting an open-source application fits your team, then brief and accept a secure, recoverable deployment.
An open-source licence removes one fee; it does not arrange updates, monitoring, access control, or recovery. Brownsmith's server work has made this distinction practical rather than theoretical.
You will assess an upstream project and compare a managed service with a VPS deployment. A hands-on path covers Git, Docker, Coolify or Dokploy, networking, authentication, and backups; a founder can use the same material to review an implementer's plan.
The deliverable is a service runbook and restore proof, with a named operator and a point at which managed hosting would be the better choice.
We use this guide in Brownsmith's own team training. The tools are available to anyone; the creative work is choosing what fits the problem and knowing how to judge the result.
Nontechnical founders and small-team operators deciding whether to commission or operate a self-hosted service; the deployment exercises may be completed with a technical implementer.
No engineering experience is required for the decision path. Bring a SaaS tool you may replace or an open-source application you are considering.
The optional hands-on deployment path needs a domain, a Linux VPS, a Git provider, and someone comfortable with a command line.
Put the guide to work
Decide who will operate the service and prove a restore before treating self-hosting as a saving or an ownership win. Commission or carry out a non-critical open-source deployment, then accept it only with protected access, a tested restore, and a handover runbook.
Illustrative product or service: A private team knowledge base deployed on a controlled VPS
Continue the decision path
Evaluate an open-source project, choose hosting, and name who will update, secure, back up, and recover the service.