The backend agent
for AI‑built software
Every table, secret and migration, watched and fixed while you sleep. Nothing destructive without a yes.
Free for one project. No card needed.
Row-level security off on orders
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
1 -- 0043_orders_rls.sql2+alter table public.orders enable row level security;34+create policy "owners read own orders"5+ on public.orders for select6+ using (auth.uid() = user_id);
Shadow branch: anon reads 0 rows · owners still read their own · 214/214 tests pass
What Dusk promises
Reads, never writes
Dusk connects read only. Every fix arrives as a pull request you merge yourself.
Every layer at once
Code, database and cloud are read together, so a fix in one never breaks another.
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.
Maya joined the investigation
Orders table readable by anyone
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.
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
Wait for a yes
Anything that drops, deletes or touches production stops and waits for a person.
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.
public.refundsCritical
Rows18,422Since0045_refunds.sqlFound bynightly scanNov 2, 1:18 AM
RunEvidenceFix
Dusk’s run
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
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
Dusk watches over 1,200 apps built with AI. From weekend projects to Series B teams.
Customer storiesPriced 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
Team
Most teamsFor 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
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
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 directlyNo. 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.