Skip to main content
Home/Recipes/Automated drift tracking with an API key
Automation

Automated drift tracking with an API key

DeveloperQAEnterprise

Overview

Generate an API key, then pass --key to the CLI. Every run uploads a snapshot to your account and is scored against the previous one for that domain. Drift over time with nothing to save by hand.

The manual baseline workflow works for occasional checks, but drift is continuous and deserves a continuous instrument. Generate an API key in the Dembrandt App under API keys, then pass it to the CLI with --key. Each run uploads the extraction to your account under the site's domain and scores it against the last stored snapshot. There is nothing to save or drag: the history lives in the cloud, grouped by domain, with a timeline you can scrub and a drift report between any two points. Wire the same command into CI so every deploy records a snapshot, and the brand gets a commit log. When a color shifts, you see which release introduced it. Keys are secret and shown once, so store them as a CI secret and never in the repo. Per-account extraction limits apply: 20 per hour, 200 per day, 500 per week.

Push a snapshot to your account

Terminal
dembrandt app.example.com --key dmb_xxx

Push from a container or CI runner

Terminal
dembrandt app.example.com --key dmb_xxx --no-sandbox
GitHub Actions: snapshot after every production deploy
# .github/workflows/drift.yml
# Store key as repo secret: DEMBRANDT_KEY
name: Cloud drift snapshot
on:
deployment_status:
jobs:
snapshot:
if: >
github.event.deployment_status.state == 'success' &&
github.event.deployment_status.environment == 'Production'
runs-on: ubuntu-latest
steps:
- uses: actions/setup-node@v4
with:
node-version: 24
- name: Install Chromium
run: npx playwright-core install --with-deps chromium
- name: Snapshot
env:
DEMBRANDT_KEY: ${{ secrets.DEMBRANDT_KEY }}
run: |
npx -y dembrandt@latest your-site.com --key "$DEMBRANDT_KEY" --no-sandbox
Where the history lives
# dembrandt.com/app/extractions
# Cloud column, open the domain, scrub the timeline.
# The drift panel shows what changed between snapshots.
Output

One cloud snapshot per run, grouped by domain, auto-scored against the previous one. Timeline and drift report in the App, no files to manage.

Browse all

All recipes →

56 workflows