Product review
Castle anti-detect browser detection review
Castle brings device and behavior evidence into account-event risk assessment. Its documented multi-accounting detection and policy tools can support investigation beyond one browser flag. Evaluate the event model and retained evidence for anti-detect scenarios rather than assuming every detection must be built from raw identifiers.
Editorial score
- Evidence layer
- Event-based device, behavior and account risk
- Free access
- 5 US dollars API usage/month: up to 1,000 Risk API calls
- Paid entry
- Pro: 200 US dollars/month, including 40,000 Risk API calls
Key facts
- Identity and matching scope
- Event-based device/behavior risk and policy outputs for account actions. Vendor page ↗
- Result to inspect
- Device evidence, risk scores and policy outcomes Vendor page ↗
- Access and pricing
- 5 US dollars API usage/month: up to 1,000 Risk API calls. Pro: 200 US dollars/month, including 40,000 Risk API calls. Compare the actual plan, product and usage unit. Vendor page ↗
- Multi-accounting scope
- The documented detection covers linked-account activity. Evaluate the required event association and policy rather than assuming the product has no multi-accounting support. Vendor page ↗
- Browser scope
- Use device and behavior evidence with account events and risk policies. Confirm the named detection fields and supported environment for the selected SDK. Vendor page ↗
Strengths
- Risk, automation and account signals are relevant to protected account events.
- Free usage supports a controlled API evaluation.
- Public documentation explains signals, metrics and policy integration.
Limitations
- IP-lookup allowances should not be counted as Risk API calls.
- History, operational tooling and throughput depend on the plan.
Who it fits
Teams that want event-based risk and policy controls alongside device and account history.
Use the alternatives by integration model to compare production risk integrations, inline bot protection and manual browser diagnostics.
What the score means
The 8.6 out of 10 score is an editorial assessment under the same 41-criterion, seven-category framework. The rubric covers spoof/tamper detection, cross-layer signal depth, evasion resilience, identity, integration, false positives and access. The published scale runs from 0 to 10.
The award and score are distinct. Read all criteria and relative weights and verify the required signal and integration for your traffic.
How to evaluate it
Associate the browser event with the correct account and action. Evaluate the documented device and automation evidence, policy output and multi-accounting workflow with legitimate controls.
Free API allowance
Use the free allowance for a controlled Risk API evaluation; confirm retention and throughput before a larger pilot.
Open evaluation routeSources and further reading
- Product and detection approach · checked October 23, 2026
- Pricing and access · checked October 23, 2026
- Integration and result documentation · checked October 23, 2026
- Official guide and technical context · checked October 23, 2026
FAQ
What does Castle return?
Risk scores, event evidence and policy outcomes. Event-based device/behavior risk and policy outputs for account actions.
How can a team evaluate Castle?
Associate the browser event with the correct account and action. Evaluate the documented device and automation evidence, policy output and multi-accounting workflow with legitimate controls.
What should be checked before choosing Castle?
IP-lookup allowances should not be counted as Risk API calls. History, operational tooling and throughput depend on the plan.