The Software Estate
Connect product and installation records.
The Software EstateConnect product and installation records.
Recorded License RightsInspect entitlements alongside known installations.
Renewal DecisionsBring supplier obligations into the review.
Reclamation ContextUse recorded usage and recovery information.
ProductRights
Bring product, installation, entitlement, renewal and reclamation context into software decisions.
What Connects Here
Explore in detailRecorded License Rights
Inspect entitlements alongside known installations.
Renewal Decisions
Bring supplier obligations into the review.
Reclamation Context
Use recorded usage and recovery information.
Product → Rights → Reclamation
Explore the details below, then bring your workflow, source data and questions to a guided conversation.
Built into the platform
The capabilities behind
the experience.
Executive workspace
Inspect the software estate and license position.
Product inventory
Maintain software product CIs in the shared CMDB.
Supplier lifecycle
Coordinate onboarding, review and controlled offboarding.
Third-party risk
Track assessments, review coverage and risk findings.
Discovery sources
Maintain provider and infrastructure discovery configuration.
Patterns
Define discovery behavior for supported sources.
Actual product view
Inside Software License Governance.
See the running demo environment. Features and records are subject to your role, configuration and integrations.
Connected capabilities
Explore the workspaces
that make it possible.
01 / assets
Software Asset Management
Connect software product CIs, installation records, licenses, contracts, usage and reclamation in one software asset workspace.
Explore 02 / assetsVendor & Contract Management
Connect supplier onboarding, third-party risk, agreements, obligations, performance and controlled exit across enterprise operations.
Explore 03 / infrastructureDiscovery & Reconciliation
Configure discovery sources, patterns, ranges and schedules, then reconcile confirmed inventory into the shared CMDB.
ExploreImplementation context
Features depend on enabled modules, configured roles, source data and supported integrations. Agree your implementation scope and acceptance criteria during discovery.
Who this is for
Software asset managers,License and procurement specialists,Contract renewal owners
Software decisions become unreliable when product inventory, installations, recorded rights and supplier agreements are reviewed separately. Teams need to relate the available evidence before discussing renewal or reclamation, while recognizing that a technical inventory alone cannot establish the organization’s complete contractual license position.
Illustrative walkthrough
Illustrative workflow: review a software renewal and reclamation decision
An illustrative organization approaches a software renewal and wants to understand its recorded position. The software asset team reviews product and license inventory, installation context, usage information and contract timing before deciding what should be investigated, renewed or considered for reclamation.
01Establish the recorded software position
Identify the product, license inventory and relevant installation CIs for the review. Inspect available usage and entitlement context, and qualify incomplete or conflicting information. Keep a clear distinction between software discovered on a device and rights recorded under an agreement before drawing conclusions about the organization’s position.
02Connect the commercial decision context
Review the relevant contract, renewal information and accountable owner alongside the software evidence. Inspect bundles or deployment context where applicable to the question. Record the assumptions and unresolved interpretation issues so a renewal discussion does not present incomplete inventory as a definitive legal or contractual license assessment.
03Review renewal or reclamation responsibilities
Evaluate the recorded renewal and reclamation decision with the appropriate software and commercial owners. Preserve the supporting evidence and agreed next work. Treat any subsequent change to usage or entitlement as work to validate rather than claim that identifying a reclamation opportunity automatically produces financial savings or license compliance.
Inspect product identity, recorded rights, installation and usage context, contracts and decision evidence together. These support software governance and renewal planning; they do not replace contractual interpretation or prove complete license compliance across an organization from inventory data alone.
Explore the platform
See Qintorava in action.
Open a workspace for a closer look.
Prepare the evaluation
Bring the right inputs.
What to prepare
- Product, license and installation records
- Relevant contract, renewal and usage context
- Software and commercial decision owners
Candidate measures to agree
- Renewal decisions linked to reviewed source evidence
- Software positions with explicit coverage qualifications
- Reclamation candidates assigned for accountable review
These are evaluation criteria, not promised outcomes. Agree the baseline, scope, source coverage and acceptance method with the responsible owners before drawing conclusions.
Questions for this topic
Get the details.
Does discovered software prove that a license is required or available?
Discovery establishes an observation about an installation within its source coverage. License requirements and rights depend on the applicable agreement and metric. Review product, entitlement, usage and contract evidence with the responsible specialists before interpreting technical inventory as a complete contractual license conclusion.
Does identifying reclamation opportunity guarantee savings?
No. A reclamation candidate requires an accountable decision and validation of the subsequent work, user need and commercial effect. Evaluate the supporting usage and entitlement context, and distinguish a potential opportunity from an achieved reduction in actual cost or a confirmed change to contractual obligations.
Can renewal planning connect to supplier contracts?
The reviewed scope connects software products, rights, installations, usage and contract or renewal context. Include the relevant software and commercial owners in discovery, then inspect a representative decision so data coverage, contract interpretation and approval responsibilities remain visible throughout the evaluation.
Your next operating chapter
See what connects
when everything connects.
Bring one workflow, one service challenge or one part of your estate. We’ll show you where Qintorava fits.