Walk into the audit already knowing the number.
Omnitam keeps the entitlements you record and the seats you assign in one governed system: an effective license position, a contract and vendor register, publisher and product on each license, and a 12-month renewal forecast. Over-assignment surfaces before the vendor finds it; unassigned seats surface before finance renews them.
Software ROI with receipts.
License management sits in the same governed system as the CMDB: what you are entitled to is compared to the seats you assign or record. Linking license use to the software discovery finds is planned.
Effective license position
One position across 8 license models: perpetual, subscription, concurrent, named-user, device, site, open-source, and other. Entitlements recorded beside assigned seats.
Seat utilization & reclaim
Per-user assignment and utilization history, with unassigned seats called out, so unused seats surface before finance renews them.
Contract & vendor register
Every vendor and contract in one register: terms, quantities, start and end dates, and the entitlements each grants, kept beside the spend.
Publisher and product on each license
Record the publisher and product on each license, so you always know who you buy from and what each entitlement covers.
12-month renewal forecast
Every renewal on a timeline with contract terms and amounts beside the spend. Renewal week stops being a surprise.
Over-deployment & true-up
Over-assignment surfaces before the vendor's audit finds it, and true-up exposure is quantified early, at your negotiating table rather than theirs.
Master agreements (Enterprise)
Enterprise license contracts recorded once, with the entitlements they grant, so every title under the agreement reads from the same terms.
SBOM-backed composition
Ingest SPDX / CycloneDX for open-source license data and "where does that library run?" See SBOM / Software Composition.
Entitlements next to assignments.
Utilization per vendor, the seats nobody is assigned, and the renewals coming at you, on one screen.
Contracts, vendors, and publishers in one place.
Not a folder of PDFs and a spreadsheet of seats. A governed register where every contract, the vendor behind it, and the publisher and versions it covers live next to the seats you assign.
| vendor | product | model | seats | renews | status |
|---|---|---|---|---|---|
| Oracle | Database EE | named-user | 436 / 420 | 2026-11-30 | over-deployed |
| Atlassian | Cloud | subscription | 1,730 / 2,000 | 2027-03-31 | compliant |
| Datadog | Observability | subscription | 800 / 2,000 | 2027-01-15 | reclaim |
| Microsoft | 365 E5 | named-user | 2,940 / 3,000 | 2026-12-09 | review |
| Red Hat | RHEL | subscription | 88 / 100 | 2026-12-01 | compliant |
Demo data as of 25 Oct 2026. Renewal dates and "due in" figures are relative to that date; status reflects assigned versus entitled seats and the renewal outlook.
Know the number before anyone asks.
Walk in knowing the number
The position you present at an audit is one you maintain all year, not a reconstruction under a 30-day deadline. Over-deployment is quantified before the vendor quantifies it for you.
Reclaim before you renew
Unassigned and under-used seats are called out before renewal, so finance renews the right quantity instead of last year's.
One record for finance and audit
Contracts, vendors, publishers, and entitlements sit beside assigned seats, so procurement, ITAM, and audit all read from the same governed source.
About License Management.
Which license models are supported?
Eight: perpetual, subscription, concurrent, named-user, device, site, open-source, and other. Each entitlement is recorded with its model, quantity, and contract terms, then compared to the seats you assign or record.
How do entitlements get into Omnitam?
You record contracts, vendors, and entitlements in the register (by hand or over the API), and seats are assigned or typed in by hand. Open-source composition can also be ingested as SPDX / CycloneDX. Omnitam reconciles what you own against what you have assigned; linking license use to the software discovery finds is planned.
Is License Management a premium add-on?
No. License position, the contract and vendor register, publisher and product on each license, and the renewal forecast are part of the core platform on every paid plan (seats, assignments, renewals), not a separate module. Master agreements (enterprise license contracts) are on Enterprise.
How is this different from SBOM / Software Composition?
License Management is about commercial titles, contracts, and seats: what you buy and whether you are compliant. SBOM / Software Composition is about open-source components inside what you ship: which versions run where, and their OSS-license data. They complement each other.
See your effective license position.
Connect one account read-only, record a contract or two, and watch entitlements line up against the seats you assign in a single session.