diff --git a/content/licensing/3.open-innovation-grant.md b/content/licensing/3.open-innovation-grant.md
index 7a508c89..2291336e 100644
--- a/content/licensing/3.open-innovation-grant.md
+++ b/content/licensing/3.open-innovation-grant.md
@@ -47,6 +47,14 @@ A license binds to your project and `PUBLIC_URL`, not to a container, IP address
 
 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](/licensing/overview#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.