driftdetective/ddetective-frontend repository overview

⁠Cloudkeel-DD backend

The API, Celery worker and Celery beat of Cloudkeel-DD⁠, self-hosted configuration-drift detection for Terraform and Kubernetes teams. One image, three roles, chosen by the container command.

Install it with the Helm chart, not with docker run. The backend needs PostgreSQL, Redis and an OPA sidecar, and the chart wires all of them: driftdetective/d-detective⁠ (version 0.3.7, which deploys this image at 0.3.7).

helm show chart oci://registry-1.docker.io/driftdetective/d-detective --version 0.3.7

Quickstart: cloudkeel.io/quickstart⁠ · Docs: cloudkeel.io/docs⁠ · Release notes: github.com/cloudkeel/cloudkeel-dd/releases⁠

⁠Image facts

⁠Tags

• X.Y.Z: immutable. Equals the chart's appVersion; a chart release whose app did not change reuses the previous tag rather than republishing it.
• latest: moves to each new app release. Pin a version in production.
• Every published tag is the exact multi-arch manifest that passed CI; images are copied from the build registry, never rebuilt for publishing.
• 0.3.0 was removed after 0.3.1 shipped and will not return. 0.3.3 never existed on this registry. Use 0.3.2 or later.

Verify what you pulled:

docker buildx imagetools inspect driftdetective/ddetective-backend:0.3.7

Each GitHub release lists the sha256 index digest for its backend and frontend tags.

⁠How it runs

• Self-hosted, in your cluster. No telemetry, no analytics, no licence server, no update check.
• Read-only against your clouds: it needs reader roles only, and remediation ships as a pull request you review.
• Cloud credentials are encrypted at rest with a key only your install holds. Finding data leaves your cluster only through destinations you configure: notification webhooks and GitHub/GitLab remediation pull requests.
• Runs unmetered for 30 days, then converts to the Free tier (1 enabled scope, 3 users, every feature); nothing is deleted. Pricing⁠.

Scans are point-in-time. Coverage, by cloud and by how it was verified: cloudkeel.io/docs/claims/coverage⁠.

⁠Support and security

Bug reports and questions go to GitHub issues⁠. Security reports go to [email protected]⁠, never to a public issue (policy⁠).

Cloudkeel-DD is commercial, self-hosted software; the application source is not published.