Application hosting

Hosting Caddy

Caddy is a web server and reverse proxy. Its official documentation covers Linux service operation, Caddyfile configuration, and automatic HTTPS; server sizing depends on the workload and is not published as a universal requirement.

Min vCPU
Depends on workload
Min memory
Depends on workload
Min storage
Depends on workload

Must have

Hard prerequisites

No universal server-size prerequisite is published. Check the exact release and configuration before you deploy.

Recommended

Documented guidance

No further general recommendations are published for this version.

Capacity depends on your workload

The cited installation and service documentation does not give a universal CPU, memory, or disk minimum. TLS certificates, access logs, proxied applications, and traffic affect resource use.

We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.

Deploy with

Supported paths

  • Official Linux packages with systemd service units
  • Official Docker image with Docker Compose
  • Caddyfile or JSON configuration

The host must provide

Runtime

Operating system
A supported platform/build for the selected Caddy release
Service manager
systemd 232 or newer when using the documented Linux service setup
Network access
Public HTTP/HTTPS access and valid DNS are needed for the documented public automatic-HTTPS flow

Storage

Persistent data

Persist configuration and Caddy data, including certificate state; decide how access logs are retained and backed up. The cited pages do not set a universal disk allowance.

Step by step

Caddy deployment outline

  1. Choose an install path

    Use the official Linux service package or container instructions and keep the supplied data/configuration locations persistent.

    Official instructions
  2. Configure the site

    Define the site address and handlers in a Caddyfile or supported JSON configuration; use the reverse-proxy guide when forwarding requests to an application.

    Official instructions
  3. Check public HTTPS prerequisites

    For automatic public certificates, point the domain at the server and allow the documented HTTP/HTTPS validation path. Keep administration interfaces private.

    Official instructions

Security

Before you go public

  • Keep the administrative API private unless the deployment has an explicit access-control design.
  • Run the service with the official service unit and review file ownership for its configuration and data.
  • Keep a restorable copy of configuration and certificate state.

Cost

Beyond the server price

  • The software itself is open source; hosting, bandwidth, persistent storage, and any domain or external service remain separately charged.
  • No server price or resource size is specified by the cited project pages.

Matching plans

Plans with published evidence

DigitalOcean

CPU-Optimized Regular Droplet · 2 vCPU / 4 GiB

2vCPU
4 GiBRAM
25 GiBStorage
4 TBTransfer
  • Dedicated CPU
  • SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

DigitalOcean

General Purpose Droplet · 2 Dedicated vCPU / 8 GB

2vCPU
8 GBRAM
25 GBStorage
4 TBTransfer
  • Dedicated vCPU (100% allocatio...
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Google Cloud

Compute Engine e2-medium · 2 vCPU / 4 GB

2vCPU
4 GBRAM
—Storage
—Transfer
  • Shared vCPU (1.00 sustained)
  • Persistent Disk (billed separa...
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Google Cloud

Compute Engine e2-small · 2 vCPU / 2 GB

2vCPU
2 GBRAM
—Storage
—Transfer
  • Shared vCPU (0.50 sustained)
  • Persistent Disk (billed separa...
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX13 (Germany and Finland)

2vCPU
8 GBRAM
80 GBStorage
20 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX23 (Germany and Finland)

4vCPU
16 GBRAM
160 GBStorage
20 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX33 (Germany and Finland)

8vCPU
32 GBRAM
240 GBStorage
30 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX43 (Germany and Finland)

16vCPU
64 GBRAM
360 GBStorage
40 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX53 (Germany and Finland)

32vCPU
128 GBRAM
600 GBStorage
50 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX63 (Germany and Finland)

48vCPU
192 GBRAM
960 GBStorage
60 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CPX11 (US locations)

2vCPU
2 GBRAM
40 GBStorage
1 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CPX12 (Germany and Finland)

1vCPU
2 GBRAM
40 GBStorage
20 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.