LeanIX - Product Documentation

Welcome to the LeanIX Product Documentation. Here you will find all the basic information you need to start working with LeanIX. We provide you with well-structured information on how to get more out of LeanIX, best-practices and use-case specific guidelines. Feel free to spread this product documentation in your company and use it as a common information source to answer your colleagues’ most urgent questions.

Get Started

Technology Risk Management

This section gives you an overview of modeling reports used for Technology Risk Management. It shows you which standard reports are available and how to import the right data to get meaningful analyses.

One of the main challenges when consolidating your IT landscape is to understand where your software is running. Often, identifying fragmented data centers and hosting shows great potential for cost savings. This tutorial shows how to get started.

Please make sure to read our documentation on how to Import & Export your Data as well, if you haven't done so already.

1. Import your application list

2. Import the software versions you have in use

In this example, we look at database servers. It is good practice to use a Tech. Stack (see What is a Fact Sheet?) to group your software, as well as to use a Tag Group (see Use Tags for more powerful insights) to mark the recommendation whether to use the software or not, e.g. with a Candidate, Leading, Exception, Sunset model.

3. Import your data centers and server into LeanIX

Next, we import the information on server and remote data center locations. Again, it's good practice to assign a Tech. Stack.

4. Verify your software and server import

The IT Component Landscape Report gives you a great overview on the imported IT Components group by Technology Stack. As one example, we can use the created Tag Group to display the software recommendation. Learn more about reports here: Insights through Reports.

Also, the IT Component Location report provides a nice overview where your servers are located:

5. Link software and server to Applications

Now it's time to link the Applications. For a first view, it's sufficient to create a link to a software and to a server. Later, you can also consider to link software and server, e.g. via a requires relation.

Diagrams allow you to get a nice overview of the created relations. Start with the application, and use the show dependency, drill down and roll up options to display the relation.

6. Now what?

Now you can put the pieces together. Use the Application Landscape to find out where a certain data center location affects your business.

Use the Application Sourcing Report to find out where Applications using certain Software versions are hosted.

Or just use the table view in the Inventory to make the dependencies transparent.

Updated 6 days ago

Technology Risk Management


This section gives you an overview of modeling reports used for Technology Risk Management. It shows you which standard reports are available and how to import the right data to get meaningful analyses.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.