The verification cockpit for apps your AI wrote.
Your builder cheks its own homeworkchecks its own homework — chekd is the independent verifier that works on your apps and learns your taste.
* chek = check · chex = checks · chekd = it’s been checked. Branded by default — and always defined right where it’s used. See the lexicon ↓
* Plain-language mode is on — the playful spellings (chek, chex, chekd) are written out as check, checks, and checked. Flip it back any time with the toggle up top.
npx chekd <url>
…or paste it to your coding agent: “run npx chekd on this app and walk me through what’s broken.”
First run sets itself up — chekd auto-installs a private copy of Chromium to walk your app. Nothing to download by hand.
- Shareyou drive + talk, chekd logs
- Scanit walks & flags findings
- Fixyou dispatch each card
- chekd ONit fixes & re-cheksre-checks for you — paid
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.
That's the whole point: chekd isn't a one-time audit you run and forget. It's a tool that 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 paid
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. Kill the slop you shipped.
chekd is the verification cockpit for apps your AI wrote — it amplifies your taste, it doesn’t grade you. You vibe-coded something, shipped it, and never went back to polish it. chekd is how you go back.
Paste one line
Drop npx chekd into your AI setup or your terminal. No account, no upload, no config to wade through.
ChekCheck your app
chekd opens the cockpit and walks your shipped app, probing every control it can find — and telling you what it couldn’t reach.
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.
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. Walking your app, the findings, and quieting the noise never cost a cent. 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.
Everything objective — walking your app, catching what’s visibly wrong, quieting what you dismiss — is free, unlimited, local, forever. The paid tier is the taste layer: chekd learning to nag exactly like you, and fixing accordingly.
unlimited local chexchecks — no account, no card, no upload
- ✓Unlimited local chexchecks — walk any web app as often as you like, $0 every time
- ✓The FUNCTION lens — does it work? Every control probed; dead, broken, and inert clicks caught
- ✓The CONTENT lens — does it read right? “undefined”, mojibake, and leftover placeholder keys caught
- ✓The LAYOUT lens — does it look broken? Overflow, overlap, clipped text, and broken images caught
- ✓BYO any model — your subscription, a free local model, or your own key; never silently metered
- ✓Corrections always recorded — your taste corpus accrues from day one, plain files in your own repo
- ✓Dismiss hygiene — what you dismiss stays dismissed, exact-match, every future chekcheck
Free is the floor, not a trial — the objective layer never expires and never meters.
pay once — unlock forever
- +Taste intelligence — priors that generalize from your corrections: “you corrected something like this before”, surfaced before you ask
- +My-style profile — “that’s my style” teaches it your look, chek over chekcheck over check
- +The DESIGN lens — observations on balance, density, and feel; options offered, never verdicts
- +FULLFIX apply — Fix it writes the fix on a
qa/branch; main never moves, you merge - +The chekd-ON loop — approve fixes and chekd applies, re-walks, and verifies — bounded, never “until perfect.”
Be first when it ships — drop your email and we’ll ping you at launch. Your corpus is yours on either tier; corrections are recorded free from day one, so waiting loses nothing.
A trusted copilot, never a critic.
Subjective findings are suggestions to confirm — only the deterministic ones (a button that throws, “undefined” in the page) get stated flatly. Plain language, encouraging, 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.
- 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.
- AI-powered QA automatically fixed your app.Overrides the builder; hype, not honesty.