open-source · runs in your ci · €19/mo

know the moment someone changes your infrastructure by hand

a tiny job in your own CI compares your Terraform state with reality and pings Slack the moment something changes outside your code. your credentials never leave your pipeline.

no demo to sit through. you'll know when it's live.
in sync scanning drift detected
drift detected 2m ago · staging-ci
production-network drifted
1 security group changed outside terraform
~ aws_security_group.web
+ ingress 22/tcp from 0.0.0.0/0
added in console · 9:24 · by an IAM user
the product is this message

not the dashboard. the slack ping on the day it bites.

drift is invisible until a confusing terraform plan eats forty minutes of someone's afternoon. driftd makes it loud at exactly the right moment — and silent every other day.

>_ driftd APP 9:24
production-network drifted
1 security group changed outside terraform
aws_security_group.web · ingress 22/tcp from 0.0.0.0/0
added in console · stack staging-ci
  • day 0
    2am incident.someone hot-fixes a security group in the console and forgets it.
  • day 1
    ~10 min to live.sign in, create a stack, paste a 5-line workflow. then forget us.
  • day 9
    the alert above lands.names the exact resource and diff. fixed in five minutes.
how it works

it runs where your credentials already live.

the agent runs inside your own CI — the place that already has cloud access for terraform plan. only structured findings cross the wire. never state files, never secrets.

01

runs in your ci

a single binary checks for drift on every pipeline run, using credentials that never leave your environment.

02

only findings leave

resource names and diffs are posted outbound to our API, like a webhook. we never connect into your infrastructure.

03

you get pinged

a precise Slack alert names the resource and the change — plus run history and a weekly digest in the dashboard.

 .github/workflows/driftd.yml
# add five lines to any pipeline
- uses: driftd/check@v1
  with:
    token: ${{ secrets.DRIFTD_TOKEN }}
    dir:   ./infra
why you can run this

asking for cloud credentials is a non-starter. so we don't.

open source

read the agent yourself

the thing that touches your infrastructure is open source. audit it, fork it, pin the version.

zero secrets out

credentials stay in your ci

only findings cross the boundary. there's a free mode that prints locally and sends nothing at all.

human in the loop

we propose PRs, never apply

fixes arrive as pull requests a person merges. driftd never changes your infrastructure for you.

pricing

flat. no per-resource fees.

anything that runs once and prints is free. memory, aggregation and notifications are paid.

free
€0
  • open-source agent
  • drift checks in CI
  • output in build logs
  • zero data out mode
team
€19 / month
  • dashboard + run history
  • slack alerts & routing
  • "mark as expected" rules
  • multiple stacks
  • weekly digest
pro later
€49 / month
  • AI triage across findings
  • AI-drafted fix PRs
  • who-did-it correlation
  • cost trend graphs
we're validating before we build

drop your email. we'll tell you the day it's live.

if enough people want this, we build it. that's the whole plan — and you'd be helping shape it.