Operations

When to self-host a small web tool

A tiny application may be simple to install and still expensive to own. Count patching, abuse, backups and handover before choosing it.

Good reason to self-host: you need control that materially reduces risk or cost, and a named team can maintain the service for its entire lifetime.

Define the boundary

A bookmark manager used by five staff is different from a public file drop. Internet-facing tools attract scanning and abuse even when nobody promotes them. Uploads, authentication, URL fetching and document conversion expand the attack surface because they process untrusted input or reach other systems.

Write down who can access the tool, what data it stores, whether it can make outbound requests and what an attacker gains if it is compromised. If the tool is only for a small team, a private network or identity-aware proxy may be more appropriate than a public login page.

Calculate operational work

Installation is the shortest phase. Ongoing work includes operating-system and dependency updates, certificate renewal, log review, backups, restore tests, capacity monitoring and responding to vulnerability notices. Public services also need rate limits, abuse reporting and a plan for illegal or harmful content.

The OWASP Application Security Verification Standard is a useful catalogue of web-application controls. The CISA Secure by Design resources argue that safe defaults and reduced product complexity should be built in rather than shifted to users.

Prefer fewer capabilities

A static information site is easier to defend than an application that accepts files. A redirect table maintained through version control may be safer than a public short-link creator. If a feature is not needed, leaving it out removes code, permissions, data and failure modes.

Run services with the least privileges they require. Separate uploaded or generated content from executable application files. Limit file types and sizes, store secrets outside the repository and avoid exposing management interfaces to the public internet.

Design for recovery and departure

Backups are only useful if someone can restore them. Test a restore to a clean environment and document the dependencies, DNS, certificates and data migrations involved. Keep at least two people able to operate critical tools. If a volunteer or single employee leaves, the domain and accounts must remain recoverable.

Plan an exit format before importing data. Open formats and regular exports reduce lock-in to your own abandoned installation just as they reduce lock-in to a vendor. Decide what the retirement page will say and how old links will be handled.

Use a short decision record

  • What requirement cannot be met safely by an existing managed service?
  • Who owns patching and how quickly must critical updates be applied?
  • What personal or confidential data will be stored?
  • How are authentication, logs, backups and deletion handled?
  • What is the monthly time budget, not just the server bill?
  • How will the service be migrated or retired?

Self-hosting can be a sound choice when control is genuinely valuable and operations are funded. It is not automatically more private merely because the server belongs to you.