Overview

LevelFour reads two things from your infrastructure. Cloud cost and usage data, to detect waste and calculate savings. Infrastructure-as-Code in your repositories (Terraform, CloudFormation, AWS CDK, Pulumi and Kubernetes manifests), to open pull requests with the savings changes. You grant each kind of access through a self-service flow in the dashboard at Connect Accounts.

AWS and GitHub onboarding are independent: do either, both, or each at its own pace. Only the AWS paths use a handshake ID. Google Cloud and GitHub verify themselves and need no follow-up.

Cost and usage data

AWS

Single account, if any of these is true	Multi-account, if all of these are true
You have one AWS account, or only a few that you onboard one at a time	You use AWS Organizations with all features mode enabled
You do not use AWS Organizations, or you only use it for consolidated billing	You want to onboard many member accounts at once, including future accounts that join your organization
You prefer to grant access to each account explicitly	You can deploy CloudFormation from the management account, or a delegated StackSets admin account

On the single-account path you click a Launch Stack link, deploy a single CloudFormation stack per account, and LevelFour auto-detects the role as soon as it exists. Five minutes per account.

On the multi-account path you click one Launch Stack link in the management account, paste your AWS Organizations root or OU ID, and CloudFormation StackSets fans the role out to every account in the target OU. Future accounts that join the OU pick up the role automatically.

Both paths create the same roles in every account, under predictable names, so you never copy an ARN back to LevelFour. See what the stack creates.

Detailed cost data is a separate, optional step. LevelFour falls back to Cost Explorer without it, and resource-level views and tag-based cost allocation are richer once it is on.

Google Cloud

Ask your LevelFour contact to turn on Google Cloud for your organization first. Then connect your projects by running a short command in your own Cloud Shell, scoped either to one project or to your whole Google Cloud organization. LevelFour never asks for a service-account key.

Cost data arrives separately, through Cloud Billing export, which a finance or billing admin can own.

Azure and Kubernetes

Neither is self-service yet. Talk to your LevelFour contact if you need to onboard an Azure tenant or a Kubernetes cluster today.

Infrastructure-as-Code

GitHub

One GitHub App install powers both GitHub-side products. The PR bot scores the cost and performance impact of every pull request your team opens that touches your Infrastructure-as-Code, against your real usage data, and posts what it finds on the PR. The IaC PR platform reads the same repositories, finds cost waste, and opens savings pull requests of its own for your team to review and merge.

You install it from the dashboard and grant access to all repositories or a curated subset.

Each provider you connect shows as Connected on its panel under Connect Accounts in the dashboard.