chekd
chekd
local-first · PR-aware · nothing uploadsruns on your computer · checks pull requests · nothing is sent anywhere

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.

localhost:5173 / checkout
walking
brokenbtn.checkout

“Pay now” does nothing on click — handler never bound.

findingh2.pricing

“undefined” is showing in visible text — leftover from a missed variable?

quietedtooltip nit

You dismissed this last chek — staying quiet.

learning your taste
sharper every run
The autonomy ramp
  1. Shareyou drive + talk, chekd logs
  2. Scanit walks & flags findings
  3. Fixyou dispatch each card
  4. chekd ONit fixes & re-cheksre-checks for you — paid
You choose how much human vs. AI — the slider is always yours. Meet the four stops ↓
01The correction flywheel

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.

ChekCheck

It walks your app

chekd opens the cockpit and walks your shipped app, surfacing dead, broken, and ugly findings as cards.

Dispatch

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.

Learn

It cements your taste

Every correction is remembered. The noise you ignore quiets down; the things you care about get sharper.

Chek againCheck again

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.

02The autonomy slider

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.

Stop 1

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.

Stop 2

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.

Stop 3

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.

Stop 4

chekd ON

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.

03How it works

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.

Step 01

Paste one line

Drop npx chekd into your AI setup or your terminal. No account, no upload, no config to wade through.

Step 02

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.

Step 03

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.

$ npx chekd
⟨✓⟩ chekd · the verification cockpit
cheking localhost:5173 …
broken  checkout button has no handler → fix
finding “NaN” in the cart total text → snooze
security changed route dropped a defensive header → review
fixed  checkout handler — on qa/run-42, main untouched
• quieted tooltip nit — you dismissed it last chek
⟨✓⟩ cards dispatched · it’s been chekd
04PR & security review

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.

01

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.

02

Baseline security, no drama

Runtime headers, cookies, mixed content, dependency changes, and repo posture surface as normal findings with severity, confidence, and provenance.

03

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.

Enterprise spine: policy profiles, local credential references, audit exports, and SOX/SOC2-aware evidence packs are being staged behind release gates. chekd is not a pentest, full vulnerability scanner, compliance certification, or auto-commenting PR bot. Write-back to GitHub only happens when you ask. Team workflows: [email protected].
05Principles

Built to be yours — and to stay yours.

Three commitments shape every part of chekd, from the first run to the thousandth.

01

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.

02

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.

03

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.

06Your model · your machine

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.

A subscription you already pay forchekd prefers riding what you’ve got
A free local model (Ollama)runs entirely on your machine — $0 Free · airgapped
Your own provider keyopt-in & metered — chekd triple-checks first

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.

Nothing uploads

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.

07Pricing

Free forever. Pay when it starts fixing like you — or reviewing PRs.

Everything objective for a local URL stays free: walking your app, catching what’s visibly wrong, quieting what you dismiss, and baseline runtime security. Paid tiers add the taste loop, fix loop, PR review, repo security, policy, and richer evidence exports.

Free forever
$0

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
  • Baseline runtime security — passive checks for headers, cookies, mixed content, and obvious client-side exposure
  • 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.

chekd Pro coming soon
$9.99/mo

launch target — final price may change before release

  • +PR/diff review workflow — map changed files into an editable, deterministic test plan
  • +Repo & dependency security audit — posture and advisory checks without pretending to be a pentest
  • +GitHub PR context — read-only by default; comments or checks only after an explicit action
  • +Policy profiles — local schema-versioned rules for what should warn, fail, or require approval
  • +Credentialed workflows — local secret references and safe-active checks with one-run approval
  • +Evidence exports — richer Markdown, SARIF, JSON, stats, and coverage bundles

Pro layers on top of the local-first product — it never meters your model usage, uploads your repo, or writes back to GitHub without your approval.

08How it talks

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.
  • 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.
Copied to clipboard