Infralyst Logoinfralyst

Infralyst Docs

Short guides to help you set up Infralyst, understand downsizing, and keep AWS changes safe.

Can't find what you need? Email [email protected].

Getting started

The basics for getting your first workspace connected and ready to generate Terraform pull requests.

Create your workspace

Sign up with your work email and create a workspace for your team. Every workspace starts on the Free plan with 3 PR credits so you can try Infralyst on real infrastructure.

Later, you can invite teammates and upgrade from inside the app.

Connect AWS with a read-only IAM role

From your workspace:

  • Add an AWS account in your workspace.
  • Follow the in-app steps to install the Infralyst Terraform module in one of your infra repos.
  • Copy the generated read-only IAM role ARN back into Infralyst and test the connection.

Infralyst can now read your AWS resources and usage, but never runs code or applies changes in your accounts.

View the Terraform module →

Connect GitHub and map Terraform state

From your workspace:

  • Install the Infralyst GitHub App and choose the GitHub organization and repos that contain your Terraform code.
  • Add those repos to your workspace.
  • For each AWS account, add Terraform states, choose the backend (GitHub or S3), and select the repo that owns the code for that state.

You can combine multiple AWS accounts, Terraform states, and repos to match how your infrastructure is laid out. Recommendations land in the right repo for each account.

Core concepts

A quick overview of how Infralyst thinks about workspaces, recommendations, and PR credits.

Workspaces and PR credits

Infralyst is organized around workspaces. Each workspace starts with 3 PR credits on the Free plan. Generating a Terraform PR for a recommendation uses one credit. You can upgrade to the Founder plan from inside the app if you need more PRs.

Recommendations and confidence

For each downsizable EC2-backed resource, Infralyst:

  • Collects CPU and, where available, memory metrics from CloudWatch
  • Looks at averages and high-percentile usage over time
  • Applies conservative checks on data quality, CPU, memory, and seasonality

Each recommendation includes a confidence score based on how much history we have and how stable the usage patterns are.

You can view recommendations in your workspace either by AWS account or by GitHub repository, depending on how your team likes to work.

What Infralyst changes

For each downsizable EC2-backed resource, Infralyst proposes small, targeted changes to your existing Terraform:

  • Individual EC2 instances – we change the instance_type on the relevant Terraform resource. Applying this will restart that instance, so it's usually done in a maintenance window.
  • Autoscaling groups with launch templates – we update the launch template's instance_type, adjust version references so only the target ASG picks up the new version, and use Terraform's instance_refresh mechanism for a rolling, zero-downtime replacement of instances. Other ASGs that share the same launch template stay pinned to their current version.

We don't touch unrelated resources, and we don't add any hidden automation outside what's described in the PR.

Integrations

The services Infralyst connects to today and what we use each one for.

AWS (required)

Used for reading CloudWatch metrics and resource metadata via the read-only IAM role created by the Terraform module. We use this data to find downsizing opportunities. We do not store or ask for long-term access keys.

GitHub (required)

Used for opening pull requests in the repositories you select via the Infralyst GitHub App. We never push directly to your main branch and we never merge changes on your behalf. You can remove the GitHub App or deselect repositories at any time.

Slack (optional)

Used for sending notifications when new savings appear and letting you trigger PR generation from your channels. Notifications can be configured per AWS account or per GitHub repo so the right teams see the right messages. You can disconnect Slack at any time from your workspace settings.

Troubleshooting

Quick checks for the most common setup issues. If these don't help, email [email protected] and we'll take a look.

AWS connection issues

  • Make sure you've applied the Infralyst Terraform module in one of your infra repos.
  • Copy the IAM role ARN from Terraform into the AWS account in Infralyst exactly as shown.
  • Click Test connection in the workspace.
  • If tests keep failing, send us the error message from the AWS account page.

GitHub / Terraform state not showing

  • Check that the Infralyst GitHub App is installed in the correct GitHub organization.
  • Confirm the repos that contain your Terraform code are selected in the GitHub App and added to your workspace.
  • For each AWS account, make sure at least one Terraform state is added and mapped to the right repo and backend (GitHub or S3).
  • If repos or states still don't appear as expected, let us know your workspace name and the repo/state you're expecting to see.

No recommendations appearing

  • Newly connected accounts may need time to collect enough history. We typically need at least 30 days of CPU (and memory, if available) data before we can make safe downsizing recommendations.
  • If instances are consistently busy, Infralyst may decide there's nothing safe to downsize yet.
  • Check that the AWS account and Terraform state are both connected and healthy in your workspace.
  • If you still see no recommendations after data has had time to collect, reach out and we'll investigate.

Billing and support

Plans and billing

Infralyst workspaces start on the Free plan with 3 PR credits and full analysis. The Founder plan is billed per workspace and unlocks ongoing PR generation plus additional features over time.

See the Pricing page for details and current terms.

Getting help

If you hit something that is not covered here:

You can also visit the Support page to see how we handle response times and availability.