Product review
Castle abuse detection review
Castle connects device and behavior signals to signup, login and account-security decisions. Its pricing separates API usage units, so a Risk API call and an IP lookup should be costed separately.
Editorial score
Account security and device behavior
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
- Detection scope
- Castle connects device and behavior signals to signup, login and account-security decisions. Its pricing separates API usage units, so a Risk API call and an IP lookup should be costed separately. Vendor page ↗
- Output
- Risk scores, signals and configurable policies Vendor page ↗
- Access and commercial model
- 5 US dollars API usage/month: up to 1,000 Risk API calls. Pro: 200 US dollars/month, including 40,000 Risk API calls. Confirm the entitled features and billing unit. Vendor page ↗
- Integration and evaluation
- Use known legitimate activity and authorized controlled abuse cases. Link the result to the protected action, inspect reasons and missing-result behavior, then verify recovery and review paths. Use the free allowance for a controlled Risk API evaluation; confirm retention and throughput before a larger pilot. Vendor page ↗
Strengths
- Bot, abuse and account-takeover signals address account actions.
- API documentation supports a direct application integration.
- A recurring free usage allowance supports small experiments.
Limitations
- Policy and action design still needs an application workflow.
- The free plan has short retention; compare the included usage and rate limits.
Who it fits
Developer-led teams building account security, abuse policies and step-up flows.
Use the alternatives by evidence need to compare overlapping device, identity, behavior and automation capabilities.
What the score means
The 8.8 out of 10 score is an editorial assessment under the same 41-criterion, seven-category framework. It weighs abuse coverage, identity linking, verdict quality, workflow, access, integration and real-time decisions.
Editor’s Choice is a separate recommendation. Read all criteria and relative weights and evaluate the entitled product on the product flow you protect.
How to evaluate it
Use known legitimate activity and authorized controlled abuse cases. Link the result to the protected action, inspect reasons and missing-result behavior, then verify recovery and review paths. Use the free allowance for a controlled Risk API evaluation; confirm retention and throughput before a larger pilot.
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 22, 2026
- Pricing and access · checked October 22, 2026
- Integration and result documentation · checked October 22, 2026
- Introducing multi-accounting detection · checked October 22, 2026
FAQ
What does Castle cover?
Castle connects device and behavior signals to signup, login and account-security decisions. Its pricing separates API usage units, so a Risk API call and an IP lookup should be costed separately.
Who should evaluate Castle?
Developer-led teams building account security, abuse policies and step-up flows.
How can I try Castle?
Use the free allowance for a controlled Risk API evaluation; confirm retention and throughput before a larger pilot. 5 US dollars API usage/month: up to 1,000 Risk API calls. Pro: 200 US dollars/month, including 40,000 Risk API calls.
Explore checkers, demos and evaluation routes →