From a72d28689177bb642fbacb73646051483c890a69 Mon Sep 17 00:00:00 2001 From: James White Date: Fri, 12 Jun 2026 18:39:59 +0100 Subject: [PATCH 1/2] add replicas clarification --- content/licensing/1.overview.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/licensing/1.overview.md b/content/licensing/1.overview.md index 3addec42f..7a400b4aa 100644 --- a/content/licensing/1.overview.md +++ b/content/licensing/1.overview.md @@ -109,6 +109,12 @@ On first use, a license key creates an **activation** on the Directus licensing A single license key may be activated against multiple instances at different `PUBLIC_URL`s, depending on your license. For example, an [Open Innovation Grant](https://directus.com/oig) license supports up to **5 activations**, intended to cover the distinct environments of a single project (such as local, dev, staging, and production). +### 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 license key covers the entire cluster rather than each individual container. + +Set the license through the `LICENSE_KEY` (or `LICENSE_TOKEN`) environment variable at the service or task level so that every replica inherits the same value automatically. New containers spun up by autoscaling pick up the license on start without any manual setup or per-container retrieval. + ### Deactivating a License Deactivating a license frees its activation on the licensing service so the binding can be reused. From 0df56859495ccbd3e3d45644ec47d7223093ab6b Mon Sep 17 00:00:00 2001 From: James White Date: Fri, 12 Jun 2026 18:41:23 +0100 Subject: [PATCH 2/2] fix location --- content/licensing/1.overview.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/licensing/1.overview.md b/content/licensing/1.overview.md index 7a400b4aa..ad0143123 100644 --- a/content/licensing/1.overview.md +++ b/content/licensing/1.overview.md @@ -109,12 +109,6 @@ On first use, a license key creates an **activation** on the Directus licensing A single license key may be activated against multiple instances at different `PUBLIC_URL`s, depending on your license. For example, an [Open Innovation Grant](https://directus.com/oig) license supports up to **5 activations**, intended to cover the distinct environments of a single project (such as local, dev, staging, and production). -### 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 license key covers the entire cluster rather than each individual container. - -Set the license through the `LICENSE_KEY` (or `LICENSE_TOKEN`) environment variable at the service or task level so that every replica inherits the same value automatically. New containers spun up by autoscaling pick up the license on start without any manual setup or per-container retrieval. - ### Deactivating a License Deactivating a license frees its activation on the licensing service so the binding can be reused. @@ -134,6 +128,12 @@ If you change the `PUBLIC_URL` of an existing instance — for example, when mig To reuse the same license on the new URL without exceeding your license's activation limit, deactivate the license on the old instance **before** bringing the new one online. +### 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 license key covers the entire cluster rather than each individual container. + +Set the license through the `LICENSE_KEY` (or `LICENSE_TOKEN`) environment variable at the service or task level so that every replica inherits the same value automatically. New containers spun up by autoscaling pick up the license on start without any manual setup or per-container retrieval. + ## Resolution Flow If your instance exceeds its entitlements — for example, after downgrading a plan — the Studio surfaces a **Resource Resolution** screen for admins. This screen lists each entitlement that requires action: