GitDrift - Real-Time Infrastructure-as-Code Drift Detection

Watches your Terraform, CloudFormation, or Pulumi repos for actual cloud state divergence, alerts when reality doesn't match code, and auto-generates fix commits with one click.

Difficulty

intermediate

Overview

Infrastructure teams waste hours debugging 'why is this security group rule missing?' by manually comparing cloud consoles to git repos. GitDrift automatically syncs your IaC repo with actual cloud state, detects divergence in real time, and generates corrective code changes. It's like GitHub's native drift detection but for multi-cloud and self-hosted infrastructure.

Key Features

▸Real-time drift detection via periodic state sync
▸Auto-generate corrective Terraform/CloudFormation PRs
▸Slack/email alerts with context
▸Multi-cloud support (AWS, GCP, Azure)
▸Audit log of all drift events and fixes

Target Audience

DevOps engineers and infrastructure teams at mid-market tech companies (50-500 employees). Estimated 8,000 teams actively using Terraform who experience drift weekly.

Tech Stack

Next.js, FastAPI, Terraform Cloud API, AWS SDK, Anthropic Claude API, Postgres, GitHub Actions — build with Cursor for backend, Lovable for dashboard, v0 for monitoring UI.

Time to Ship

3 weeks

Business Model

SaaS subscription per repository or team

Required Skills

IaC platforms (Terraform), cloud APIs (AWS, GCP), GitHub integration, Python backend.

Resources

Terraform Cloud API docs, AWS SDK examples, GitHub webhooks guide, Claude API for code generation.

Monetization Path

Free tier monitors 1 repo. Paid starts at $99/month for 5 repos plus slack alerts and auto-fix generation.

Competition Level

Low

Estimated Monthly Cost

AWS API calls: $35, Terraform Cloud API: $15, Postgres (Supabase): $25, Vercel: $20, Claude API (code generation): $60. Total: ~$155/month at launch.

Revenue Potential

$99/month × 100 teams at month 4 = $9,900 MRR. $299/month × 150 teams at month 10 = $44,850 MRR.

Build It Right

Core User Journey

Sign up → connect AWS account → select Terraform Cloud workspace → GitDrift syncs state → detects first drift in 24h → customer approves auto-generated fix.

Success Definition

A mid-market DevOps team discovers the product via ProductHunt or word-of-mouth, activates monitoring on 3 repos, detects a real drift event, auto-generates a fix PR, approves it, and renews for month 2.

Architecture Pattern

GitHub webhook → Lambda → state comparison engine (Postgres) → Claude API generates fix PR → GitHub PR created → Slack notification fired.

Integration Points

Terraform Cloud API for state sync, AWS SDK for resource inspection, GitHub API for PR creation, Slack API for alerts, Claude API for code generation.

Data Model

Team has many Repositories. Repository has many DriftEvents. DriftEvent has one ProposedFix. ProposedFix may have one ApprovedPR. Team has many Credentials (encrypted).

Avoid These Pitfalls

Storing unencrypted cloud credentials will kill trust immediately — use AWS Secrets Manager or HashiCorp Vault from day one. Do not attempt multi-cloud support before nailing AWS. Do not over-promise auto-fix accuracy — start conservative, only fix simple divergences.

V1 Scope Boundaries

V1 excludes: Kubernetes drift detection, cost anomaly detection, team collaboration approval workflows, white-label, custom Terraform module analysis.

Example Use Case

Sarah manages infrastructure for a 200-person SaaS company with 15 Terraform modules. A contractor manually adds a security group rule via AWS console. GitDrift detects it within 5 minutes, generates a PR to sync it to code, Sarah reviews and merges. The divergence is caught before it causes compliance issues.

Challenges

Requiring customers to grant cloud API read access is a trust barrier. Terraform state file secrets management adds complexity.

Success Metrics

Week 1: 80 signups. Week 3: 15 paid teams. Month 2: 65% retention, $2k MRR.

MVP Scope

Single cloud (AWS) support, Terraform Cloud sync, drift detection, Slack alerts, GitHub PR generation, basic dashboard.

Launch & Validation Plan

Interview 15 DevOps leads at mid-market companies about drift pain. Build landing page with case study. Recruit 8 beta teams for 4-week pilot.

Customer Acquisition Strategy

First customer: Cold email 30 DevOps engineering managers at Series B/C companies mentioning specific pain (manual drift reconciliation). Offer 3 months free for detailed feedback. Ongoing: ProductHunt, r/devops, HashiCorp forums, LinkedIn DevOps community, sponsorship of Terraform webinars.

Competitive Advantage

Terraform Cloud's native drift detection is basic and slow. GitDrift is 4x faster, works across platforms, and auto-generates fixes.