Out of your request path
Volance never sits inline. No proxy, no CDN requirement, no latency added to the request you're protecting — and nothing of ours can take your site down. Your server calls us, and your server decides.
BOT & AGENT DETECTION, EXPLAINED
Every visit
leaves a signal.
Know what’s behind the request. An explainable score for humans, agents, and bots. A decision that stays yours.
One script on your page. One API call from your server. No black box.
SESSION INSPECTORILLUSTRATIVE DATA
BEHAVIORAL TRACEnot a live measurement
SESSION STARTSAMPLE PATTERN
HUMAN-LIKENESS
96/ 100
CLASSIFICATIONhuman↗ allow
SAMPLE OBSERVATION
Varied interaction timing and consistent client signals.
A score is an estimate. Not proof of identity.
Human sample: score 96 of 100, verdict human, action allow.
WHY VOLANCE
Four things the
bigger tools can't say.
Every verdict arrives with its evidence
Not a black box with an opinion. Each response names the checks that ran, what they read, and which ones moved the score — so a decision can be explained to your team, your customer, or an auditor.
Agents are not bots
Most tools see two things: human and threat. Volance separates human, agent and bot, and lets verified agents through by policy — because the web is shared with automation that belongs.
We don't follow the visitor
On-site signals only. No cross-site identifiers, no fingerprinting unless you ask for it, hashed IP addresses, and raw scores purged after 30 days. Boundaries you can put in writing.
Arrivallands on /checkout
Collectedpointer, timing, dwell
Relayedyour backend to Volance
Scored87 / 100, human
Decidedyour server: allow
THE WEB HAS CHANGED
Not all automation is abuse.
Not every visitor is human.
A binary bot check misses the bigger picture. Volance gives you a human-likeness score, a classification, and the signals behind the verdict—so you can make a more informed call.
Integration overviewListen to the session.
Enable on-site behavioral and client signals where you need them. Collection is an explicit integration choice, not a hidden default.
Get the full picture.
Inspect the score, classification, and contributing evidence—not just a yes or no. See why a request deserves a closer look.
Set your own boundaries.
Keep enforcement on your server. Allow, flag, or block according to your application’s policy. Legitimate automation can belong.
A RESPONSE YOU CAN REASON ABOUT
Evidence in.
Clarity out.
A readable response for the application you’re already building. Keep secrets and enforcement on your server.
Illustrative excerpt. Not a live response.
Read the API referencePOST /api/trace/scoreEXCERPT
{
"score": 96,
"verdict": "human",
"action": "allow",
"classification": {
"label": "human"
}
}Changes with the sample inspector. No API call is made.
THE PRIVACY DESIGN
Understand the session.
Don’t follow the person.
Behavioral detection needs clear boundaries. Volance collects on-site only, keeps no cross-site identifiers, hashes IP addresses, and purges raw scores after 30 days.
How Volance handles privacy- Collection
- On-site, operator-enabled
- Cross-site identifiers
- None
- IP storage
- Hashed
- Raw retention
- 30 days
MAKE THE NEXT REQUEST MAKE SENSE.
Less guessing.
More understanding.
One script on your site.
One API call from your server.
Every signal behind the verdict, in your own portal.