Infrastructure drift alerts
Know when your cloud stops matching your code.
Diffindor compares what's running with what your code says, finds changes made by hand and resources nobody tracks, and tells you in Slack what changed and who did it. It runs in your own CI, so your cloud keys never leave it.
Drift in prod/network: 1 change made outside your code, 3 untracked resources
"We could just script this ourselves."
You could, and it's a good start. Then the script prints forty lines of harmless noise every night, it can't see the resources someone created by hand, nobody can tell who made the one change that matters, and the alerts end up in a channel no one reads. Diffindor is that script, with the boring parts done properly.
How it works
-
1
Add one workflow
Drop the Diffindor Action into a scheduled GitHub workflow. It uses the read-only AWS role you already give your CI.
on: schedule: [{ cron: "0 6 * * *" }] jobs: drift: runs-on: ubuntu-latest steps: - uses: diffindor/action@v1 with: stacks: live/** -
2
It checks everything
Every project in your repo, plus the resources in your cloud account that no code manages, on whatever schedule you set. Differences you've marked as expected are muted, so you only hear about real drift.
-
3
You get one clear message
Slack shows what changed, where, and who changed it, looked up in your cloud's audit log with your own role. A short history shows whether it keeps coming back.
Works with
- Terraform
- Terragrunt
- OpenTofu
- AWS
- GitHub Actions
- Slack
More tools and clouds are on the way.
Your keys stay yours
It runs in your CI with your credentials. Diffindor never holds cloud keys and never sees your state.
Read-only
It only reads. It never applies, imports or changes anything in your account.
Built for small teams
No sales calls, no platform to migrate to. Keep your repo layout and workflows as they are.
Pricing
- Scheduled drift checks for all your projects
- Finds resources that aren't in your code
- Slack alerts with who made the change
- Mute rules for known differences
- 30 days of drift history
Beta teams use it free and help decide what comes next.
Questions
How is this different from the big infrastructure platforms?
Their drift detection is part of enterprise plans and needs your runs to move onto their platform. Diffindor works with what you already have, in the CI you already use.
Which tools and clouds does it support?
See "Works with" above. If you need something that isn't listed yet, say so in the form below.
Does it cover Kubernetes?
No. Argo CD and Flux already handle drift inside a cluster well.
What does the beta involve?
A 20-minute call about how you catch drift today, then a couple of weeks running Diffindor on a few of your projects. It's free, and you can stop any time.
Join the beta
Two quick questions, then we'll be in touch. No newsletter, no spam.
Form not loading? Email support@vololabs.dev.