Application hosting

Hosting Directus

Directus provides a data API and content management interface over a database. Its Docker guide distinguishes a small container minimum from a larger recommended starting allocation.

Min vCPU
0.25
Min memory
0.5 GiB
Min storage
Depends on workload

Must have

Hard prerequisites

  • Container CPU allocation of at least 0.25 vCPU
  • At least 512 MB container memory

Recommended

Documented guidance

No further general recommendations are published for this version.

Published starting requirements

These are Directus container resources, not whole-server capacity. The same guide recommends 2 × 1 vCPU and 2 GB containers as a starting point; database and uploads need more.

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

Deploy with

Supported paths

  • Official Docker image with Docker Compose

The host must provide

Runtime

Database
Supported PostgreSQL, MySQL, SQLite or other listed LTS database
Secret
Unique SECRET environment value for token signing

Storage

Persistent data

Persist the database and uploaded files outside the container. Extensions and templates also need persistent volumes when used.

Step by step

Directus deployment outline

  1. Choose a pinned image and database

    Follow the Docker guide and select a supported database version for the Directus release.

    Official instructions
  2. Persist state

    Mount the database, uploads and extension directories as required by your configuration.

    Official instructions
  3. Secure the public endpoint

    Set a unique signing secret, use HTTPS and replace bootstrap administrator credentials.

    Official instructions

Security

Before you go public

  • Set a unique SECRET and protect bootstrap admin credentials.
  • Use HTTPS and keep the pinned image updated.
  • Back up database and uploads together.

Cost

Beyond the server price

  • Budget for database, uploads and backups in addition to the Directus container.
  • The documented minimum is unsuitable as a production capacity guarantee.

Matching plans

Plans with published evidence

Hetzner Cloud

Hetzner Cloud CPX21 (US locations)

3vCPU
4 GBRAM
80 GBStorage
2 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CPX22 (Germany and Finland)

2vCPU
4 GBRAM
80 GBStorage
20 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CPX31 (US locations)

4vCPU
8 GBRAM
160 GBStorage
3 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CPX32 (Germany and Finland)

4vCPU
8 GBRAM
160 GBStorage
20 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CPX41 (US locations)

8vCPU
16 GBRAM
240 GBStorage
4 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CPX42 (Germany and Finland)

8vCPU
16 GBRAM
320 GBStorage
20 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CPX51 (US locations)

16vCPU
32 GBRAM
360 GBStorage
5 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CPX52 (Germany and Finland)

12vCPU
24 GBRAM
480 GBStorage
20 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CPX62 (Germany and Finland)

16vCPU
32 GBRAM
640 GBStorage
20 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.
Hostinger

Hostinger KVM 1 VPS

1vCPU
4 GBRAM
50 GBStorage
4 TBTransfer
  • KVM vCPU (AMD EPYC)
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.
Hostinger

Hostinger KVM 2 VPS

2vCPU
8 GBRAM
100 GBStorage
8 TBTransfer
  • KVM vCPU (AMD EPYC)
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.
Hostinger

Hostinger KVM 4 VPS

4vCPU
16 GBRAM
200 GBStorage
16 TBTransfer
  • NVMe SSD
Meets the documented hard prerequisites

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

  • Container CPU allocation of at least 0.25 vCPUThe published plan value satisfies this requirement.
  • At least 512 MB container memoryThe published plan value satisfies this requirement.

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