Host boundary

Home server or single VPS?

Choose the host boundary from public exposure, network control, power recovery, maintenance access, and the independent backup destination.

Best fit

Home server or NAS

Private services or users who can operate their own network, power, and off-site recovery path.

  • • Public exposure requires deliberate router and firewall work.
  • • Power and uplink are part of the service boundary.
  • • Off-site backup remains separate from the host.

Best fit

Single VPS

Public services where a stable public IP, data-center network, and simple remote access fit the operating model.

  • • Host capacity, snapshots, and backup storage become recurring operating decisions.
  • • Provider snapshots do not replace an independent recovery copy.
  • • Public access still needs firewall and reverse-proxy discipline.

Decision rule

Choose the host whose networking, power, updates, and recovery workflow you can keep current. Build the deployment blueprint before comparing specific providers.

Build the deployment blueprint

Sources and scope

Last reviewed 2026-07-13. This page separates the decision it supports from the facts that still require a platform or model-specific check.

Applies to

Single-host Docker Compose planning.

Does not cover

Provider pricing, availability, regional regulation, or a benchmark of a particular host.

Docker Compose production guidanceProduction-specific Compose configuration, restarts, ports, logging, and deployment changes.Open source ↗Docker Compose quickstartNamed volumes, environment configuration, and validating rendered Compose configuration.Open source ↗