I see either the old or new cloaker services offers the same pricing. not sure if copycat or the service is actually worth it. some use cloudflare config and has some success and as we know it is depend on your pool of blacklist ips. the more you have the more your cloaker service is strong enough. but recently even the new service ask for high price almost the same as the legend service on the field. that is why im thinking if it actually worth the pricing.
Hi, look, I also don’t see any point in paying “by default” just because of the price tag. Right now old and new cloakers often cost almost the same, but that’s not a quality indicator at all. The infrastructure is expensive for everyone anyway, but the value isn’t the dashboard - it’s how stable and controllable the results are at scale.
In arbitrage, it’s not the “panel” or some Cloudflare config that matters. Two things decide everything: the IP/ASN/reputation database and how often it’s updated, and stability on volume. If the database is weak or rarely updated, the service is basically dead, even if it costs 900 EUR. And what works on small traffic often collapses on real volume, especially when more dirty or burned IPs hit your flow.
Yes, you can tune Cloudflare and sometimes it works, but that’s not “cloaking as a service”. It’s more like a workaround that survives until you get more dirty traffic, checks, or reports. So my approach is simple: I wouldn’t touch anything without a test, a trial, or at least a month-to-month option. If a service can’t clearly show how they update their databases, what filters they offer, what stats they provide, and how fast support reacts, then it’s just an expensive landing page. If pricing is similar, I’d either go with a proven one that truly holds volume, or I wouldn’t pay at all and keep using CF until a serious flag hits.
To avoid guessing, I’d do it like this: pick the top 5 cloakers and run a proper test for up to 2 weeks. Same conditions for everyone: one GEO, same landers and logic, no “special” tweaks per provider. Split the 2 weeks so each gets enough load: roughly 2–3 days per service plus 1–2 buffer days for a retest if something starts collapsing. Then judge only by real metrics: clean-traffic ratio, frequency of checks/flags, stability across ISPs/ASNs, and how long the setup survives without constant manual fixes.
Bottom line paying only makes sense if the service delivers a clear lift in approval rate and setup lifespan on volume. If there’s no measurable improvement, it’s just a straight hit to ROI.
