Licensing

No activation. No revocation. No clock.

Most PDF vendors sell a licence that phones home. This one does not, and the difference matters most in exactly the places PDF code runs: air-gapped build servers, offline appliances, containers that scale to zero, and machines that will still be running in eleven years.

Activation

There is none

A key is an Ed25519-signed string. Your build verifies it locally and never contacts us — no endpoint to be down, no seat server, and nothing to fail at 3am in a datacentre you do not own.

Revocation

Not possible

Once a key is delivered it verifies forever. We say so plainly because it cuts both ways: it is a guarantee to you, and it means a refund can stop future entitlements and nothing else.

Expiry

Against the build date

A key covers any build released on or before your maintenance end date — forever, including in production. Nothing switches off on a date. The engine never reads the system clock.

Seats

Recorded, not enforced

The seat count rides in the key and no code path checks it. We tell you rather than implying a limit that does not exist.

What maintenance actually buys

A lapsed maintenance plan never breaks a running system. It means the next release is not yours yet. That is the entire consequence, and it is checkable: the test inside the engine compares your key against the date the binary was compiled, not against today.

The editions

Edition	Engine feature mask
Starter	0x81
Lite	0x83
Professional	0x8F · add-ons 0x30
Enterprise	0xCF · add-ons 0x30

Those masks are the engine's own constants, generated from its source rather than typed here. The comparison page says what each bit means in words.

Royalty-free redistribution

Every edition lets you ship the engine inside your product to as many end users as you like, with no runtime fee and no per-deployment reporting. You are buying the right to build with it, once.

Download and try it Pricing