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:
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.
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.