Licensing
Perpetual licenses with a calendar-version horizon, three ways to renew, and a clear policy for keys.
Two products, two kinds of credentials
The hosted API is a subscription with credits; you authenticate with an API key created in the portal. The self-hosted container is a perpetual license; you activate it with a license key delivered at purchase, and may optionally protect it with API keys of your own. The two never mix: a license key is a signed document verified offline, an API key is a random secret verified on every request.
Calendar versioning and the horizon
Releases are numbered year.month.patch — 2026.8.1 is the first build of the August 2026 release. Every license key carries a horizon, a year.month such as 2027.08. The rule is a single comparison, done offline at container start:
A release runs with your key if its year.month is at or before the horizon — and it keeps running forever. Releases published after the horizon start in demo mode.
So a key bought on 27 August 2026 has horizon 2027.08 and runs 2026.8.1, every release of the following twelve months, and any patch of those releases published later. Nothing you already run ever stops working; renewing only matters when you want a newer release.
Editions
| Edition | Developers | Deployment | Redistribution |
|---|---|---|---|
| Developer | One named developer | Unlimited, inside your organization | No |
| Company | Unlimited, one legal entity | Unlimited, inside your organization | No |
| Company Redistribution | Unlimited, one legal entity | Unlimited, inside your organization | Yes — ship applications embedding Rendarium to third parties, activated with your key, royalty-free. Known historically as “OEM”. |
Redistribution means your customers run your application with Rendarium inside it. Exposing the Rendarium API itself to them as a product needs a separate agreement — write to sales@rendarium.com.
Renewals — three paths, in order of price
Each renewal extends the horizon by 12 months from the payment date and delivers a new key; old keys stay valid for the releases they already cover.
- Auto-renewal (default, lowest price) — a yearly subscription. At every charge a new key with the extended horizon is generated and emailed automatically. Cancel any time; the last key you received keeps its horizon.
- One-time renewal — no subscription. Bought manually whenever you want while the license is within its horizon or shortly after it. A little more expensive than the auto-renewal rate.
- Late reactivation — for a license expired less than 12 months ago. Restarts the auto-renewal subscription with a higher first installment; every following installment is charged at the standard auto-renewal rate.
More than 12 months after expiry the license cannot be reactivated; a new license at full price is required.
| Edition | License | Auto-renewal / yr | One-time renewal | Late reactivation |
|---|---|---|---|---|
| Developer | $350 | $140 | $175 | $250 then $140 |
| Company | $750 | $300 | $375 | $540 then $300 |
| Company Redistribution | $1,150 | $460 | $575 | $830 then $460 |
Example
Company license bought 1 March 2026, horizon 2027.03. Auto-renewal charged 1 March 2027 → new key, horizon 2028.03. The customer cancels in 2028: release 2028.3.x and every earlier release run forever; 2028.4.1 starts in demo mode. Returning in December 2028 (nine months after expiry) → late reactivation, horizon 2029.12. Returning in June 2029 (fifteen months) → new license.
Buying and linking licenses
Licenses are bought at checkout without a portal account; the key arrives at the order email. Optionally, link your purchase email to a portal account from the Licenses page to view keys, horizons and renewal options in one place and to reissue a key. Reissued keys have the same edition and horizon; because validation is offline, previous keys are never revoked.
Hosted API keys
- Keys are shown in full once, at creation. We only store a hash; lost keys are revoked and replaced, never recovered.
- Up to 10 active keys per account, each with a label and its own usage breakdown. All keys draw from the same credit balance; revoking a key does not change the balance.
- Keep keys out of public repositories, client-side code and logs. Rotate a key by creating a new one, updating your configuration, then revoking the old one.
Self-hosted API keys
Generated inside your container (docker run rendarium/rendarium genkey) and listed in RENDARIUM_API_KEYS. They are entirely yours: Rendarium never sees them, and they are not tied to your license.
The full legal text is the End User License Agreement; hosted use is governed by the Terms of Service.