LumasHow licensing works, and why there is no activation step
The engine verifies a key locally. There is no server, no activation, and nothing to go down.
People arrive at this page looking for the activation instructions. There are none, and the absence is deliberate.
A LumasPDF key is a signed blob. Your application passes it to the engine; the engine verifies the signature against a public key compiled into the binary and reads the fields out of it. That happens in microseconds, in your own process, with no socket involved.
What follows is worth listing, because it is why the design was chosen. Air-gapped builds work. Builds behind a corporate proxy work. A build running during an outage at our end works, because our end is not involved. There is no activation count to exhaust when you rebuild a CI image for the two-hundredth time. And nothing about your usage is visible to us, because nothing is sent.
The trade-off is honest too: because there is no server, there is no way to recall a key that has already been delivered. Our refund policy says so in those words rather than implying a switch we do not have.
Last updated 2026-09-09.
Related
- What maintenance covers Maintenance is a window over build dates. It never affects software you have already shipped.
- Seats are recorded, not enforced The seat count rides in the key. No code counts installations, and the portal register is yours to keep.