Self-hosted Docker
The same engine, as a container on your servers
Run Rendarium anywhere Docker runs — on-premises, in your cloud account, in an air-gapped network. No data leaves your infrastructure, no usage is metered, and the license is perpetual.
Pull and run
docker pull rendarium/rendarium:latestdocker run -p 8490:8490 \
-e RENDARIUM_LICENSE_KEY= \
# -e RENDARIUM_API_KEYS=rnd_self_... (optional request auth)
rendarium/rendarium:2026.8RENDARIUM_LICENSE_KEY= — leave empty for demo mode (watermarked). Paste your license key to activate. Image tags: 2026.8.1 (exact), 2026.8 (latest patch of that release), latest.
Demo mode, no key
Every operation is available immediately; output documents carry a watermark. Evaluate for as long as you need on real workloads, then paste the key — nothing else changes.
Perpetual license, calendar versioned
Releases are numbered year.month.patch. Your key covers every release up to its horizon, for good: a key with horizon 2027.08 runs 2026.8.1, 2027.3.2 and 2027.8.1 forever. Renewals extend the horizon by 12 months and are never required to keep running what you already have.
Optional API keys for your network
Several internal teams sharing one container? Generate keys inside the image and require them on every request. They are yours: Rendarium never sees them.
docker run rendarium/rendarium genkey
# rnd_self_q3w8e2r7t5y1u9i4o6p0a8s3d7f2g5h1
docker run -p 8490:8490 \
-e RENDARIUM_LICENSE_KEY=... \
-e RENDARIUM_API_KEYS=rnd_self_q3w8...,rnd_self_m4n7... \
rendarium/rendarium:2026.8Keys are compared in constant time against the configured values. With RENDARIUM_API_KEYS unset, authentication is disabled — the usual choice on an isolated internal network.
Editions
| Edition | Who may develop | Where it may run | Price |
|---|---|---|---|
| Developer | One named developer | Unlimited internal deployment | $350 |
| Company | Unlimited developers, one company | Unlimited internal deployment | $750 |
| Company Redistribution | Unlimited developers, one company | Internal deployment + applications shipped to third parties, activated with your key (also known as OEM) | $1,150 |
Frequently asked questions
What happens without a license key?
The container runs in demo mode: the full engine with every operation, but every output document is watermarked. There is no separate trial build and no trial key to request — pull the image and start.
Does the container call home?
No. The license key is a signed document verified offline, once, at container start, with a public key embedded in the image. There is no usage metering, no activation server and no outbound connection required.
What does the calendar version horizon mean?
Releases are versioned year.month.patch, for example 2026.8.1. Your key carries a horizon such as 2027.08: every release whose year.month is at or before the horizon runs with your key, forever. Releases published after the horizon require a renewal, which extends the horizon by 12 months.
Can I use API keys with the container?
Yes, optionally. Set RENDARIUM_API_KEYS to one or more keys generated with the genkey subcommand and every request must present one as a Bearer token. Leave the variable unset on an isolated network and authentication is disabled.
What are the system requirements?
A Linux host (x64 or ARM64) with Docker or any OCI runtime. Recommended: 2 vCPU and 4 GB RAM per container replica for HTML rendering; scale horizontally behind your own load balancer.
Is the hosted API contract the same?
Identical. Same paths, same JSON, same error codes, same client libraries. Only the base URL and the key prefix change (rnd_self_ instead of rnd_live_), and there are no credits in self-hosted mode.