chris082Q: Stealth is confusing. Why do I care what level?
I think your pricing model on different levels of stealth is confusing. I don't have a lot of experience here so how would I know what's relevant to me? Seems like you're tee'ing up people for a bad UX when they don't have enough "stealth" to get what they want and it's not obvious how it related to one site vs the next.
Why not just give the best stealth experience you can do and let your product standout? You already gate on usage. Or at the very least, gate on something that is easy to understand like a binary feature such as "captcha or no captcha".
Can you explain why I would care between basic/advanced/+ for stealth?
Sam_Notte
May 12, 2026A: Hi,
Honestly, fair critique. You're not wrong that "Basic / Advanced / +" is doing a lot of work for a buyer who hasn't yet wrestled with a Cloudflare wall/challenge.
The Practical Rule of Thumb
- The Entry Tier: If the sites you care about don't actively block automation (most internal tools, most CMSes, or "normal" SaaS), this is genuinely fine.
- Higher Tiers: If you start hitting captcha pages, Cloudflare interstitials, or Datadome blocks, that's your signal to step up. The higher tiers focus on:
- Residential proxying
- Fingerprint patching
- Advanced captcha handling
(This is the specific stuff anti-bot vendors look for.)
Why not "Max Stealth" by default?
The reason we don't ship max stealth for everyone is simply cost. Residential proxies and captcha solving are real per-action expenses. Bundling them into every session would push the floor price up for the 70% of users who don't actually need them. Tiering allows the basic plan to stay affordable.
The labels could definitely be clearer, and the documentation should explicitly tell you: "Use X if your target site has Y." This is really good input, thanks for the feedback