SableTicket runs a sports betting serving customers across Southeast Asia. Before Deflecto, attacks meant diverting traffic to a scrubbing provider and waiting.
The challenge
Bonus abuse by automated account creation.
The result
- 293 attacks mitigated in the first year
- Median time to mitigation 193 ms
- 48% lower origin infrastructure cost
- Zero customer-visible outages
We replaced a CAPTCHA that cost us conversions with something our customers never see.
CISO, SableTicket
Is the risk score exposed in the logs so we can build our own dashboards on it?
The billing model is what got our finance team on board, honestly.
How do you avoid challenging uptime monitors and partners?
Any plans to support per-tenant limits keyed on a JWT claim?