Catalog

The Catalog provides a dynamic view of your environment, enabling exploration of your application, infrastructure, code, or contributors. It serves as the gateway to Heeler’s patent-pending ProductDNA, which automates deployment tracking, application lineage, and lifecycle management.

Applications

Within Heeler, applications connect the services that work together to deliver business outcomes. Heeler will automatically map the communication paths between the services. Context such as Tier and Security Lead, when set for the application, are propagated to all services of the application.

When viewing an application in Heeler, the platform models the connections between services by analyzing both the code and the underlying running infrastructure. This provides a holistic view of the application’s architecture. From the application view, you can seamlessly explore individual services or dive into the cloud infrastructure that supports the application.

Services

Services are automated constructs that map source code to its running deployments, bridging the gap between development and runtime. Once connected to your Source Code Management (SCM) and Cloud Service Provider (SCMs and CSPs), Heeler automatically identifies and creates services in your environment, mapping source code repositories to the running compute in your environment. It analyzes your cloud environment along with the source code to identify related resources such as databases, load balancers, and additional services.

For monorepos, Heeler goes a step further by automatically mapping individual projects to their respective running deployments, enabling segmentation of findings for each project in the monorepo.

With each service deployment, Heeler pinpoints the exact changeset of the repository in use, enabling precise tracking of individual deployments. This capability allows you to identify and compare material changes between deployments, ensuring greater visibility and control over your application lifecycle.

Infrastructure

The Infrastructure section provides essential context by linking your cloud infrastructure to the services and applications it supports. This connection enables you to quickly inspect infrastructure components and understand their relationships with the broader application ecosystem. With Heeler, you can easily determine which service or application is tied to a specific piece of infrastructure, offering deep visibility into your environment.

Once event collection is configured for your CSP, Heeler detects infrastructure changes within 60 seconds, delivering a near real-time view of your cloud environment. This capability ensures that you stay informed about updates and modifications as they happen, empowering you to maintain control and respond quickly to any changes that impact your applications.

Code

Once you connect your SCM, analysis begins immediately including breaking down monorepos into separate projects. For each repository listed, you are able to see and sort according to summary properties related to languages, code roots, dependencies, API endpoints, dependency findings, and contributors.

While in this view, you can also inspect individual repositories to view their Code Roots, which are logical “entry points” or “service boundaries” within a source-code repository. In a multi-service repository, each Code Root identifies a distinct application, microservice, module, or component.

For each Code Root, you can see summary properties related to dependencies, available remediations, dependency findings by severity, and ownership. Further, there is information on linked Services and a link to the Code Root section.