License and Enterprise features
TrayPage's licensing (core is MIT, ee/ is commercial) and how to enable Enterprise features with a license key.
License
| Scope | License |
|---|---|
The core (everything except ee/) | MIT |
The ee/ directory | TrayPage Enterprise License (commercial) |
- The core is MIT licensed. You can use, modify, and redistribute it freely.
ee/contains the Enterprise feature code, and its source is public. You are free to read and run it for development and evaluation, but using it in production requires a license key (or the matching plan on tray.page).- Creating pages, managing versions, publishing, MCP, the CLI, comments, revision instructions, workspaces and projects, basic roles, sharing settings, the shared page entry point, and sign-in with providers such as Google are all part of the core (MIT).
- A feature may move from
ee/into the core, but never from the core intoee/.
Note that the license text of ee/ is currently a draft and not the final version.
Enabling Enterprise features with a license key
There is a single build (Docker image and Workers bundle), and it already includes ee/. Setting a license key turns on the Enterprise features the key includes. You do not need to swap or reinstall anything.
| State | Behavior |
|---|---|
| No key | Community. All Enterprise features are disabled |
| Key set | The features in the key are enabled for every workspace in the instance |
How to set it:
- Docker / VPS: write
TRAYPAGE_LICENSE_KEY=tp1.…in.envand apply it withdocker compose up -d - Cloudflare: add the secret
TRAYPAGE_LICENSE_KEY
About keys:
- A key carries the company name, the list of enabled features, the expiry date, and more, and it is signed.
- The signature is verified inside your server, offline. No check is sent anywhere, so it works in closed networks.
- When a key expires, your data is not deleted. After a grace period (30 days), only the Enterprise features are disabled.
To obtain a key or ask about plans, contact the operator (8d inc).