Changelog

This page tracks notable changes in LiMon product builds.

Standard release notes are included here
Professional release notes are included here

The entries below summarize the most important user-facing additions, platform improvements, and upgrade-relevant fixes across recent releases.

2027.1

New

Time in Product measures how long someone held at least one licensed feature of an application, rather than summing every concurrent feature checkout. Concurrent features of one application are one held product, so they are merged before being measured; two applications held at the same moment stay two products in use. It is now the hours figure on the Users list, User Detail, Departments, Department Detail and an application's top users. Licence possession can include idle applications and unattended jobs; it does not prove active work.

Improved

Quick Report covers Sites as well as Applications. The report can be created in Excel format.
User, department, application and usage views now report how many of the sessions behind an hours figure actually had a measurable duration. A zero no longer has to be guessed at: it says whether the licences were held for no time, or whether the duration could not be established.

Fixed

Chargeback now says when it allocated an application's cost on checkout counts because no session had a measurable duration, instead of presenting that split as if it had been made on usage hours.

2026.2.1

New

Debug logs from FlexLM servers started with the date-stamp option can now be imported.
The department view breaks down how a department's usage is allocated across the features it draws on.
A licence server whose clock runs ahead of LiMon is flagged on its server page, with how far ahead its reported session starts are.

Improved

The user report counts sessions and licence units separately, so a feature that draws many units per checkout no longer reads as though it had that many sessions.
Total hours on the user report shows how much is already recorded and how much is still accruing in open sessions, which explains why it can read higher than the activity chart or the usage explorer for the same period.
Open sessions report how long they have been held as an "at least" figure, measured between the times LiMon actually saw them, and stop accruing while LiMon cannot reach the server.
The operational manual layout and contents has been refreshed.

Fixed

Searching the user report for a name that several usernames begin with lists the matching users instead of reporting that no such user exists.
Log files that run past midnight without an internal date marker are dated correctly instead of filing everything after midnight under the previous day.
Historical usage imported from DSLS tracing logs consolidates simultaneous grant handles for the same client into one consumed seat, matching the live DSLS usage report instead of overstating short peaks.
Session hours no longer include the difference between the licence server's clock and LiMon's own.

2026.2

Edition scope: Standard and Professional

New

Compliance ledger (Professional, with active maintenance). Each day is sealed as a signed, immutable evidence package — licence inventory, activity, denials, monitoring coverage, and the SHA-256 of every log file imported — chained to the day before it. Late data and operator corrections are appended as signed amendments instead of rewriting the seal, so a report can show both what was known at the time and what is understood now. The signing key can be rotated with continuity proven in both directions, and every install ships a standalone verifier an auditor can run on their own machine, against an exported bundle, with no access to your systems.
External anchoring. Export the current head of the ledger to a write-once store you control — object-locked storage, a SIEM, an archive — and file the receipt that system returns. Until you do, LiMon states plainly that its evidence is verified locally only. Nothing is transmitted anywhere by LiMon, so air-gapped sites can anchor their ledger exactly like everyone else.
An idle hour and an unwatched hour are reported as different things. Every historical figure says whether it rests on measurement, on evidence that the feature was genuinely idle, or on a gap in coverage — so a monitoring outage is never presented as quiet demand.
Each site can record a contact person — name, role, email and phone — so a problem at a site has an owner.
Admin fields that are deliberately not shown to users are marked as such, so it is clear why something filled in does not appear on a dashboard.
Deleting a site or an application warns that its historical usage will lose that label before you confirm.

Improved

The Audit Report reports separately on the chain, the signatures, the evidence, monitoring coverage, amendments and external checkpoints instead of giving one pass-or-fail verdict.
Cost of delay is measured per interruption rather than per denial record, so a licence client's automatic retries no longer multiply the hours lost. Related interruptions count once, and no employee can lose more than a working day (8 hours by default, and configurable).
Utilisation, peak and coverage figures name the window and the population they measure, so two different questions cannot be read as the same number.
Right-sizing says how many licence pools fund a recommendation and separates genuinely rare use from ordinary over-provisioning.
Reports are substantially faster to generate: the historical evidence behind a report is read in one pass instead of once per metric.
Live views cap the tables that can run to hundreds of rows, and say they are working instead of showing an empty panel while a large view loads.
Under privacy masking the same person keeps the same pseudonym however each licence server spells their name.

Fixed

Usage that was never attributed to an application is no longer reported as belonging to a deleted owner.
Sessions whose server has since been removed stay in user history, and retired features keep their place in the feature pivot.
Usernames are masked in top-user responses when privacy masking is enabled.
Diagnostic support bundles no longer carry site and cost detail.
Capacity forecast headings and the transfer table stay inside their columns in generated PDFs.
LiMon warns when the installation ID cannot be saved.

2026.1

Edition scope: Standard and Professional

Highlights

Matured the native-package release line with .deb and .rpm artifacts, deterministic package validation, and stronger install/bootstrap behavior.
Improved offline install readiness by bundling Python dependencies per supported interpreter path and tightening the packaged limon-setup bootstrap flow.
Expanded historical-data capabilities with multi-vendor log import for FlexLM, RLM, and LM-X, using a unified parser-selection path.
Added Chargeback as a web-first intelligence report with export support instead of treating it as another PDF-only workflow.

Fixes

Fixed several native-package edge cases around bundled Python dependencies, package metadata, and first-run bootstrap recovery.
Corrected package acceptance issues in both DEB and RPM validation lanes.
Improved release artifacts so Docker and package outputs contain the expected files without duplicate or misleading payloads.

Upgrade Notes

No data migration is expected.
If you automate .deb or .rpm installs, review the current package-install flow and supported Python/runtime expectations before upgrading.

2025.3

Edition scope: Standard and Professional

Highlights

Added live intelligence report pages and report services so key report flows can be explored in the web UI, not only as generated files.
Added a live Compliance Ledger panel and folded compliance context more deeply into the Audit Defense experience.
Expanded Savings report scenario analysis so teams can compare both seat-count and pricing assumptions from the report UI.
Added report scheduling and report settings support to the administration workflow.

Fixes

Improved timezone handling and surfaced site timezone context more clearly in site cards and details.
Refined report behavior for applications without cost data so capacity analysis still remains usable.
Improved report rendering and export behavior across intelligence views.

Upgrade Notes

Review report settings after upgrade if your team relies on scheduled or customer-facing intelligence outputs.

2025.2

Edition scope: Standard and Professional

Highlights

Added first-class native package installation with the limon-setup wrapper and a guided packaged setup path.
Reworked Docker delivery around offline-friendly bundles and docker-install.sh so commercial installs no longer depend on a live registry pull.
Added limon-diag support-bundle tooling to make customer troubleshooting faster and more consistent.
Strengthened end-to-end release validation so Docker and packaged builds are exercised before publication.

Fixes

Fixed setup and packaging edge cases across Docker distribution and packaged install paths.
Improved deployment route handling so /admin/ and /setup/ work consistently on supported deployment routes.
Corrected early release-process issues in offline bundle assembly and validation.

Upgrade Notes

If you are upgrading from older commercial builds, align your operational runbooks with limon-setup, limon-diag, and the offline Docker bundle flow.