your verification tool.
chekd gives you a second set of eyes: it walks your app, surfaces the dead, broken, and ugly bits, and learns your taste with every decision.
npx chekd <url>
…or paste it into your AI: “run npx chekd and walk me through what’s broken.”
- Shareyou drive + talk, chekd logs
- Scanit walks & flags findings
- Fixyou dispatch each card
- chekd ONit fixes & re-cheksre-checks for you — chekd Plus
Generic design audits tell everyone the same thing. chekd learns what bugs you.
Every time you correct a finding, chekd cements your taste. The longer you run it, the more irreplaceably yours it becomes — a loop no off-the-shelf audit can copy.
It walks your app
chekd opens the cockpit and walks your shipped app, surfacing dead, broken, and ugly findings as cards.
You correct it
Fix it, snooze it, dismiss it, or move to the next. Each call is you teaching chekd what you actually care about.
It cements your taste
Every correction is remembered. The noise you ignore quiets down; the things you care about get sharper.
The next chekcheck is yours
Run it again and it’s quiet where you said to be quiet — and louder only where you’ve cared before. Sharper every chekcheck.
Every chekcheck, it nags a little more like you.
chekd gets more yours the longer you use it — until skipping it feels like shipping with your eyes closed.
One slider, four stops.
Choose how much is you and how much is chekd — from quietly logging while you drive, to fixing and re-chekingre-checking for you. Land anywhere; every stop hands the calls back to you.
Share live
You drive and talk; chekd rides along in the browser, logging what it sees — every click observed, every error caught, your narration pinned to the moment you said it. It changes nothing. No fix, ever, at this stop.
Scan live
chekd drives; you review. It walks your app and surfaces findings as cards — you snooze or dismiss, and there’s no fix affordance at all. The first hand-off on the trust ramp.
Fix live
chekd drives; you correct and dispatch. Fix it writes a real fix on a qa/ branch in your own repo — main never moves; you review and merge it yourself.
chekd ON chekd Plus
Correct, then unleash: you approve the fixes; chekd applies them, re-walks, and verifies — bounded, never “until perfect.” Anything new it finds comes back to you.
More chekd never means less you.
Every stop up the ramp is something chekd does for you, never instead of you: it only fixes what you corrected, it re-cheksre-checks what it touched, and whatever it finds next lands back in your queue.
Paste one line. ChekCheck your app or PR. Kill the slop you shipped.
chekd is the verification cockpit for apps your AI wrote — it walks the running app, maps changed files into a test plan when a repo or PR is available, and keeps you in the chair for every fix.
Paste one line
Drop npx chekd into your AI setup or your terminal. No account, no upload, no config to wade through.
ChekCheck the surface
chekd opens the cockpit and walks your shipped app. Add a repo, branch diff, or GitHub PR when you want changed-file context too.
Dispatch a disposition
Each finding is a card: fix it, snooze it, dismiss it, or move to next. You stay in the chair the whole time.
Review the change, not just the page.
Point chekd at a repo, branch diff, or GitHub PR when you want it to plan from what changed, run the app checks, and add baseline security posture findings with reviewable evidence.
Plan from the diff
Local git diff is primary. GitHub PR context is optional and read-only by default. chekd turns changed files into required and optional steps before it runs.
Baseline security, no drama
Runtime headers, cookies, mixed content, dependency changes, and repo posture surface as normal findings with severity, confidence, and provenance.
Evidence for teams
Markdown, JSON, and SARIF exports carry redacted evidence, detector versions, policy gates, and coverage ledgers so a reviewer can see what was checked.
Built to be yours — and to stay yours.
Three commitments shape every part of chekd, from the first run to the thousandth.
Accessible to all
Real value at $0, forever — no required API key, no expertise gate. Plain language, never gatekeeping.
Make it your own
Dark + light and three themes on day one. Bring any model you like. Set the autonomy yourself — from watch-only to fix-it-for-me.
Compounding
Every use makes it more yours and better. It learns your taste, your corrections compound, and the next chekcheck is already sharper — the flywheel.
Bring any model. Nothing uploads.
chekd is BYO-anything: ride a subscription you already have, run a free local model, or use your own key — all offered, none forced. No required account, no surprise bill, ever.
Opt into metered billing and chekd triple-checks first and points you at the free options. The cockpit ships dark + light and three themes — make it your own.
BYO any model — your subscription, a free local model, or your own key. Offered, none forced.
Nothing uploads — the only thing that ever leaves is the AI request you choose, to your provider, under their policy. Your findings, corrections, and screenshots stay on your machine as plain files in your own repo.
When you bring a paid provider, you bring and run your own CLI or API key, under your own account and that provider’s Terms of Service — chekd never resells, proxies, stores, or meters your usage.
Run a local model and nothing leaves at all. That’s the genuinely airgapped path — zero bytes off your machine.
Free forever. Pay when it starts fixing like you — or reviewing PRs.
Everything objective is free. Free remembers what you decided; paid turns those decisions into active intelligence.
unlimited local chexchecks — no account, no card, no upload
- ✓Unlimited local chexchecks — no quota, $0 every time
- ✓Share & Scan autonomy — you drive, or chekd walks and flags
- ✓FUNCTION · CONTENT · LAYOUT lenses — dead clicks, “undefined” text, broken layout
- ✓Baseline runtime security
- ✓BYO any model — never silently metered
- ✓Corrections always recorded — your dismissals stick, your taste corpus grows from day one
Free is the floor, not a trial.
Founding Member price — get in at launch and you keep this rate when the price rises later
- +Taste intelligence — your decisions become priors, surfaced before you ask
- +DESIGN lens + my-style — learns your look, chek over chekcheck over check
- +FULLFIX apply — fixes land on a
qa/branch; you merge - +chekd-ON — the highest-autonomy loop, bounded
- +PR/diff review + repo security audit
- +Policy profiles & evidence exports
Drop your email — we’ll ping you at launch.
A trusted copilot, never a critic.
Subjective findings are suggestions; only deterministic ones get stated flatly. Honest about limits — and it never judges the work you made.
✓ What it says
- The “Pay now” button doesn’t fire — want me to wire it up?Concrete, names the spot, hands the decision back.
- This label is hard to read on that surface. Bump it one step?Plain language a non-technical builder gets.
- This PR drops a defensive header on checkout. Want the evidence pack?Specific to the changed surface; no scare language.
- You dismissed this kind of thing before — want it quieted for good?Shows it’s learning you, chek over chekcheck over check.
- I might be wrong here — ignore if this is intentional.Honest about limits; never authoritative.
✗ What it never says
- Critical accessibility violation detected. Fix immediately.Alarmist, gatekeeping, treats a finding as a verdict.
- Your design is bad. Here’s what a real designer would do.Judges the creative work. Never do this.
- 17 issues found across 4 severity tiers (see dashboard).Noisy, jargon-heavy, dumps work on the user.
- SOC 2 compliant after one scan.False compliance claim. chekd can produce evidence; it cannot certify you.
- AI-powered QA automatically fixed your app.Overrides the builder; hype, not honesty.