Skip to content

Specify breaking changes for licensing #733

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JamesW1 merged 3 commits into from
Jun 11, 2026
Merged

Specify breaking changes for licensing #733

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d046331
specify breaking changes
ComfortablyCoding Jun 11, 2026
85b0576
Apply suggestion from @JamesW1
JamesW1 Jun 11, 2026
fc38b2b
Merge branch 'main' into improve-breaking-change-notes
JamesW1 Jun 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions content/releases/3.breaking-changes/3.version-12.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,20 @@ Jump to:

### License Enforcement

Directus 12 introduces active license enforcement. Self-hosted instances run on the **core tier** by default. Higher limits and additional features are unlocked by configuring a license. See [Licensing](/licensing/overview) for a full explanation.
Directus 12 introduces active license enforcement. Self-hosted instances run on the **Core tier** by default. Higher limits and additional features require a valid license. See [Licensing](/licensing/overview) for a complete overview.

This change affects instances previously using features that now require a license, including:

- **SSO** — SSO login will no longer work. Users who authenticate through SSO will be unable to log in and must be converted to email and password users to regain access.
- **Custom permission rules** — custom rules on access policies will be ignored.
- **Custom or self-hosted LLMs** — connections to custom LLMs will no longer work.
- **AI Translations** — AI-powered translations will no longer be available.

::callout{icon="i-lucide-info"}
Enforcement is immediate on new instances. Instances upgrading to Directus 12 get a 30-day [grace period](#post-upgrade-grace-period) from the time of upgrade, after which these are enforced unless a license that enables them is configured.
::

If your instance uses any of these features, add a license that includes them to continue to do so. If your instance uses only Core tier features, no action is required.

#### Post-upgrade Grace Period

Expand All @@ -26,7 +39,7 @@ The grace period exists to ensure uninterrupted service for existing customers w

If you are not an existing customer and do not intend to add a license, reduce usage to within core limits before the grace period ends. Note that free commercial use may be available through the [Open Innovation Grant](https://directus.com/oig).

If the grace period ends with usage still above core limits, the resolution flow is triggered on next admin login and certain APIs are locked down until resolved.
If the grace period ends without resolution, the resolution flow is triggered on next admin login and certain APIs are locked down. To resolve, either add a license that covers your usage and features, or bring usage and feature use within Core tier limits.

#### Locked-Down Behavior

Expand Down
Loading