User Blueprints vs Plugin Blueprints

Rely distinguishes between two types of blueprints: User Blueprints and Plugin Blueprints.

Plugin Blueprints

Plugin Blueprints are predefined by Rely and define each native plugin's data model. These blueprints (and its entities) are not editable by users, ensuring stability and integrity of the plugin's functionality.

When installing (some) plugins, you may select assets of interest. The selected assets determine which Plugin Blueprints are incorporated into your own data model.

By default, plugin blueprints are located in the 'hidden' section of your data model builder and in the 'hidden' section of the Software Catalog sidebar.

These blueprints establish the structure for entities that Rely automatically retrieves and maintains through its entity discovery process. This automation keeps your catalogs consistently up-to-date without any manual intervention required.

Entities created from plugin blueprints serve as an accurate reflection of data from your development tools, acting as the definitive source of truth for the information Rely ingests.

User Blueprints

In contrast, User Blueprints are fully customisable. They are created and managed by users to tailor its Rely environment to specific organisational needs. These blueprints allow for flexibility and adaptability in defining and managing the entities within your software catalog.

Entities derived from User Blueprints are editable through multiple methods:

• Directly via the Rely UI

• Programmatically via the public API

• Or through automation rules, which allow you to map & manipulate data from plugin blueprint entities onto user blueprint entities.

To learn more about the user blueprints that rely enables out-of-the-box, checkout the default data model.