LumasWhat maintenance covers
Maintenance is a window over build dates. It never affects software you have already shipped.
Maintenance buys you newer builds and support for a period. The mechanism behind it is a comparison between the window recorded in your key and the date the engine binary was built.
Read that again, because it is not how most licences work: the comparison is against a BUILD DATE, not against today's date. The engine does not consult the clock when it checks a licence.
Two things follow.
Software you have shipped keeps working. The build inside it has a fixed build date, and that date does not move. There is no future point at which your customers' installations change behaviour.
A release cut after your window is simply not covered. You can still download and run the builds that are covered, and you can renew if you want the newer ones. Nothing you already have is affected by the decision either way.
The changelog prints each release's build stamp, which is the number the comparison uses, so you can check coverage yourself without asking us.
Last updated 2026-09-09.
Related
- How 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.
- Seats are recorded, not enforced The seat count rides in the key. No code counts installations, and the portal register is yours to keep.