Hourly secret scans for shipping-fast teams
Deploys land hourly; so should checks. 3 projects, hourly cadence, Slack alerts — $29/mo. Findings visible at every tier.
Interval-to-risk logic for agent-era deploy frequency.
What hourly buys
Daily scans leave twenty-three-hour windows where a reintroduced key ships silently. Hourly shrinks that to sixty minutes — catching a regression during standup instead of during invoice review.
Plan mechanics
Indie covers three projects hourly with eighty chunks per scan and Slack added to email. Changes take effect immediately; visibility rules never move with billing.
When daily suffices
Static marketing sites and dormant internal tools move slowly enough for daily truth. Anything with active feature flow deserves hourly honesty.
Pairing with previews
Point spare slots at volatile preview URLs during risky migrations — temporary surveillance beats permanent surprises.
The bigger picture
It helps to name the economics honestly. Fixing this class of leak costs minutes when caught at deploy time and days when caught at invoice time, because by then the credential has been harvested, validated, resold or drained — often all four. Detection latency is the entire game, which is why the monitoring half of KeyDrift exists alongside the scanning half.
How KeyDrift reports this exact finding
When KeyDrift finds this on your deployment, the report shows a masked value (first 8 and last 4 characters only), a salted fingerprint for tracking, the exact chunk filename carrying it, and a severity with written rationale. Public-by-design neighbours — anon keys, publishable keys, Firebase web constants — appear as informational context rather than noise, because knowing what should be there is what makes the real findings credible.
Manual check, step by step
A five-minute version you can run anywhere: view-source on the landing page, copy every src= script URL, fetch each and search the results for eyJ. It misses manifest-only chunks and streamed payloads — which is precisely the gap between "I checked" and "it is clean" — but it catches the loud majority and builds the pattern-recognition that makes scanner output legible.
Close the loop with monitoring
Monitoring closes the loop that one-time verification leaves open. A scheduled scan refetches everything, diffs against history, and fires only on transitions: created, regressed, resolved. Regression alerts matter most here — they fire when a previously fixed finding returns, which in agent-era codebases is less a possibility than a schedule.
What the plans change
- Free $0 — 1 project · daily scans · email alerts · findings always visible.
- Indie $29/mo — 3 projects · hourly · Slack added · 80 chunks per scan.
- Team $89/mo — 15 projects · every 15 minutes · Discord + webhooks · 150 chunks.
- Growth — from $249/mo, quoted display-only until checkout ships.
The constant across every tier: plans limit how much is watched, never what a scan found. Visibility is structural, not promotional — asserted by tests over the entitlements model itself.
Common questions
Cancel anytime?
Yes; downgrades stop delivery channels, never visibility of past findings.
Annual pricing?
Ten times monthly — effectively two months free.
Run a free scan at keydrift.dev/scan — paste a URL or the bundle source itself, no account. Findings arrive masked, with the exact chunk they live in.