Signups worth welcoming
Add a verification step to help deter fake-account creation, referral abuse, and automated registrations.
Signup · Onboarding · ReferralsWelcome people.
Challenge bots.
Protect signup, login, and checkout with a mobile motion challenge. BotGuard adds human verification where automated abuse hurts, while your application stays in control.
Starting on desktop
Scan. Tilt. Continue.
Scan the QR code with your phone, then tilt to guide the ball into the goal.
A compatible phone and motion permission are required.Your server verifies the result.Your application decides what happens next.
Illustrated experience · Try the real challenge in the live demo
Make automation work harder
Protect the moments
that bots exploit.
Put a human verification step
before the actions that matter most.
A step before account access
Challenge automated login and recovery attempts before your application completes a sensitive action.
Login · Password reset · RecoveryMore control at checkout
Put verification in front of purchases, promotions, and other flows where scripted abuse can become costly.
Checkout · Promotions · High-value actionsOne challenge. Your decision.
A human step,
built into your flow.
- 01 / CHALLENGE
Let the person take over.
Your chosen form launches BotGuard. Desktop visitors scan a QR code; mobile visitors open the motion challenge directly.
A phone-based interaction - 02 / VERIFY
Confirm it on your server.
After the challenge is completed, your backend verifies the result before processing the protected action.
Enforcement beyond the browser - 03 / CONTINUE
Keep the decision yours.
Let the workflow continue, offer a retry, or take another step using your application’s own rules and risk signals.
Your workflow. Your controls.
Experience it before you integrate it.
See live demo Our “Threats Near You” demo uses BotGuard before revealing nearby threat activity.
Add another signal
Human verification.
With a wider view of risk.
Use BotGuard alongside ACE v2 IP Reputation to combine a completed challenge with what FraudGuard knows about the source IP.
Your application brings the signals together and decides when to challenge, allow, or take another step.
Explore ACE v2 IP ReputationBotGuard
Was the challenge completed?
A verification result for the protected action.
ACE v2 IP Reputation
What do we know about this IP?
Source risk and observed threat context.
A decision informed by both.
Combined in your application’s own logic.
Do my users need a phone?
Yes. Desktop visitors scan a QR code with a phone; mobile visitors open the challenge directly. The phone needs compatible motion sensors and permission to use them. Provide an alternative verification or recovery path for visitors who cannot complete a motion challenge.
What does integration involve?
Add the hosted BotGuard client to the forms you choose, then verify the returned token on your server before completing the action. You control where verification appears and how your application handles the result. The integration docs cover the implementation.
Will returning visitors face another challenge?
A valid verification session can let visitors skip a new challenge. Your server must still verify the result before processing each protected action. Session behavior and expiry are covered in the API docs.
How does it fit into my bot defenses?
BotGuard adds a human verification step to help deter automated abuse, including automated browser workflows. Pair it with IP intelligence, rate limits, and your application’s fraud controls as part of a layered defense.
How does BotGuard handle visitor data?
BotGuard processes source IP, challenge identifiers, tokens, and session state. The hosted client remembers verified sessions in browser storage. See the integration and privacy notes for details, including the desktop QR service.
Which plans include BotGuard?
BotGuard is available on Professional and above, and active trials can use it. Compare plans or start a free trial to evaluate it in your workflow.
Start with the experience
Try the human side
of bot defense.
See BotGuard in action, then bring verification
to the workflows that need it.