Why our paid plans count only successful takedowns
Success-based counting isn't a discount gimmick. It's an alignment mechanism. Here's why our paid plans tie quota to the only metric that matters.
Most security spending is measured in activity: reports filed, alerts triaged, hours logged. The problem with activity metrics is that they reward motion, not outcomes. A vendor can file a hundred reports and remove nothing, and still look busy.
The only metric that matters
For a takedown, there is exactly one outcome worth paying for: the malicious content is gone and stays gone. Everything else (the report, the escalation, the follow-up) is just the work required to get there. So on paid plans, what uses your quota is the outcome, not the work.
What success-based billing forces
Tying quota to removals changes the incentives on our side:
- We have to target the layer that actually works (host, registrar, CDN), not just the easiest one to file against.
- We have to escalate stalled cases instead of letting them sit closed-but-not-resolved.
- We have to verify removal, because a case that reappears isn't a success.
If we don't get the content down, it doesn't count against your paid quota. That sentence is only safe to write if every part of the process is built to actually finish the job.
What it means for you
No minimums, no multi-year lock-in, and a filing that went nowhere uses none of your paid quota. You send the target and we do the work. On a paid plan the monthly fee is the same whatever happens, and a takedown only counts against your quota once the content is confirmed offline. The free plan works differently: its single request is used whatever the outcome. It's a simple promise, but it only works because the incentive points the same direction as your goal: removal, verified.