trial and licensing
Evaluate for 30 days. Then decide.
A self-hosted deployment starts a 30-day full-feature evaluation the first time it runs. When you buy, you activate a signed key on your own server. There is no licence server to call and nothing to phone home.
the evaluation
30 days of the whole product
Not a limited edition with the useful parts removed. The same build a paying customer runs.
Starts by itself
No key, no sign-up, no card. Install the bundle, leave LICENSE_KEY empty, and the clock starts on first use.
Nothing is crippled
Every feature is on. You are evaluating the real product, which is the only kind of evaluation worth anything.
Counted on the server
The clock is a server timestamp written once. Changing a browser clock, timezone or cookie does not move it, and restarting the container does not reset it.
Visible, not hidden
Administration → License shows the state and the exact days remaining, and warns as expiry approaches.
Survives a restore
Trial state lives in the database. A backup and restore preserves it rather than quietly granting another month.
Ends predictably
No surprise lockout, no deletion, no countdown theatre. Read on for exactly what expiry does.
failure behaviour
What the deployment does in every state
Including the ones vendors normally leave out.
| State | When | Behaviour |
|---|---|---|
| Trial | No licence, within 30 days of first use | Full access to every feature. |
| Licensed | A valid signed licence | Full access to the entitlements the licence grants. |
| Grace | Up to 7 days past a licence's expiry | Still fully working. The console warns you to renew. |
| Expired | Trial elapsed, or a licence past its grace window | Read-only. You can log in, read, export and activate. Your data is preserved. |
| Offline | No network, or we are unreachable | No effect. Verification is local, so a valid licence keeps working. |
What “read-only” means, precisely
Write operations — creating or running work, changing settings — are refused with a clear message until a licence is activated. Reading, logging in, exporting your data and activating a licence all keep working. Nothing is deleted. Activating a valid licence restores full access immediately, with no restart and no data migration.
activation
How a licence is applied
Two steps, and neither of them needs us to be reachable.
- 01
Buy, and receive a signed key
A licence is a signed statement of what you are entitled to: edition, expiry, seat limit, repository limit and features.
- 02
Paste it into Administration → License
The server checks the RSA signature and the expiry locally, then applies it immediately — no restart, and it persists across restarts.
Why it works offline
Your deployment holds only the public verification key. The private signing key never leaves our issuing system and is never present in a customer image. Verification is therefore a local signature check, which is why an air-gapped server can activate a licence and why our availability is irrelevant to yours.
It also means the entitlements cannot be edited. Changing the key text to extend an expiry or add seats breaks the signature, and the key is refused.
Renewal is the same action: paste the new key, and the new entitlement replaces the old one immediately. No data is affected.
questions
Licensing, answered
start with the trial
No key required to begin
Install the bundle and the 30-day evaluation starts by itself. Buy a licence when it has earned it.