Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?


Failed to load latest commit information.
Latest commit message
Commit time
Dec 6, 2021
Dec 6, 2021


Measures infrastructure as code coverage, and tracks infrastructure drift.
IaC: Terraform. Cloud providers: AWS, GitHub, Azure, GCP.
⚠️ This tool is still in beta state and will evolve in the future with potential breaking changes ⚠️

Packaging status Packaging status

Why driftctl ?

Infrastructure drift is a blind spot and a source of potential security issues. Drift can have multiple causes: from team members creating or updating infrastructure through the web console without backporting changes to Terraform, to unexpected actions from authenticated apps and services.

You can't efficiently improve what you don't track. We track coverage for unit tests, why not infrastructure as code coverage?

Spot discrepancies as they happen: driftctl is a free and open-source CLI that warns of infrastructure drifts and fills in the missing piece in your DevSecOps toolbox.


  • Scan cloud provider and map resources with IaC code
  • Analyze diffs, and warn about drift and unwanted unmanaged resources
  • Allow users to ignore resources
  • Multiple output formats


Get Started





To learn more about compiling driftctl and contributing, please refer to the contribution guidelines and the contributing guide for technical details.

This project follows the all-contributors specification and is brought to you by these awesome contributors.

Build with ❤️️ from 🇫🇷 🇬🇧 🇯🇵 🇬🇷 🇸🇪 🇺🇸 🇷🇪 🇨🇦 🇮🇱 🇩🇪

Helping you get started

We have 30 min slots for 1:1 tech discussions and overviews twice a day to help you get started and collect users feedback.

Feel free to book a slot.

Security notice

All Terraform state and Terraform files in this repository are for unit test purposes only. No running code attempts to access these resources (except to create and destroy them, in the case of acceptance tests). They are just opaque strings.