Bot protection for developers

Stop bots.
Not humans.

Passive scoring, friction only when risk rises, and signed tokens your backend verifies — not checkbox farms or blind client trust.

  • Free to start — no credit card
  • Works with existing forms
  • Server-side token verify
Security model →

Live preview

Open full demo →

How it works

Keys, embed, verify — in three steps

Click each step to see the live preview update.

Live preview

Sitecheckout.example.com
Public keysp_site_7f3a…c21e
Secretsp_sec_••••••••••••Server only

Why ShieldPass

Three reasons teams switch

Not another generic widget — a verification flow designed around how production apps actually ship.

  • Instead of

    Checkbox captchas

    You get

    Invisible until risk spikes

    Real users rarely see UI. Bots meet friction when scores demand it.

  • Instead of

    Client-side pass/fail

    You get

    Signed server verify

    Your API checks tokens with a secret — attackers cannot forge success in DevTools.

  • Instead of

    One-size friction

    You get

    Adaptive scoring + challenges

    Passive signals first; tap-order, odd-one-out, or direction-match only when needed.

See adaptive friction in the risk lab →

Developers

Copy, paste, verify

Three HTTP endpoints. HTML embed, React SDK, or custom UI — same server verify.

POST /challenge200 OK
HTTP 200 OK

{
  "riskScore": 34,
  "challenge": null,
  "sessionId": "sess_8f2a91"
}
HTML
<script src="https://shieldpass-verify.vercel.app/sdk/shieldpass.js" async defer></script>

<form method="post" action="/api/signup">
  <shield-pass sitekey="sp_site_…"></shield-pass>
  <input type="email" name="email" required />
  <button type="submit">Sign up</button>
</form>

<!-- Token is posted as shieldpass-response — verify on your server -->

Early adopters

What teams report after switching

Feedback from design partners — not marketing fluff.

“We replaced a checkbox captcha on signup. Support tickets about 'I am not a robot' dropped — and we still block scripted signups server-side.”
Platform engineerB2B SaaS · early access
“Checkout was the win. Card testers hit verify before Stripe — we verify the ShieldPass token on our API first.”
Backend leadE-commerce · pilot

Quotes reflect early access feedback. Your risk profile and stack may vary.

Use cases

One widget across your product

Same keys, same verify flow — from marketing sites to SaaS dashboards.

Signup & login

Gate account creation without punishing real users.

Checkout

Stop card-testing bots before they hit your payment provider.

Lead forms

Verify submissions server-side before CRM or email.

APIs

Pair public site keys with secret verify for automated flows.

Get started

Protect your next form today

Free account, two-line embed, server-side verify. See the integration walkthrough or jump straight in.