NewMCP server for AI agents - let Claude Code codify your cloud

Reverse Terraform Your Cloud Infrastructure

The maintained, fast successor to Terraformer. Scan AWS, Azure, and GCP and reverse-engineer them into clean Terraform code plus Terraform 1.5+ import blocks - import your whole cloud in minutes, not months. 240+ resource types across AWS, Azure and GCP, all running locally with read-only credentials.

pip install terraback
~30sfor under 100 resources
1,000+imported in minutes
Parallelmulti-account scanning
AWS
Azure
GCP
Quick start

Get Started in Minutes

Choose your installation method and start scanning your cloud infrastructure

1

Choose Your Installation Method

or use standalone binaries

Download for Linux

After download, run:

chmod +x terraback-linux
2

Verify Installation

terraback scan auth-check
3

Start Scanning Your Infrastructure

1. Authenticate with the AWS CLI:

aws configure

2. Scan all resources in a region:

terraback scan all aws --region us-east-1

3. (Optional) Scan a specific service:

terraback aws ec2 scan-instances --region us-east-1

1. Authenticate with the Azure CLI:

az login

2. Scan all resources in a subscription:

terraback scan all azure --subscription-id YOUR_ID

3. (Optional) Scan a specific service:

terraback azure compute vm scan --subscription-id YOUR_ID

1. Authenticate with the gcloud CLI:

gcloud auth login

2. Scan all resources in a project:

terraback scan all gcp --project my-gcp-project

3. (Optional) Scan a specific service:

terraback gcp compute instance scan --project my-gcp-project
Under the hood

How It Works

Convert your cloud infrastructure into production-ready Terraform code

Terraback simplifies the complex process of converting existing cloud infrastructure into clean, maintainable Terraform code. It achieves this through reverse-engineering, intelligent dependency discovery, and automated code generation.

New - Model Context Protocol

Give AI Agents Access to Your Cloud via MCP

Claude Code, Claude Desktop, Cursor, Windsurf, and any other MCP client can now scan, codify, and verify your infrastructure as Terraform - deterministically.

Scan

The agent calls scan_infrastructure for a read-only inventory of what actually exists in AWS, Azure, or GCP.

Codify

codify_resource and codify_batch generate the HCL and Terraform 1.5+ import blocks from Jinja templates - no LLM guessing the syntax.

Verify

verify_plan runs terraform plan and hands the agent a parsed drift summary, so it can self-correct until the plan is clean.

The self-hosted deterministic codification engine for AI agents

The only open, self-hosted MCP server doing deterministic multi-cloud (AWS + Azure + GCP) codification with import blocks - no SaaS account, no LLM-guessed HCL. Community includes the full MCP server, with codify_batch capped at 25 resources per run; Professional lifts the cap.

claude mcp add terraback -- terraback mcp
Why Terraback

Why Teams Choose Terraback™

Built for real-world infrastructure challenges

True Multi-Cloud

Unified CLI for AWS, Azure, and GCP. Same commands, same workflow, different clouds. No need to learn provider-specific tools.

Dependency Mapping

Discovers and maps resource relationships across services. Security groups, subnets, IAM roles - properly referenced in generated code. Available in Professional tier.

Built for Speed

Import your whole cloud in minutes - around 30 seconds for under 100 resources, 1-3 minutes for hundreds, 5-20 minutes for thousands (cloud API rate limits are usually the bottleneck). Professional parallel scanning cuts wall-clock time further. The fast, maintained successor to Terraformer.

Best Practices Built-in

Generates clean, modular Terraform following HashiCorp's style guide. Proper naming, consistent formatting, and logical resource grouping.

Clean Output

Generates clean Terraform code with automatic variable extraction, environment detection, and proper state management for your infrastructure.

Professional Features

Advanced dependency scanning, parallel execution, and support for multiple AWS profiles, Azure subscriptions, and GCP projects.

Runs locally - nothing leaves your machine

Terraback uses read-only credentials and runs entirely on your machine. Your cloud is scanned, parsed, and turned into Terraform locally - nothing about your infrastructure is ever sent to our servers.

Read-only access No data sent to us Offline license after activation
Pricing

Simple, Transparent Pricing

Choose the plan that fits your infrastructure needs

Community

Free

forever - no card required

Perfect for testing and small projects

  • Core resources for AWS, Azure, GCP
  • EC2, VPC, S3 (AWS)
  • VMs, VNets, Storage (Azure)
  • Compute, Networks, Storage (GCP)
  • Unlimited core resources
  • Basic dependency mapping
  • MCP server for AI agents (codify_batch capped at 25/run)
  • Advanced services (RDS, Lambda, etc.)
  • Multi-account support
  • Priority support
Best value

Professional

$499

one-time payment - lifetime access

Full access to all features, forever

  • All 240+ resource types (80+ AWS, 80+ Azure, 80+ GCP)
  • MCP server, no codify_batch cap
  • Unlimited resources & accounts
  • Advanced dependency mapping
  • Multi-account/subscription scanning
  • RDS, Lambda, EKS, and more
  • Module generation & best practices
  • State file management
  • Priority email support
  • Lifetime updates included

Need multiple licenses for your team? Contact us

FAQ

F.A.Q's

Common questions about Terraback

Terraback operates on a principle of zero trust andnever stores your cloud credentials. It securely uses the authentication you've already configured in your local environment via standard, official CLI tools.
The Professional license is a one-time purchase that gives you lifetime access to all 240+ resource types across AWS, Azure and GCP, advanced dependency mapping, multi-account scanning, parallel processing, and priority support. You keep all generated Terraform code forever.
Yes, absolutely. Terraback is designed for automation. You can install and run it in any CI/CD environment like GitHub Actions, Jenkins, GitLab CI, etc. For authentication in these environments, we recommend using short-lived credentials, which Terraback fully supports.
The terraform import command only pulls resources into your Terraform state file; it does not generate the corresponding HCL configuration code. Terraback does the hard work of actually writing the clean, production-ready.tf files for you, including discovering dependencies between resources.
Explore

Popular import guides & comparisons

Step-by-step guides for importing specific resources, plus how Terraback compares to the alternatives.