Skip to content

add license replicas clarification #740

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
ComfortablyCoding merged 2 commits into from
Jun 12, 2026
Merged

add license replicas clarification #740

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a72d286
add replicas clarification
JamesW1 Jun 12, 2026
0df5685
fix location
JamesW1 Jun 12, 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
6 changes: 6 additions & 0 deletions content/licensing/1.overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,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:
Expand Down
Loading