[metadata]
description: How the Open Innovation Grant works, what it includes, and how its activations apply to multiple environments, CI pipelines, and database restores.
og:description: How the Open Innovation Grant works, what it includes, and how its activations apply to multiple environments, CI pipelines, and database restores.
og:image: https://og.directus.com/template/docs?v=1&title=Open+Innovation+Grant&description=How+the+Open+Innovation+Grant+works%2C+what+it+includes%2C+and+how+its+activations+apply+to+multiple+environments%2C+CI+pipelines%2C+and+database+restores.&breadcrumb=Licensing&sig=9f31ee96db2e476ff3061a0b477b4a3545e2e33601c9f661b17f8a716c2b853d
og:title: Open Innovation Grant
robots: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
twitter:card: summary_large_image
viewport: width=device-width, initial-scale=1

[document-links]
/docs/
AI Assistant: Query Your Data, Update Content + More: https://directus.com/ai
API: /docs/api
Activations and project bindings: /docs/licensing/overview#activations-and-project-bindings
Apply for the Open Innovation Grant: https://directus.com/oig
Check out our product changelog.: /docs/releases/changelog
Cloud Policies: https://directus.com/cloud-policies
Docs MCP Server Connect Claude, Cursor, VS Code, or any MCP-compatible client directly to the Directus documentation.: /docs/mcp-help
Docs: /docs/getting-started/overview
Edit this page: https://github.com/directus/docs/edit/main/content/licensing/3.open-innovation-grant.md
Join our Community Platform.: https://community.directus.com
License: https://directus.com/license
Licensing overview: /docs/licensing/overview
Licensing: /docs/licensing/overview
Managing Your License: /docs/licensing/overview#managing-your-license
Need a license? Contact Sales.: https://directus.com/contact
Need help? Contact Support.: https://directus.com/support
Open Innovation Grant: /docs/licensing/open-innovation-grant
Overview: /docs/licensing/overview
PUBLIC_URL configuration: /docs/configuration/general
Pricing: https://directus.com/pricing
Privacy: https://directus.com/privacy
Replicas and Horizontal Scaling: /docs/licensing/overview#replicas-and-horizontal-scaling
Star on GitHub: https://github.com/directus/directus
Telemetry Exactly what usage data Directus collects, when it is sent, and how to disable it.: /docs/licensing/telemetry
Telemetry: /docs/licensing/telemetry
Terms: https://directus.com/terms
Tutorials: /docs/tutorials
deactivate a license: /docs/licensing/overview#deactivating-a-license
https://bsky.app/profile/directus.io
https://directus.chat/
https://directus.com
https://github.com/directus/directus
https://x.com/directus

[content]
Open Innovation Grant
AI Assistant: Query Your Data, Update Content + More
Docs
API
Tutorials
Licensing
Search ⌘K
Ask AI
Licensing
Personalize
Licensing
Overview
Telemetry
Open Innovation Grant
Menu
On this page
/
Licensing
Open Innovation Grant
Favorite
Copy page
How the Open Innovation Grant works, what it includes, and how its activations apply to multiple environments, CI pipelines, and database restores.
The
Open Innovation Grant (OIG)
provides free commercial use of Directus for entities with less than $5M in annual revenue and fewer than 50 employees. Eligibility is assessed based on the legal entities whose representatives log into the Directus Studio. Full terms are set out in the grant usage agreement.
Apply for the Open Innovation Grant
to receive a license key. Once you have it, follow
Managing Your License
to apply it to your instance.
This page covers the questions that come up most often once you have an OIG license: what it includes, how its activations work across environments, and how it behaves in CI pipelines and database restores.
The grant covers free use of
self-hosted
Directus. Directus Cloud is a separate managed offering; eligible entities can run on Cloud for a flat hosting fee. See
Pricing
for current rates.
Haven't Received Your Key?
License keys are delivered by email. If your key has not arrived, check your spam or junk folder, as grant emails are often filtered there.
What's Included
An OIG license is not a trial or a reduced edition. It unlocks the entitlement-gated features most projects need, including custom access policies and SSO, with no caps specific to the grant. A small number of capabilities are reserved for higher commercial tiers.
The main thing to plan around is the number of activations, covered below.
Activations
Each OIG license key includes
5 activations
. An activation binds the key to one instance at its
PUBLIC_URL
on first use, and that binding authenticates all later revalidation requests for the instance. See
Activations and project bindings
for the full mechanics and the deactivation flow.
Five activations are intended to cover the distinct environments of a single project, such as local, dev, staging, and production, with one spare. Because a license binds to your
PUBLIC_URL
and project database rather than to a container or IP address, you do not consume a separate activation for each replica.
Always
deactivate a license
before destroying the instance it is bound to.
If you wipe the database or drop the container without deactivating first, the activation stays bound on the licensing service and keeps counting against your 5.
Multiple Projects and Agencies
A single key and its 5 activations are meant for one project across its environments. If you build and host Directus for multiple clients or run several distinct projects, apply for a separate OIG key per project. Each key receives its own 5 activations, so a project's environments never compete with another project's for slots.
Replicas and Horizontal Scaling
A license binds to your project and
PUBLIC_URL
, not to a container, IP address, or instance identity. In a horizontally scaled deployment, every replica shares the same project database and the same
PUBLIC_URL
, so a single key and a single activation cover the entire cluster rather than each container.
Set the license through the
LICENSE_KEY
environment variable at the service or task level so that every replica inherits the same value automatically. New containers added by autoscaling pick up the license on start with no manual setup or per-container retrieval. See
Replicas and Horizontal Scaling
for more detail.
Renewal and Expiration
An OIG license is valid for one year from the date it is issued, and its expiration date is shown under
Settings > License
in the Studio. The grant can be renewed year on year, so eligible entities can keep running Directus beyond the first year.
An automated renewal process is being established and will be available before your renewal date. You do not need to take any action ahead of it.
After a license reaches its expiration date, a 30-day grace period applies, giving you time to complete renewal. During this grace period, Directus shows a notice in the Studio.
Continuous Integration and Ephemeral Environments
CI pipelines are the most common way to exhaust an OIG license's activations. The problem comes from fully ephemeral setups: if a pipeline run tears down both Directus and its database and recreates them from scratch, each run generates a new project and a new binding, consuming an activation every time. Because old activations are not released when the throwaway instance disappears, five runs exhaust the limit and later runs fail with an activation limit error.
To validate licensed features (such as SSO and OIDC) in CI without burning through activations, use one of the following approaches:
Reuse the same database and
PUBLIC_URL
across runs.
If runs share a persistent project database and a constant
PUBLIC_URL
, they reuse a single binding and consume only one activation in total. Persist the database between runs rather than recreating it each time.
Validate against a stable instance.
Point feature tests at a long-lived dev or staging instance that holds its own activation, instead of spinning up a fresh licensed instance per run.
Run ephemeral pipelines on the core tier.
Leave the license out of throwaway runs entirely and reserve licensed-feature validation for a persistent environment. The core tier runs without a license and without consuming activations.
Use a commercial license
sized to your workload if none of the above fit your pipeline.
Activation-based licensing is designed for stable, long-lived environments. We know fully ephemeral, per-run CI is a different pattern, and we are actively exploring ways to support it that work for both our users and the licensing model.
Restoring Database Dumps
Dumping a database and restoring it elsewhere (for example, copying production into a local or dev environment) is a common workflow, and how it interacts with your license depends entirely on the
PUBLIC_URL
of the instance you restore into.
A dump carries the project's license binding with it. What happens on the next boot is:
Restoring into the same environment
(same project and same
PUBLIC_URL
, such as recovering a backup of production back onto production) revalidates the existing binding. It does not create a new activation, so restoring a backup into its own environment is free.
Restoring into a different environment
(a different
PUBLIC_URL
, such as production into local) does not match the original binding. The instance still starts as licensed and keeps running while its current validation holds, but because it cannot revalidate under the new URL, it eventually falls back to the core tier once that validation expires.
If you want a long-lived local or secondary copy running at the full tier, dedicate one of your 5 activations to it and activate the license under that environment's own
PUBLIC_URL
. Always restore into the same
PUBLIC_URL
for that environment. Changing the URL on each restore registers a new binding every time and consumes additional activations.
Next Steps
Licensing overview
for license keys, statuses, and the deactivation flow.
Telemetry
for what usage data Directus collects.
PUBLIC_URL
configuration
for setting the value that licensing binds to.
Get once-a-month release notes & real‑world code tips...no fluff. 🐰
Telemetry
Exactly what usage data Directus collects, when it is sent, and how to disable it.
Docs MCP Server
Connect Claude, Cursor, VS Code, or any MCP-compatible client directly to the Directus documentation.
On this page
On this page
Haven't Received Your Key?
What's Included
Activations
Multiple Projects and Agencies
Replicas and Horizontal Scaling
Renewal and Expiration
Continuous Integration and Ephemeral Environments
Restoring Database Dumps
Next Steps
Was this helpful?
Edit this page
Star on GitHub
Need help? Contact Support.
Join our Community Platform.
Check out our product changelog.
Need a license? Contact Sales.
Cloud Policies
License
Terms
Privacy
© 2026 Monospace Inc
I
