Directus sits on top of a SQL database and turns it into an API and an admin app. That is why people hire for it: they have a database already, or need an internal tool and a content API from one schema. A Directus developer is as much a database engineer as a CMS person, and the work often looks like data platform work.
What a Directus developer does for you
- Putting Directus in front of an existing PostgreSQL, MySQL or similar database without rewriting the schema.
- Designing collections, relations and fields so the data model, not only the admin screens, stays sound.
- Configuring roles, policies and permissions, including row-level filters for multi-tenant data.
- Building Flows for automation, plus custom endpoints, hooks and interfaces as extensions.
- Building internal tools and back offices where the admin app is the product.
- Connecting a frontend through the REST or GraphQL API, and moving content in from another CMS.
Checks before we propose a Directus engineer
- Candidates think in indexes, foreign keys and migrations. Directus exposes your schema, so schema mistakes become API mistakes.
- They test permission rules as each role, since a filter that looks right in the app can leak rows through a related collection.
- They know how to snapshot and apply the schema between environments, and what does not travel with it.
- They write and package extensions against the Directus SDK, and know how an upgrade can break them.
- They can explain the Directus licence terms and the choice between self-hosting and the vendor’s cloud.
We ask candidates to review a schema and say which relations will hurt the API.
Starting on a Directus project
Week one: connect to a copy of the database, inspect which tables Directus should expose and which it should not, and map the roles in use. Week two: a short written plan with the permission model, the environments and the schema workflow. Then the first collections, roles and an automation or endpoint in staging, ready for your team to test with real data. You keep the schema snapshot in git throughout.
How the engagement works
A single Directus developer fits a defined backlog. IT staff augmentation works when your data or platform team needs another pair of hands. If the project also needs a frontend and infrastructure, a dedicated team covers all of it. Rates for different roles and levels sit between $50 and $150 per hour, quoted after an intro call. Work begins once we have matched the person to your database and stack.
Directus fit: where it works and where it does not
Directus fits when the database is the center of the project: an internal tool, a data catalogue, or a content API on top of a schema you already trust. It can be self-hosted or run in the vendor’s cloud. It is a weaker fit for marketing sites where editors expect a page builder and live preview, and you should read the licence terms before you build a commercial product on a self-hosted copy.
Typical stack around Directus
Directus usually runs as a Node service next to a PostgreSQL or MySQL database, with object storage for files and a reverse proxy in front. Frontends are Next.js, Nuxt or Astro sites reading the API, or internal apps built on the same endpoints. The developer owns environments and backups too, since the database is the product and a bad migration there costs more than a bad deploy.
When the scope is bigger
For a full build, see our Directus services. If you are deciding between platforms, Strapi against Directus compares model-first against database-first. You can also browse other headless CMS developers.
