Product review
Castle free trial abuse prevention review
Castle joins device, behavior and account events with risk scores and configurable policies. Its multi-accounting coverage can support repeated-trial investigation and should not be reduced to a raw identifier alone. The selected integration, policy and shared API budget determine the workflow the team can operate.
Editorial score
- Evidence layer
- Browser/device signals for account security
- 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 ↗
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 operating event-based risk policies and account investigations within a developer-oriented platform.
Use the alternatives by integration model to compare ready-made account findings, hosted recognition, configurable risk, authentication and email screening.
What the score means
The 8.6 out of 10 score is an editorial assessment under the same 40-criterion, seven-category framework. The rubric covers persistence/linkage, signup decisions, core signals, adjacent abuse, access/pricing, integration and explainability. 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
Compare a permitted repeated-trial case with a legitimate shared-network account. Inspect account links, risk results, policy consequences and the actual shared API budget.
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
- Vendor guide or technical reading · checked October 23, 2026
FAQ
What does Castle contribute to trial-abuse prevention?
Castle joins device, behavior and account events with risk scores and configurable policies. Its multi-accounting coverage can support repeated-trial investigation and should not be reduced to a raw identifier alone. The selected integration, policy and shared API budget determine the workflow the team can operate.
Who should evaluate Castle?
Teams operating event-based risk policies and account investigations within a developer-oriented platform.
How can I evaluate the product?
Compare a permitted repeated-trial case with a legitimate shared-network account. Inspect account links, risk results, policy consequences and the actual shared API budget.