GitHub
LevelFour installs as a single GitHub App on the organizations and repositories you select. One install powers both of our GitHub-side products:
- PR bot. Comments on the pull requests your team opens. On every pull request that touches Infrastructure-as-Code (Terraform, CloudFormation, AWS CDK, Pulumi, or Kubernetes manifests), the bot reads the diff and scores the cost and performance impact against your real LevelFour usage data (not a generic price book). It posts a before vs after comparison comment in the PR conversation, drops inline "Suggested change" boxes on the diff with concrete commits to optimize cost or performance, and surfaces a check-run status visible in the PR's checks panel. The cost conversation happens at review time, before the monthly bill arrives.
- IaC PR platform. Reads the Infrastructure-as-Code across the repos you granted access to, finds cost waste, and opens pull requests against your default branch with the savings changes ready for you to review and merge. It runs the same engine on the same data and proposes the same commit suggestions. The difference is who opens the pull request: LevelFour, rather than your team.
.levelfour/config.yml.You complete this from the LevelFour dashboard. No onboarding email loop, no credentials to share.
Prerequisites
- You are an Owner of the GitHub organization you want to install on. Members and outside collaborators cannot install third-party apps.
- Your organization does not block third-party GitHub Apps under Settings > Third-party access. Most organizations leave this open by default.
- You are signed in to the LevelFour dashboard at
https://dashboard.levelfour.aias a member of the LevelFour organization you want to connect this GitHub organization to.
Install
Open Connect Accounts, then GitHub
In the dashboard sidebar, click Connect Accounts, then click the GitHub tile.
You land on https://dashboard.levelfour.ai/connect-accounts/github. The panel shows a short overview, the install steps, and an Install GitHub App button. If your organization already has LevelFour installations, they appear in the Connected installations section at the top.
Install the GitHub App
Click Install GitHub App. A new tab opens GitHub's install page for the LevelFour app.
GitHub asks two questions:
Which account do you want to install on. Pick the GitHub organization you intend to connect. If the picker only shows your personal account, you are not an Owner on the target organization, or the organization has third-party app restrictions enabled.
Which repositories to grant access to. Two options:
- All repositories grants access to every repo in the organization now and any repo added later. Use this when LevelFour should track everything.
- Only select repositories grants access to the repos you pick. Use this for a phased rollout.
Click Install. GitHub redirects to a callback page on the LevelFour dashboard. You can close that tab once it shows "You can close this window."
Wait for the panel to flip to Connected
The original /connect-accounts/github tab polls for the installation. The status pill cycles through Waiting for install and Verifying installation.
Connected within five to ten seconds, and the Connected installations list shows your GitHub organization with the repo count.LevelFour starts reading repo metadata right away. Cost analysis on your existing Infrastructure-as-Code takes a few minutes; comments on new pull requests start immediately.
What the GitHub App grants
LevelFour requests these permissions:
| Permission | Why we ask for it |
|---|---|
| Read access to repository metadata | List the repos you granted us |
| Read and write access to repository contents | Read your Infrastructure-as-Code files (.tf, .json/.yml CloudFormation, CDK and Pulumi sources, .yaml/.yml Kubernetes manifests) and propose savings via pull requests we open |
| Read access to issues | Correlate bot comments with related issues |
| Read and write access to pull requests | Comment cost impact on your PRs and update our own |
| Read and write access to check runs | Post a "LevelFour" status check that is visible in the PR's checks panel |
Tuning the PR bot
You tune the bot per repo by committing a .levelfour/config.yml file at the root of the repo's default branch. PR bot configuration has the schema, the defaults, the examples, and the roadmap for an organization-level toggle.
Changing or removing access
You change what LevelFour can see from inside GitHub, not from the LevelFour dashboard. Open https://github.com/organizations/<your-org>/settings/installations and click Configure next to the LevelFour app.
Adding or removing repositories
Adjust the Repository access section and save. GitHub fires a webhook to LevelFour the moment you save, and the dashboard reflects the new repo count on the next page load.
Removing the app
Scroll to the bottom of the same page and click Uninstall.
GitHub fires the uninstall webhook to LevelFour. We delete the installation record and stop scanning your repos within a minute. Pull request comments and check runs LevelFour previously posted stay in place for your audit log.
Troubleshooting
| Symptom | What to do |
|---|---|
| The install picker only shows your personal account, not your organization | You are not an Owner of the GitHub organization, or the organization restricts third-party apps. Ask an Owner to install for you, or ask them to lift the restriction in Settings > Third-party access |
The dashboard is stuck on Waiting for install | The popup may have been blocked. Click Reopen GitHub install to open the URL in a new tab manually. If GitHub returned a 404 on the install URL, contact LevelFour support: the GitHub App slug may have changed |
The dashboard shows Verifying installation for more than a minute | GitHub redirected the popup but LevelFour could not validate the install. Click Cancel, then Install GitHub App again. If the issue recurs, contact LevelFour support with the integration ID from the URL (the ?integration= query parameter) |
| You uninstalled but the dashboard still shows the installation | Refresh the page after waiting 30 seconds. If the row persists, contact LevelFour support with the GitHub organization login |
Next
- PR bot configuration is the
.levelfour/config.ymlschema and the defaults - AWS single account and AWS multi-account connect cloud accounts, which is independent of this install
- Onboarding overview is which path to take
Committed use discounts
Turn on the Committed Use Discounts export in Cloud Billing and grant LevelFour read access, so your commitment terms, dates, and status appear alongside coverage.
Azure
Azure is not part of the self-service onboarding flow yet. To connect a Microsoft Azure tenant today, talk to your LevelFour contact.