FR/ENRequest a quote
Home/Directus Agency
Agence Directus — Paris

Directus as a backend and headless CMS.The next question: which frontend?

Scroll has been using Directus in its stack for several years—as an API backend, a headless CMS, and an admin layer for business applications. We know how to configure it, scale it, and above all, anticipate the question every project eventually asks: when to build a custom interface on top.

Speak with an expert Request a quote
Directus Architectureself-hosted
DatabasePostgreSQL
expose
DirectusHeadless CMS
REST APIGraphQLAuto-generated admin
Auto back-officeAdministrators
Next.js frontendBusiness users
Path A V1 completePath B front in V2
01 — Why we use it

Why Directus
is part of Scroll’s stack.

Directus isn’t necessarily a tool to replace—it’s a tool to deploy properly. Three concrete reasons why it earns its place in our projects.

01

A full admin back-office in a few hours

Directus automatically generates a complete admin interface from your PostgreSQL schema. Data, roles, permissions, and basic workflows managed without writing a single line of front-end code. For teams that need to administer data quickly, it’s a real advantage.

02

A ready-to-use REST and GraphQL API

The entire data schema is automatically exposed via a documented API. No need to develop an API from scratch—we connect the front-end or third-party tools (n8n, mobile apps, exports) directly to it.

03

Open source, self-hostable, no licensing costs

Directus installs on your infrastructure (OVH, Scaleway, self-hosted). No usage-based billing, no data passing through a third-party SaaS. Sovereignty by default.

02 — The real question

Is the auto-generated back-office enough
for your end users?

The Directus back-office is designed for technical administrators. When your end users—business teams, clients, or field operators—also need to use the interface, the question of a custom front-end arises. This architectural choice is something we frame from the start.

The Directus back-office is sufficient if…
  • Your interface users are administrators or technical profiles
  • Workflows are simple (create, edit, delete entries)
  • You need to launch quickly, and UX is not yet a priority
  • You’re validating a concept before investing in a frontend
A Next.js front-end becomes necessary when…
  • Non-technical users need to use the application daily
  • Business workflows are complex (multi-step, validation, notifications, dashboards)
  • User experience is a key factor for success or internal adoption
  • You’re integrating AI, automations, or differentiated roles with distinct views
03 — Architecture

Two ways to build with Directus
depending on where you stand.

Both lead to the same destination: a robust Directus backend and a custom frontend when needed. What changes is the sequencing, and it depends on your context, not a fixed rule.

Path AFull V1

Full V1 from the start

You know your end users will need a custom interface. We start with the complete architecture: Directus as backend + API, Next.js as frontend. The Directus admin panel remains for administrators, while the Next.js front serves business users.

When to choose this path

Project with identified end users, critical UX for adoption, need for AI integration or automations from launch.

Path BBackend first

V1 backend, V2 frontend

You want to validate the data model and workflows before investing in a frontend. We build the Directus backend + API quickly, and teams use the auto-generated admin panel while validating. The Next.js frontend arrives in V2, without touching the backend.

When to choose this path

MVP or internal tool where UX isn’t yet critical, constrained V1 budget, need to validate logic before building the interface.

They trusted usView our client cases
Ubki
Perfway
Hexa
Art Explora
Bellman
Cabaia
04 — Deployment stack

The Directus stack
as we deploy it.

Directus at the core, surrounded by open-source, self-hostable components. A coherent, sovereign architecture that your teams can take over—from data schema to monitoring.

LayerTool
Headless CMS & APIDirectus (self-hosted)
DatabasePostgreSQL via Supabase or dedicated instance
Custom frontend (full V1 or V2)Next.js, React, TypeScript
AuthenticationDirectus Auth + SSO possible (SAML, OIDC)
File storageDirectus Files + S3 or Supabase Storage
Automationsself-hosted n8n connected to the Directus API
AI & agentsNative LLM (Mistral, OpenAI, Claude) via Directus API
Infrastructure & hostingOVH, Scaleway, Docker, GitHub Actions
MonitoringSentry, PostHog
Stack adaptable to your context: existing infrastructure, GDPR constraints, or sovereignty requirements. Everything is open source and hosted by you.
05 — FAQ

Frequently asked questions

The most common questions we hear during scoping. If yours isn’t here, get in touch!

Both are open-source, self-hostable headless CMS. Directus automatically generates an admin interface from any PostgreSQL schema—its strength for quickly setting up a back office. Payload is more “code first”: it offers greater frontend flexibility and better integration with Next.js when a custom interface is the priority. Scroll uses both depending on the context; we’ll help you choose during scoping.

Yes. The Directus API exposes data in a structured way, making it compatible with an AI layer (RAG, agents, document generation). We build the MCP server or LLM connector that plugs into the Directus API to expose your data to the model in a controlled way.

Directus can serve as a custom back office for workflows that a generic ERP doesn’t cover well. It’s not a turnkey ERP—it’s a flexible foundation on which we build the workflows you need. For simple to moderately complex cases, it’s often a better fit than an oversized ERP.

Yes, particularly from CMS like Strapi, Contentful, or Sanity. Migration involves the data schema and content. The frontend remains unchanged if it’s properly decoupled.

Scroll can handle hosting and maintenance (updates, monitoring, backups). We can also transfer this responsibility to your team or infrastructure—the code and configuration are entirely yours.

A Directus backend with data schema, permissions, and configured API: 2 to 4 weeks. With a custom Next.js frontend in V1: 2 to 4 months, depending on workflow complexity.
Get started

Directus as a backend—let’s scope the frontend question together.

Contact details
20 Rue des Taillandiers
75011 Paris
Response within 24 business hours.