Build the Environment Inventory

Your Environment Inventory is the foundation of Golive. It brings together the systems you want to manage, the categories that describe them, and the attributes that capture their details.

This article acts as a map of the process. It outlines the key steps to build your Environment Inventory and provides links to detailed instructions for each step. You can also use the Get Started wizard in-app to guide you through the process.

Steps to Build the Environment Inventory

Step 1: Set up Applications

Applications represent the business systems or services you want to track. They are the anchor for everything else in Golive. Applications can connect to Jira Versions, define deployments, and include multiple tiers when your system is structured that way.

For instructions, refer to the Manage Applications article.

Step 2: Set up Environment Categories

Categories describe the purpose of an Environment, such as Development, Testing, Staging, or Production. They give context to your Environments and help teams understand how each one is meant to be used.

For instructions, refer to the Environment Categories article.

Step 3: Define Environment Attributes

Attributes store additional information about your Environments — such as URLs, owners, database versions, or other custom details. They ensure every Environment follows a consistent structure and provides the context your teams need.

For instructions, refer to the Environment Attributes article.

Step 4: Create Environments and Environment Landscapes

Environments are the actual instances where your applications live. Each Environment is tied to an application and category, and enriched with attributes.

Environment Landscapes extend this concept: they represent multi-tier setups, grouping related Environments together under a single structure.

For instructions, refer to the Create Environments and Create Environment Landscapes articles.

Step 5: Add Environment Dependencies

Dependencies capture the relationships between Environments. They show when one system relies on another, making it easier to coordinate changes, reduce risks, and understand the impact across teams.

For instructions, refer to the Environment Dependencies article.