#How Heplon works

You connect Heplon to your systems. Heplon reads them, finds issues that reduce reliability and development velocity, and opens a pull request for each issue worth fixing. You review and merge.

connect systems  ->  find issues  ->  open pull requests  ->  review and merge
      ^                                                              |
      |                                                              |
      +---------------------- improve and repeat --------------------+

#1. Connect your systems

You register connectors for your repositories, infrastructure, and engineering tools. See Connectors for what each one reads and which credential it needs.

Heplon builds internal representations of your systems. For example, it builds a graph from everything you connect.

If some of your systems are not reachable over the public internet, Heplon offers a small relay tool that you can run inside your infrastructure, and which forwards requests between your internal systems and Heplon. We also do bring-your-own-cloud deployments and host Heplon within your own infrastructure.

#2. Heplon finds issues

Heplon runs a library of issue detectors against data from your systems.

The detector library is continuously updated from incident reports, release notes for your toolchain, and other signals. Heplon assesses each finding against your business context to decide which ones are worth your attention, so you get the findings that matter to your organization, not every theoretical problem.

#3. Heplon opens pull requests

When Heplon finds an issue, it assesses its estimated impact and whether it is worth your attention. If so, Heplon opens a pull request that fixes it. A fix can span more than one pull request when the repair crosses repositories.

In addition to seeing Heplon's pull requests in your repositories, you can get an overview of Heplon's findings in the Issues area of the web app.

#4. Review and merge

You review each pull request and merge it.