Directus Hosting

Turn SQL databases into managed APIs, content collections, workflows, and admin dashboards.

Order now No setup fees
  • One click deploy
  • 2 GB RAM Memory needed
  • 25 GB Disk Space Needed
  • From 5 € Price

Tech

Docker image
directus/directus:latest
Default port
8055
Database
postgres

How Directus works

Directus reads a SQL database schema and presents its tables as collections and fields inside a browser-based Data Studio. Administrators can design or extend a data model, create relationships, define roles and permissions, and expose records through generated REST and GraphQL APIs. Applications consume those APIs while editors work through forms, lists, dashboards, and other studio views.

Files can be uploaded into configured storage and referenced from records. Flows automate tasks or business logic in response to events, schedules, webhooks, or manual actions. Insights dashboards visualise selected data, while extensions can add interfaces, displays, endpoints, hooks, and other project behaviour.

Key Directus features

Granular permissions can control collections, fields, actions, and item-level access for each role or policy. The API and Data Studio use the same project model, reducing the gap between editor workflows and application development. Filters, relations, validation, presets, and translations help adapt content or operational data to different teams.

Directus is flexible because it exposes a database rather than imposing one narrow website structure. That also means data modelling decisions matter: poorly chosen relations, permissions, indexes, or flows can create security and performance problems that the visual interface cannot resolve automatically.

Directus vs Contentful

Directus is a self-hosted data platform that combines a visual studio, generated APIs, permissions, files, automations, and dashboards over PostgreSQL. Contentful is a provider-operated content platform with API delivery, managed environments, marketplace integrations, content orchestration, personalisation, and broader digital-experience services.

Contentful may suit organisations that want vendor-operated infrastructure and an established managed content ecosystem. Directus is more appropriate when the database, API service, extensions, and deployment need to remain under the operator's control, provided the team can design and govern its own data model.

Who uses Directus

Development teams use Directus as a backend for websites, mobile applications, portals, and internal tools. Agencies create reusable content models for customer projects, while operations groups build structured data interfaces without developing every form and permission screen from scratch.

The platform is not a substitute for database design or application security review. Roles, public permissions, API tokens, flows, file access, and schema changes should be tested before exposing a project to external users.

Self-hosting Directus: requirements and cost

Resource use grows with collections, fields, API requests, filters, relations, file uploads, transformations, flows, dashboards, and concurrent editors. PostgreSQL with spatial extensions stores the project data and Directus system records, while Redis supports caching. PostgreSQL is included but unmanaged, and its memory is outside the exported application minimum.

AvaHost recommends Plan 3 at €10 for Directus after the database adjustment. One-click deployment, a custom API domain, automated HTTPS, automatic application updates, and scheduled backups are included. Application email is disabled, so user invitations, registered-email verification, password-reset links, and email notifications cannot be delivered from the hosted project.

F.A.Q

  • Directus starts at €10 on Plan 3 after adding capacity for PostgreSQL. The plan covers the Data Studio, REST and GraphQL APIs, Redis cache, files, and ordinary flow execution. Schema size, API traffic, filters, transformations, uploaded assets, automations, dashboards, and concurrent editors determine when more resources are needed.

  • AvaHost provisions PostgreSQL with spatial extensions and connects Directus to it. Project records, users, roles, permissions, flows, and system metadata depend on that database. PostgreSQL is included but unmanaged, so schema changes, database records, and persistent files should be reviewed together during updates, migration, or recovery.

  • The Data Studio and generated APIs can use a custom domain with automated HTTPS after DNS points to the hosted service. Configure applications against the final address, then test authentication, REST calls, GraphQL queries, file URLs, webhooks, and flow callbacks. Public permissions should be reviewed before exposing any collection.

  • Application email is disabled on AvaHost. Directus invitation links, registration-verification messages, password-reset emails, and email notifications cannot be sent from the hosted project. The initial administrator is created during deployment, but additional user onboarding and recovery need a controlled non-email process that preserves role and permission review.