2
1 Comment

Shipped v0.1.0 of an open-source Terraform drift scanner — 0 stars, looking for first feedback

18, based in Kerala, India. Start college in about 9 months. Wanted to build something real before that — not a SaaS wrapper, something that solves an actual infra problem.

The problem: Terraform says your infrastructure looks one way. AWS console shows it looks another way, because someone made a manual change. Most teams find out during an incident, not before. Existing drift tools tell you it happened. None of them tell you why it matters or what to do about it.

What I built — SynchroIaC:

  • GitHub Action scans your Terraform state against live AWS (EC2, S3, IAM for now)
  • Risk-classifies every drift: low/medium/high/critical
  • AI explains what changed and why it matters
  • One-click fix PR generation
  • Your AWS credentials never leave your own GitHub Actions runner
    Built in 2 days using Codex/Jules as implementation, me as architect. Stack: Go scanner, Next.js API on Vercel, Supabase, Groq for AI explanations.

Where I'm at: v0.1.0 shipped, live dashboard, listed on GitHub Marketplace, 11/11 e2e tests passing. Zero stars. Zero users. Posted on Dev.to yesterday, no traction yet.

What I actually want from this post:

Not validation. I want someone who runs Terraform in production to tell me if this solves a real problem or if I built a solution looking for one. I can't answer that myself — I've never run infra at scale.

If you've dealt with drift before, I'd genuinely value 5 minutes of your time looking at this and telling me what's missing or what's wrong.

Repo: github.com/Jeffrin-dev/SynchroIaC
Dashboard: synchroiac-io.vercel.app

Happy to answer anything about the build, the architecture decisions, or why I made specific tradeoffs.

on June 30, 2026
  1. 1

    This is already in a real category of pain where “detecting drift” is solved, but “understanding blast radius and deciding what to do next” is still where teams slow down or make mistakes. The risk scoring + PR generation direction is interesting because it moves from visibility to action, which is usually where these tools actually become useful in production.

Trending on Indie Hackers
I Was Picking the Wrong SaaS Tools for Two Years. Here's the Mistake I Finally Figured Out. User Avatar 120 comments Drop your landing page URL. I'll use Ferguson to tell you why visitors might be leaving User Avatar 102 comments Ferguson is LIVE on ProductHunt today... so I audited their homepage first! User Avatar 35 comments I sold $6,773 in 2 weeks, with almost no existing community. User Avatar 32 comments Why Remote Teams Stop Talking (And Don't Even Notice It) User Avatar 24 comments Built a local-first Amazon profit-by-SKU + QuickBooks/Xero journal tool. Looking for founding users. User Avatar 23 comments