## Summary AI Governance is now included with Premium licenses instead of being sold as a separate per-user add-on. This updates `docs/` to describe the new packaging, removes "Add-On" from AI Governance references, and refreshes the editions architecture diagram. ## Changes - **`docs/ai-coder/ai-governance.md`**: title is now "AI Governance"; rewrote the licensing statements (previously "a separate, per-user license... not included with a Premium subscription and must be purchased separately") to state it is included with Premium. The usage-pool section now attributes the shared Agent Workspace Build pool to Premium deployments. - **Repeated admonition (28 files under `ai-coder/agent-firewall/` and `ai-coder/ai-gateway/`)**: replaced "requires the AI Governance Add-On / as of Coder v2.32, deployments without the add-on..." with "is part of AI Governance, which is included with a Premium license." The v2.32 add-on gate no longer applies; the gate is now Premium vs. Community. - **`docs/ai-coder/index.md`, `security.md`, `tasks.md`, `usage-data-reporting.md`, `admin/licensing/index.md`, `install/releases/esr-2.29-2.34-upgrade.md`, `ai-gateway/ai-gateway-proxy/setup.md`, `ai-gateway/clients/claude-code.md`**: reworded add-on references to Premium inclusion. - **`docs/manifest.json`**: nav title "AI Governance Add-On" → "AI Governance", updated two descriptions, and swapped the 25 `"state": ["ai governance add-on"]` badges to `["premium"]` so the sidebar badge reads "Premium" instead of "AI Governance Add-On". - **`docs/images/single-region-architecture.png`**: refreshed the diagram in the **Community and Premium editions** tab on [Architecture](https://coder.com/docs/admin/infrastructure/architecture). Also deleted the unreferenced `single-region-architecture.svg` copy. ## Follow-ups outside this PR - The `"ai governance add-on"` doc-state badge is defined in `coder/coder.com` (`src/utils/docs/state.ts`). After this merges, no manifest entry uses that key, so it becomes dead config and can be removed there. - `enterprise/coderd/license/license.go:564-572` still warns admins that "The AI Governance add-on is required to use AI Gateway." That backend string will contradict these docs once shipped. ## Verification - `pnpm run lint-docs`: 0 errors across 504 files - `make lint/emdash`: clean - Vale on the changed Markdown files: 0 errors; remaining warnings are pre-existing gerund headings on untouched lines - `docs/manifest.json` validated as JSON - Confirmed the deleted SVG had no references anywhere in the repo --- PR generated with Coder Agents on behalf of @mattvollmer.
2.5 KiB
Licensing
Some features are only accessible with a Premium license, including AI Governance. See our pricing page for more details. To try paid features, you can request a trial or contact sales.
Offline license validation
Coder license keys are signed JWTs that are validated locally using cryptographic signatures. No outbound connection to Coder's servers is required for license validation. This means licenses work in air-gapped and offline deployments without any additional configuration.
Adding your license key
There are two ways to add a license to a Coder deployment:
Coder UI
-
With an
Owneraccount, go to Admin settings > Deployment. -
Select Licenses from the sidebar, then Add a license:
-
On the Add a license screen, drag your
.jwtlicense file into the Upload Your License section, or paste your license in the Paste Your License text box, then select Upload License:
Coder CLI
-
Ensure you have the Coder CLI installed.
-
Save your license key to disk and make note of the path.
-
Open a terminal.
-
Log in to your Coder deployment:
coder login <access url> -
Run
coder licenses add:-
For a
.jwtlicense file:coder licenses add -f <path to your license key> -
For a text string:
coder licenses add -l 1f5...765
-
FAQ
Find your deployment ID
You'll need your deployment ID to request a trial or license key.
From your Coder dashboard, select your user avatar, then select the Copy to clipboard icon at the bottom:
How we calculate license seat consumption
Licenses are consumed based on the status of user accounts. Only users who have been active in the last 90 days consume license seats.
Consult the user status documentation for more information about active, dormant, and suspended user statuses.



