Mastering Directus

Mastering Directus

Download PDF
Self-HostingBackend

Summary

Directus has quietly become the first thing I reach for on almost every project, and not just as a headless CMS. Point it at a Postgres database and you get an instant REST and GraphQL API, a genuinely nice admin app your non-technical teammates can actually use, granular permissions, file handling, automation, and realtime, without writing a line of boilerplate. I rarely start an app these days without standing up Directus at some point.

This is the guide I'd hand a competent developer who's never run Directus in anger: how to self-host it properly with Docker and Railway, how to model your data, how to lock it down, and how to ship real apps on top of it.

This is a living document and will be updated as Directus updates

Loading What Directus Actually Is…
Loading Self-Hosting with Docker…
Loading Storage, Caching, and Email…
Loading Deploying to Railway…
Loading Hardening for Production…
Loading Data Modeling…
Loading The API and the SDK…
Loading Access Control: Roles and Policies…
Loading Flows: Automation Inside Directus…
Loading Extensions…
Loading Beyond CRUD: Files, Realtime, and Versioning…
Loading Real-World Patterns and Gotchas…
Loading Schema Migrations: Dev to Prod…
Loading Toolkit: The Production Readiness Checklist…
Loading Toolkit: A Copy-Paste Starter…
Loading Toolkit: Choosing Your Stack…
Loading About Roger…

Do you like my content?

Sponsor Me On Github

Keep reading

Mastering Hermes

Mastering Hermes

Most of this series treats Hermes as the place its ideas land. Building Your Agentic OS pivots to it, Running the Fleet orchestrates on it, Self-Hosting the Agentic Stack deploys it. What none of them do is sit down and cover Hermes itself, the whole thing, every feature, the way I'd walk a competent developer through a tool they've never run in anger. That's this guide. Hermes is Nous Research's open-source, self-hosted agent, the one with a built-in learning loop: it writes its own skills from experience, curates its own memory, searches its own past conversations, and builds a deepening model of who you are across sessions. It installs with one command, runs on a five-dollar box or a GPU cluster, talks to whatever model you point it at, and you can message it from Telegram while it works on a cloud VM. That surface is a lot bigger than the rest of the series has needed to show. So here we go wide instead of deep: install and first contact, the model layer and Nous Portal, the terminal interface, the messaging gateway across six platforms, the six places it can run, the learning loop, context files and personality, tools and toolsets, MCP, scheduled automations, delegation and subagents, the security model, day-two operations, and migrating in from OpenClaw. Where a topic has its own field guide in this series, I point you there instead of repeating it. This is the manual that ties the rest together. _This is a living document and will be updated as Hermes updates._

Read guide
Self-Hosting the Agentic Stack: A Field Guide

Self-Hosting the Agentic Stack: A Field Guide

You can build all of this on someone else's servers. Rent an agent platform, a managed database, a hosted automation tool, pay per task, and watch your data flow through systems you don't control. Or you can run the whole thing on one box you own. This guide is about the second option: standing up a complete agentic stack on a single VPS, where Hermes runs your agents, Directus is your data and content layer, n8n handles the automation and glue, and MCP connects it all to the outside world. One server, no per-task billing, no vendor sitting between you and your own data. This is the flagship that ties the series together. The other guides built the pieces; this one wires them into a system you operate. And we do it the easy way, with Coolify, an open-source self-hosted platform that manages Docker for you, handles TLS and backups, and ships one-click templates for n8n, Directus, and Hermes, so you spend your time on the parts that matter instead of hand-writing infrastructure. We start with why self-hosting is worth it (and honestly when it isn't), get Coolify onto a box, then deploy each layer in turn: the data and content layer, the automation engine, the agent runtime, and the MCP servers that give your agents real tools. Then we wire them into one system and cover the production realities Coolify mostly hands you, TLS, backups, secrets, and the host security and upkeep that stay your job. It builds directly on [The Boring Stack](/guides/the-boring-stack), [Mastering Directus](/guides/mastering-directus), and [Mastering n8n](/guides/mastering-n8n), plus the agent guides in this series. By the end you'll have the whole stack running on hardware you control, doing real work, on your terms. _This is a living document and will be updated as the tools and patterns evolve._

Read guide