Heretic and DataDome

DataDome detects and responds to bot traffic through your delivery infrastructure. Heretic checks browser sessions and returns findings for your application to act on.

Traffic protection and session checks

DataDome integrates with servers and CDNs to evaluate traffic and apply a response. Its Protection API supports that request-time integration. Deployment requirements depend on the connector you choose.

Heretic runs through a browser script and a separate sensor connection. It returns an assessment to your backend. Your application enforces the result before accepting a signup, payout, or other protected action.

What you can inspect

DataDome can enrich logs with bot names, matched models, response types, confidence scores, and threat markers. Availability depends on plan and configuration. Its log-enrichment reference lists the fields.

Heretic returns a verdict and individual findings with documented IDs. For example, stack.os-contradiction identifies a conflict between the observed TCP signature and claimed operating system. Each finding includes a tier and human-readable details, so your policy can address that condition directly.

How Heretic reaches a verdict

Conclusive rules test observed contradictions, protocol requirements, and fixed physical constraints. One absolute or composite contradiction is enough. Conditional findings, including CPU and GPU performance comparisons, remain available without setting the verdict.

An opened session with incomplete required measurements returns refused. If the collector never loads, no result exists. A backend that requires measurement must hold or reject the action until its requirements are met.

Deployment and pricing

Heretic does not proxy application traffic. Add its collector or widget to a page, verify the site's domain, and read results from your server. Accepting a protected action still depends on receiving the required result.

Heretic's paid plans are monthly, with included probes and challenges plus metered overage. Build in the Developer Sandbox to evaluate the integration. The pricing page lists allowances and rates.

Using both

A server or CDN integration can enforce traffic policy before requests reach application code. Heretic can add browser findings at specific actions. If you combine them, decide which result each action requires and verify that result on the backend.

Use findings in your own code.

Add the collector and inspect its verdict before connecting it to your application policy.