Pwnly takes your GitHub repository through four layers of analysis, reproduces access-control and payment bugs in an isolated sandbox with fake users, and opens a fix that builds and no longer lets the exploit through.
Works today with Node.js and Next.js apps (Supabase-style auth) · read-only repository access
Any signed-in user can read another customer's invoice by changing the id.
proof · roles tested: user_a, user_b
$ user_b GET /api/invoices/1042
...
waiting for the probe
expected 403 · got ?
Sample data from an illustrative scan. Not a customer.
4
analysis layers
Cheap deterministic checks first, deep verification only where it matters.
5
fake roles per test
Anonymous, two ordinary users, an admin and an unpaid user.
0
requests to your live site
There is no field to enter a target. Tests run on an isolated copy.
~90s
to a first pre-scan
Measured on our own repositories. Your numbers will vary.
01Product
A score, a ranked list, the exact request that broke it, and a patch you can review. Click through a sample.
Everything found, sorted by risk and by how sure we are.
62/ 100
Security score
2 critical · 2 high
1 medium · 1 low
Sample data from an illustrative scan. Findings are labelled potential, confirmed or tested safe.
02How it works
Each layer narrows the field. What gets reproduced is labelled confirmed; the rest stays labelled potential or tested safe.
Layer 1·Included in the free pre-scan
Leaked keys, an exposed Supabase service_role, tables without row-level security, wildcard CORS and vulnerable packages. Deterministic rules, no AI guesswork.
repo scan · deterministic rules
Layer 2·Included in the free pre-scan
We map your API routes, auth, billing and webhooks, then write concrete, testable hypotheses: who should not be able to do what.
route map · hypotheses (unverified)
Layer 3·Launch Pass and Pro
Your app boots in a throw-away container with no network and fake data. Five fake roles probe every route the hypotheses point at.
sandbox · no network · fake users · observed status codes
user_b read user_a's invoice: expected 403, got 200. Reproduced.
Layer 4·Launch Pass and Pro
A weakness only counts if the exploit reproduces. The fix only ships if it builds, type-checks, passes our content checks and the exploit stops working. You review and merge.
fix · invoices/[id]/route.ts
- const row = await db.invoices.find(id)+ const row = await db.invoices.find({ id, owner: user.id })
03Attack surface
Pwnly probes each route with fake roles. Flip the switch to see the same app after the verified fixes.
3 reproduced · 3 potential · 2 tested safe
04What we touch
1 · Read
Your repository
Read-only access to the repositories you choose. Known secret patterns are replaced by placeholders before any excerpt reaches an AI model.
2 · Test, inside the boundary
Isolated sandbox, no network
A copy of your app, built from your code, destroyed when the scan ends.
3 · Report
Findings and a fix
Each finding is labelled potential, confirmed or tested safe. A fix waits as a pull request for you to review.
Your live site and production data never contacted
There is no field to enter a target. Pwnly cannot be pointed at a URL, an IP address or a system you did not connect.
05Why Pwnly
The difference is what lands in your inbox: a list of maybes, or a reproduced bug with a fix you can verify.
Many scanners
Pwnly
Flag a pattern that looks risky
Reproduces the bug with fake users, or reports it as tested safe for that test
Leave triage to you
Labels every finding: potential, confirmed or tested safe
Suggest a code change
Ships a fix only after build, types, content check and exploit replay pass
Often need a live target to test
Tests an isolated copy of your code. Your live site is never contacted
Produce one report per run
Re-tests on every pull request (Pro)
You merge on a diff and a warning
You merge on proof: the same request, before and after the fix
06Trust
Security tools read your source code. These are the controls between your code and everything else.
You choose the repositories. Disconnect the GitHub App at any time and scans stop at once.
Credentials that match known secret patterns become placeholders before any excerpt reaches an AI model, and are only restored locally when a patch is written.
Every reply is parsed through strict schemas. You see validated findings and fixes, never prompts or transcripts.
Repository content is untrusted data. Paths, endpoints and patches are checked by code, not by instructions to a model.
Per organization and user, kept for a year, so misuse can be traced and an account suspended in minutes.
Access follows Anthropic's Supported Regions Policy. The preview is invite-only.
07Pricing
$0layers 1 and 2
$79one-time, per repository
$99per month
Payments by Stripe. Cancel Pro anytime. Purchases open when the preview does.
08FAQ
No. Every dynamic test runs against a throw-away copy of your own code in a sandbox with no network and fake data. There is no way to enter a URL or an IP address.
Excerpts of security-relevant files are processed by Claude models from Anthropic. Secrets are replaced by placeholders first. Anthropic may retain inputs and outputs and review them for safety, as our Terms and Privacy Policy explain.
No. Pwnly automatically verifies a defined class of problems: access control, ownership and payment logic, plus secrets, configuration and dependencies. It does not replace a manual penetration test.
We have not published accuracy numbers yet, and we will not claim any we cannot measure. Every finding is labelled potential, confirmed or tested safe, and only reproduced weaknesses are called confirmed. A clean result means those tests passed, not that the app is safe.
Node.js apps, mainly Next.js. Role-based tests assume Supabase-style JWT authentication; other setups get unauthenticated checks and limited verification.
Pwnly is in a private, invite-only preview while we complete a program review. Request access and we will write back.
Join the private preview and see your first proven finding in minutes.
Request access