Directus
Deploy Directus on Polyer to manage content and data through an admin app with generated REST and GraphQL APIs. This template runs one directus/directus:11 service with SQLite; the database file, uploads and extensions live on its volume. Review the admin sign-in and the CORS origin input before deploying.
What you can use it for
- Serve content to a website or mobile app through a headless CMS API.
- Give editors an admin app to manage structured content and media files.
What this template creates
directus
directus/directus:11Public endpoint Persistent volume
Configuration to review
These inputs are exposed by the template. The deployment form identifies required values and validates them before creating services.
| Input | Environment key |
|---|---|
| Cors origin | CORS_ORIGIN |
How to deploy
- Select Configure deployment and sign in or create an account.
- Choose a new or existing project and select an available region.
- Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
- Inspect deployment logs, complete the application's setup and test its endpoints before production use.
Operating this application
- Sign in with admin@example.com and the generated admin password from the service variables, then change both in Directus, because those variables only create the first administrator.
- Back up the SQLite database together with the uploads and extensions directories and test a restore. Keep the generated KEY and SECRET variables, which Directus uses to identify the project and sign tokens.
- Set the CORS origin input to the origin of any browser app that calls the API. Back up before redeploying, since the directus:11 tag can move to a newer 11.x release that migrates the database on startup.
Hosting costs
CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.
Review prices and estimate resource costsSource and validation
This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.
Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.
Editorial content reviewed: 2026-10-10
