Live Behavioral Intelligence

Bot Detection
Without the Vendor Tax

Own your fraud signals. <secure-telemetry-provider> wraps any form and attaches a cryptographically-signed behavioral envelope to every submission. No third-party SDKs. No CAPTCHA friction. No per-transaction pricing.

27 behavioral signals
0 vendor dependencies
SHA‑256 signed envelopes

Every Submission
Is a Fingerprint

Secure-UI captures timing, interaction patterns, and environmental markers that distinguish humans from automated scripts — without asking users to solve puzzles or accept cookies.

Keystroke Velocity

Timing between keystrokes in milliseconds. Bots type uniformly; humans don't.

142ms avg · normal

Dwell Time

How long focus lingers on a field before interaction begins. Zero dwell is a red flag.

1.8s avg · normal

Paste Detection

Credential stuffing attacks flood paste events. Each is logged and scored against the pattern.

paste detected · flagged

Correction Rate

Humans make typos and fix them. Scripts don't. Backspace-to-character ratio is a strong human signal.

3 corrections · human

Autofill Detection

Browser autofill vs manual entry vs injected values — each fills at distinctly different speeds.

autofill: false

Environment Checks

WebDriver presence, headless markers, injected scripts, and devtools state — verified silently at submission.

webdriver: false

A Risk Score
in Every Envelope

Every submission gets a 0–100 composite risk score assembled from five independent signal categories. Your backend decides what to do — allow, flag for review, or block. No decisions imposed on you.

Bot markers
0 / 20
Velocity anomaly
2 / 20
Paste / inject
0 / 20
Env anomaly
0 / 20
Pattern score
6 / 20
8
/ 100
risk score
VERDICT: ALLOW

Cut the Vendors.
Keep the Signals.

0
CAPTCHAs

Detection is passive. Real users never see a puzzle. Bots never see it coming.

0
Third-party SDKs

No external scripts. No vendor calls. Signals collected and signed entirely in-browser.

$0
Per-transaction fees

MIT license. Scale to millions of submissions without watching the billing dashboard.

Every Envelope
is HMAC-Signed

The telemetry payload is signed with HMAC-SHA256 using a key you provide. Your backend verifies the signature before acting on the data — tampered payloads are rejected automatically.

  1. Signals collected

    Behavioral data gathered silently during form interaction. Nothing visible to the user.

  2. Envelope assembled

    Nonce + timestamp + all signals bundled into a structured JSON payload.

  3. Signature computed

    HMAC-SHA256 signed via the Web Crypto API. Your key never leaves the server.

  4. Backend verifies

    Your server rejects any payload whose signature doesn't match. No spoofing possible.

telemetry-envelope.json verified
{
  "nonce":     "a3f8b2c1d4e5f607",
  "issuedAt":  "2026-03-20T14:32:07Z",
  "riskScore": 8,
  "fields": [
    {
      "fieldName":        "email",
      "dwell":            1842,
      "velocity":         3.2,
      "corrections":      1,
      "pasteDetected":    false,
      "autofillDetected": false
    }
  ],
  "environment": {
    "webdriverDetected": false,
    "headlessDetected":  false,
    "mouseMovement":     true
  },
  "signature": "7c2bef09a1d3c8f2..."
}

Ship It in One Tag

Drop <secure-telemetry-provider> around any <secure-form>. Zero configuration. Zero dependencies. Full cryptographic integrity.

<secure-telemetry-provider signing-key="your-key">
  <secure-form action="/submit" method="POST">
    <!-- your fields -->
  </secure-form>
</secure-telemetry-provider>