How Infralyst works
From AWS usage data to Terraform pull requests that reduce your AWS costs, inside your existing workflow.
See how Infralyst connects to your cloud, analyzes usage, and prepares Terraform changes that your team reviews and merges.
1. Connect Infralyst to your infrastructure
A one-time setup that usually takes less than an hour.
Connect AWS
Add the Infralyst Terraform module to your infra repo. It creates a read-only IAM role so Infralyst can see your AWS resources and usage, but it never deploys changes in your accounts.
Connect GitHub
Install the Infralyst GitHub App in your GitHub organization and choose which infrastructure repositories it can access. These are the repos where Infralyst will open Terraform pull requests.
Map Terraform state
Link your Terraform states to the right AWS accounts and repos. This keeps every recommendation tied back to the exact code that manages the resource.
Once setup is complete, Infralyst runs in the background and keeps watching for new cost-saving opportunities.
2. How Infralyst finds savings
Deterministic analysis. No AI, no guesswork.
Collect data from AWS
Infralyst pulls resource metadata and utilization metrics from CloudWatch across your accounts and regions. The more history available, the stronger the recommendation.
Analyze what you are paying for
Each resource type goes through its own set of checks. Infralyst looks for oversized instances, outdated configurations, and resources you are paying for but not using.
Surface the highest-impact savings
Recommendations are ranked by estimated monthly savings and grouped by account. Every recommendation includes the data behind it so you can verify before acting.
Conservative by design
Every check is deterministic. Fixed thresholds, no machine learning, no AI. When data is sparse, noisy, or shows recurring spikes, Infralyst skips the recommendation rather than guessing. AI is only used later, to generate the Terraform code change.
3. Review recommendations
Ranked by estimated monthly savings and grouped by account. Dismiss what does not fit, generate a PR for the rest.
| Resource | CPU | Memory | Current | Recommended | Savings | |
|---|---|---|---|---|---|---|
| api-prod-01us-east-1 · 72 days | 18%avg 4.2% | 24%avg 11% | m5.2xlarge | m5.xlarge | $47/mo | Generate PR |
| worker-batch-02us-east-1 · 52 days | 22%avg 8.1% | 28%avg 12% | c5.xlarge | c5.large | $23/mo | Generate PR |
| cache-redis-03us-east-1 · 45 days | 19%avg 6.8% | 21%avg 9% | r5.large | r5.medium | $18/mo | Generate PR |
4. Generate a PR, review, and merge
Click Generate PR. An AI agent reads your repo, locates the right Terraform files, writes the change, and opens a pull request. Your team reviews and merges like any other infrastructure change.
Downsize EC2 instance worker-batch-02: c5.xlarge → c5.large (-$23/mo)
EC2 instance worker-batch-02 in us-east-1 can be downsized from c5.xlarge to c5.large, saving an estimated $23/mo.
| Metric | Avg | P99.5 |
|---|---|---|
| CPU | 8.1% | 22% |
| Memory | 12% | 28% |
Lookback: 52 days
5. Optionally connect Slack
Map AWS accounts or GitHub repos to Slack channels so each team sees what is relevant to them. Generate a PR or dismiss a recommendation without leaving Slack.
New EC2 savings recommendation · Save $23.00/mo
Resource
worker-batch-02 (us-east-1)
Lookback
52d
CPU Avg
8.1%
CPU P99.5
22%
Mem Avg
12%
Mem P99.5
28%
Current
c5.xlarge
Recommended
c5.large
View on Infralyst
What Infralyst Supports
We're starting focused and expanding fast. Here's what Infralyst covers today to reduce your AWS costs, and what's coming next.
Available now
EC2 instances
Find oversized EC2 instances using real CloudWatch data and conservative thresholds. Infralyst recommends a target size and generates the Terraform change.
Learn more →Auto Scaling Groups
Safe instance type and size changes for Auto Scaling Groups configured with Launch Templates, keeping your existing scaling configuration intact.
Learn more →ECS Fargate
Right-size task CPU and memory while respecting autoscaling and deployment settings.
Learn more →EBS gp2 to gp3 migration
Migrate gp2 volumes to gp3 for 20% lower cost and better baseline performance. No downtime, no application changes.
Learn more →Coming next
EC2 previous-gen migrations
Replacing previous-generation instance families with current ones for better price-performance.
EC2 Graviton migrations
Moving Arm-compatible workloads to Graviton instances for up to 20% better price-performance.
Want to shape what we add after this? Email [email protected].
Controls and safety rails
Built to fit teams that already treat infrastructure as code.
Read-only access
Infralyst connects via read-only IAM roles and a GitHub App. The only writes we perform are creating branches and pull requests.
No hidden automation
Every change is a Terraform diff in one of your repos. Nothing runs in your AWS accounts. You review and deploy using your existing pipeline.
Conservative defaults
If data is sparse, noisy, or shows recurring spikes, Infralyst skips the recommendation. When a change would require downtime (resizing a standalone EC2 instance, for example), Infralyst flags it in the pull request so your team can plan a maintenance window.
Per-resource control
Dismiss individual recommendations or exclude specific resources so they are not suggested again. Every action is available from the dashboard and from Slack.
For more on access and data handling, see Security at Infralyst.
How It Works FAQ
Ready to try Infralyst on your own AWS accounts?
Create a workspace, connect AWS and GitHub, and use your 3 free Terraform PRs on real infrastructure. You review and merge every change.
- No credit card required
- Read-only IAM role
- Your team reviews and merges every change