Skip to content
Dusk
CustomersPricing
Talk to usLog inStart free

Dusk

  • How it works
  • What it watches
  • Shadow branches
  • Pricing

Watches

  • Policies
  • Secrets
  • Migrations
  • Deploys

Works with

  • GitHub
  • GitLab
  • Slack
  • Your CI

Learn

  • Docs
  • Changelog
  • Guides
  • Questions

Company

  • Customers
  • About
  • Careers
  • Contact

Trust

  • Security
  • Privacy
  • Terms
Log inStart free
  • Dusk

    • How it works
    • What it watches
    • Shadow branches
    • Pricing

    Watches

    • Policies
    • Secrets
    • Migrations
    • Deploys

    Works with

    • GitHub
    • GitLab
    • Slack
    • Your CI
  • Learn

    • Docs
    • Changelog
    • Guides
    • Questions

    Company

    • Customers
    • About
    • Careers
    • Contact

    Trust

    • Security
    • Privacy
    • Terms
  • Customers
  • Pricing
  • Talk to us
NewShadow branches for every fix

The backend agent
for AI‑built software

Every table, secret and migration, watched and fixed while you sleep. Nothing destructive without a yes.

Start free$npx dusk init

Free for one project. No card needed.

NorthwindLumenHalcyonKiteTandemParallel
NNorthwind⌄
Inbox3
Findings
Tables
Secrets
Migrations
Backups

Databases

prod-us-east
prod-eu
staging
MCMaya Chen
FindingsScanning 214 tables
Needs you 2
DUSK-214Row-level security off on orders2m
DUSK-213Service key in client bundle41m
Fixed today 6
DUSK-212Missing index on sessions.user_id2h
DUSK-211Admin route without auth check3h
DUSK-210Migration drops column in use5h
DUSK-209Webhook secret logged in plain text6h
DUSK-208Unbounded query on events8h
DUSK-207Backup older than 24 hours9h
Watching 14
DUSK-206Slow policy on invoices1d
DUSK-205Unused role with write access1d
DUSK-204Rate limit missing on /login2d
Findings › DUSK-214MCJL

Row-level security off on orders

Criticalpublic.ordersanon → 18,422 rows0042_add_orders.sqlby cursor-agent

Dusk anon key read 18,422 rows from public.orders without a session · 2m

Dusk traced to 0042_add_orders.sql, merged 11:42 pm, no policy · 2m

Dusk drafted 0043_orders_rls.sql and verified on shadow/fin-214 · 1m

supabase/migrations/0043_orders_rls.sql+4 −0
1 -- 0043_orders_rls.sql
2+alter table public.orders enable row level security;
3
4+create policy "owners read own orders"
5+ on public.orders for select
6+ using (auth.uid() = user_id);

Shadow branch: anon reads 0 rows · owners still read their own · 214/214 tests pass

ReviewApply to prod⌘↵

What Dusk promises

@duskfind who can read the payments table, and fix it.
Reads the schemaReads the last day of logsReads the code that queries itWrites to the database
Opened a pull requestYou read it and merge it. Dusk never pushes.

Reads, never writes

Dusk connects read only. Every fix arrives as a pull request you merge yourself.

Refunds open to the anon keyFound in three places at once.
api/refunds.tsrefundstablereceiptsbucketTests all three on a shadow branch
One fix for all threeA route guard, a policy and a bucket rule, in one change.

Every layer at once

Code, database and cloud are read together, so a fix in one never breaks another.

STRIPE_KEYrotatedShipped with web 3.2.0
New key liveOld key kept until you revoke itPrevious release kept warmDown migration written
Undo all of it⌘ZOne step back to how it was.

Every fix has a way back

Each fix ships with its undo: a down migration, a rollback, the old key kept until you say so.

Ship fast. Wake up to fixes.

Dusk finds what’s exposed, fixes it on a shadow branch, and waits for a yes before anything reaches production.

‹All findingsOrders table readable by anyone#214MCReady for review
D

Maya joined the investigation

Policy diffAffected rowsRecent deploys
Ask Dusk anything↑
InvestigationReportFix
Maya

Orders table readable by anyone

Criticalpublic.orders18,422 rowsProductionby cursor-agent

What’s going on

At 11:42 pm the anon key read 18,422 rows from public.orders without a session. Row level security is off, so anyone with the URL can read every order.

Reads by the anon key, last 24 hours18,422 at 11:42 pm
12 am12 pmnow

Why it happened

Migration 0042_add_orders.sql created the table on Tuesday. The agent that wrote it never added a policy, and nothing in CI checks for one.

Findings

The table has no row level security policy

The anon key is used by the public web app

Two more tables were created the same way

Find what’s exposed across tables, policies, secrets and migrations, with the evidence for each one.

Fix

Every finding gets a fix, written and tested on a shadow branch before anyone sees it.

Lock public.invoices to row owners

dusk/213 · merged by Maya 2 days ago

Lock public.orders to row owners

dusk/214 · tests passed on shadow branch

Testing the fix on a shadow branch

Wait for a yes

Anything that drops, deletes or touches production stops and waits for a person.

Drops a columnTouches productionRotates a key
Apply to production⌘↵

Dusk watches what breaks at night. Policies, secrets, migrations and deploys, checked while you sleep.

Every table gets a policy. Agents create tables faster than anyone reviews them. Dusk reads every one each night and proves what a stranger can see.

Explore Policies›
  • Row level securityEvery table checked for a real policy, not just RLS on.
  • Read as a strangerDusk replays the anon key to show exactly what leaks.
  • Policy historyWhat changed, in which migration, and by whom.
  • Fixed on a branchThe policy is written and tested before you look.
D
NorthwindFindings/#214

public.refundsCritical

Rows18,422Since0045_refunds.sqlFound bynightly scanNov 2, 1:18 AM

RunEvidenceFix

Dusk’s run

›Read schema
›Check row level securityoff
›Replay the anon key18,422 rows readable
›Write the policy

1alter table refunds enable row level security;

2create policy owners_read on refunds

3 for select using (owner_id = auth.uid());

4create policy owners_write on refunds

5 for insert with check (owner_id = auth.uid());

6-- 6 of 6 policy tests passed

›Test the policy
›Open dusk/215
›Wait for review

Built with AI. Kept safe by Dusk. What teams say after their first month.

Read all stories›
“We closed an open invoices table before breakfast. Dusk found it overnight and the fix was ready when we woke up.”
Read Northwind’s story→
Priya RamanCTO, Northwind
invoices locked to owners at 6:10 am
“It’s the first security tool we never muted. It leaves a note instead of paging us at night.”
Read Halcyon’s story→
Daniel OkaforFounder, Halcyon
0 pages in 30 nights
“It reads every deploy, even the ones at 3 am. Our on-call has been quiet for a month.”
Read Tandem’s story→
Lena FischerEngineering Lead, Tandem
214 deploys read this month
“Nobody on our team is a security engineer. We ship with Cursor every day, and Dusk is the one who checks.”
Read Lumen’s story→
Sam OrtizCo-founder, Lumen
1,240 changes read this month
“Two migrations would have dropped a policy last month. Both stopped and asked first.”
Read Kite’s story→
Ana DuarteStaff Engineer, Kite
2 migrations held for review

Dusk watches over 1,200 apps built with AI. From weekend projects to Series B teams.

Customer stories →

Priced by what Dusk watches. Free for one project. Pay when there is more to watch.

Hobby

For the project you ship on weekends.

$0per month

One project

  • A nightly scan of one project
  • Fixes opened as pull requests
  • A short report each morning
Start free

Team

Most teams

For startups shipping with agents every day.

$19per project, per month

2 to 10 projects

  • Everything in Hobby
  • A check on every push in CI
  • Fixes tested on shadow branches
  • Approvals from Slack
Start a 14 day trial

Scale

For teams with many apps and one backend owner.

$15per project, per month

11 to 25 projects

  • Everything in Team
  • Custom policies and rules
  • SSO and an audit log
  • Priority support
Start a 14 day trial

More than 25 projects? Volume pricing, SSO and a named engineer, set together. Talk to us →

Questions, answered. Everything teams ask before they let Dusk near production.

Ask us directly›

No. Dusk writes and tests every fix away from production, then opens a pull request. Anything that drops, deletes or touches production stops until a person approves it.

A read only database role and a GitHub app that can open pull requests. Dusk never holds a key that can write to production.

Dusk reads your schema, policies and query metadata. When it proves a leak it counts the rows a stranger could read, it does not copy them.

Postgres on Supabase, Neon, RDS or your own servers, with deploys from GitHub Actions, Vercel or any CI that can run one command.

Every change ships with a way back. Migrations come with a down file, and rolling back is one click from the finding.

A scanner hands you a list. Dusk proves what is exposed, writes the fix, tests it, then asks before anything ships. You review one pull request, not three hundred warnings.

Yes. On Scale, the runner can live in your VPC, so nothing leaves your network except the pull request.

About five minutes. Connect the database with a read only role, install the GitHub app, and the first scan runs that night.

Let Dusk watch tonight.

Start freeTalk to us
ProductHow it worksPricingChangelogDocs
SocialXLinkedInGitHub
LegalTermsPrivacyDPA

© 2026 Dusk, Inc.

Dusk

Security for software built with AI.

Dusk