Choose by the result you need.
Compare the result your backend receives, the integration work, and the decisions each product supports.
What does your application need?
A challenge widget with server-side token validation. Compare its response fields with the checks your form requires.
Compare TurnstileExample outputs
0.KBtT_rf3q1om7…
The token is valid for the expected context.
Your application evaluates the score against its threshold.
"8c41d2be0a97f3e1"
Browser properties produce a visitor identifier.
example blocked response
The configured policy determines the traffic response.
finding: geo.rtt-below-vacuum
The verdict includes the specific findings behind it.
Side by side.
The individual comparisons link to vendor documentation. FingerprintJS refers to the open-source library unless the commercial service is named.
What each result establishes
You can combine traffic protection with Heretic session checks. Define which results your backend requires for each protected action.
Inspect a Heretic result.
The live demo shows a verdict, its findings, and the fields available to your backend.