ProLanding page

All templates

Dusk

shadcn add @detent-pro/template-dusk

4,254 lines ·Comes with Pro

dusk.dev
Skip to content
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

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

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.

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

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.

What’s inside

Every section, top to bottom. Pick one and the page on the desk takes you there.

Make it yours

From install to your product, in the order you’d do it. Every file it names lands in your project as source.

  1. 1

    Install it

    The landing page lands in components/detent/templates/dusk, with its privacy policy, terms, 404, share image and icon beside it. It needs React 19, the Next.js App Router and Tailwind v4. First time? Set up the Pro registry once, as on the Pro page under Set up once.

    shadcn add @detent-pro/template-dusk
  2. 2

    Open it

    Render it as your home page and run your app. The bar and the footer are fixed and the closing follows the window’s scroll, so give it the whole page, not a box inside one.

    app/page.tsx
    import { DuskPage } from '@/components/detent/templates/dusk/DuskPage'
    export { homeMetadata as metadata } from '@/components/detent/templates/dusk/meta'
    
    export default function Page() {
      return <DuskPage />
    }
  3. 3

    Make it yours

    Every word, quote, price, log line and link is in one file, and every one is a placeholder. Colours and the sky are tokens in theme.ts; the README lists everything to replace before launch.

    components/detent/templates/dusk/content.ts
    export const PRODUCT = 'Acme'
    
    export const HERO = {
      title: ['Your headline', 'on two lines'],
      // …
    }
  4. 4

    Add the legal pages and the 404

    Privacy and terms are pages of their own with the same bar and footer; the footer already links to /privacy and /terms. Their text is a placeholder in LEGAL in content.ts: have a lawyer replace it.

    app/privacy/page.tsx
    import { DuskPrivacy } from '@/components/detent/templates/dusk/Legal'
    export { privacyMetadata as metadata } from '@/components/detent/templates/dusk/meta'
    
    export default function Page() {
      return <DuskPrivacy />
    }
    
    // app/terms/page.tsx: DuskTerms and termsMetadata
    // app/not-found.tsx: DuskNotFound and notFoundMetadata
  5. 5

    Set the metadata and the share image

    Put your address, title and X handle in META in content.ts. The layout shares the metadata with every page, and the share image is drawn from your product name and headline. Copy icon.svg into public/.

    app/layout.tsx
    export { metadata } from '@/components/detent/templates/dusk/meta'
    
    // app/opengraph-image.tsx
    export { default, size, contentType, alt } from '@/components/detent/templates/dusk/og'