Must have
Hard prerequisites
- Container CPU allocation of at least 0.25 vCPU
- At least 512 MB container memory
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
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
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
-
Choose a pinned image and database
Follow the Docker guide and select a supported database version for the Directus release.
Official instructions -
Persist state
Mount the database, uploads and extension directories as required by your configuration.
Official instructions -
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
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.
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.
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.
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.
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.
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.
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.
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.
- Container CPU allocation of at least 0.25 vCPUThe plan does not publish this runtime or configuration detail.
- At least 512 MB container memoryThe plan does not publish this runtime or configuration detail.
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.
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.
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.
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.