HidePages vs Cloakerly (2026): Pricing, Setup and Pages Compared

HidePages vs Cloakerly at a glance#

Prices and features checked November 2026 on the official sites ([cloakerly.com](https://cloakerly.com/), [Cloakerly docs](https://cloakerly.com/docs/index.html), [hidepages.com](https://www.hidepages.com)). They may change.

The core difference: a filter you install vs a layer that serves the page#

Both products make the same decision on each visit: real prospect, or bot, spy tool, proxy, VPN or datacenter connection? The difference is what happens around that decision.

Cloakerly: a snippet on your page

Cloakerly's docs list a lot of ways in, which is a real strength if you have developers:

• PHP (the default): paste the snippet "at the very top of the landing file". It needs PHP with the cURL extension. When Cloakerly returns an affiliate URL, the visitor is redirected; filtered traffic stays on the page.
• PHP cURL (No Redirect): the browser URL doesn't change, and allowed visitors see the offer in a full-page iframe. "The destination must allow framing."
• WordPress plugin: WordPress 5.0+ and PHP 7.4+, with a server-side check and a redirect.
• JavaScript: client-side, with the docs warning about a possible brief flash of the safe page, in-app browsers that may delay the request and less reliable IP detection.
• React, Angular and Python helpers, a reverse proxy PHP file that keeps your domain and streams the origin page, and link cloaking: a Cloakerly-hosted URL with nothing to install, which redirects.

In every option except the hosted link, the safe page and the offer pages are yours to build and host. Cloakerly's site doesn't mention a page builder or page hosting.

HidePages: the link is the filter

HidePages is a page builder with a native traffic filter (Zero-Redirect) for 15+ traffic sources. The campaign link points to HidePages. The filter decides, and the page it chose is served in the same response, from pages built and hosted in the same account. No PHP version to check, no cURL extension, no iframe whose destination has to allow framing.

Filtering#

Cloakerly describes "AI traffic analysis, IP reputation data, device fingerprinting, and network-level detection" and lists datacenter and hosting traffic, public and private proxies, VPNs, Tor exit nodes, bots and "suspicious or non-human behavior patterns". It supports IPv4 and IPv6, targets by country, region or city, and lets you set device, OS, browser, frequency, UTM and click ID rules per campaign. The FAQ says it detects "known monitoring tools" and competitor scanners. Its site claims "1M+ IP's Blocked/Day"; that's a vendor figure we haven't tested.

HidePages ships filtering as features you switch on per page: bot detection, spy-tool blocking, Block Suspicious Connections, and rules for geo, language, device and campaign parameters. Each page can have its own filter.

On filtering depth the two are close on paper; Cloakerly gives power users more knobs (city-level geo, frequency caps, separate Mac and tablet URLs). Where HidePages pulls ahead is visibility: every request is in the Access Logs with its status and the reason it got that page. When conversions drop on one source, you check the log instead of guessing.

Pages and hosting#

This is where the products differ most. Cloakerly assumes your pages exist: you enter a Safe URL and "at least one affiliate page" in the campaign form, then integrate. If you need a new white page, presell or lander, you build and host it somewhere else.

HidePages builds them:

• Blank editor, import by code, clone any site by URL or templates.
• Mirror mode for external pages without a redirect, or Redirect mode when you want one.
• Subpages (presell, back redirect), A/B tests and an upsell funnel in the same campaign.

If you test many angles a week, that's the difference between duplicating a page in the panel and uploading new files to a server.

Pricing: per campaign vs per request#

Cloakerly (cloakerly.com)

The pricing section has two tabs. Read on the page in November 2026:

The page labels the click packs "/Yr", which reads as a validity period, but it isn't explained. Confirm with Cloakerly before buying. Its refund policy says it "does not issue refunds at the completion of any payment", with exceptions for upgrades and non-delivery. No trial is mentioned.

HidePages (monthly, no contract)

Side by side

Assume one request per visit and Cloakerly's subscription plans:

The pattern is clear: Cloakerly's flat price wins when volume is concentrated in few campaigns; HidePages wins when traffic is spread across many. Using list prices and HidePages overage, the break-even points are roughly:

Above those volumes, Cloakerly is cheaper on sticker price. Keep in mind that HidePages' number includes the page hosting you pay for separately with Cloakerly. The full per-1,000 math is in HidePages pricing explained.

Who should pick Cloakerly#

Cloakerly is the better choice when:

• You run one or a few big campaigns. $149 a month for unlimited clicks on one campaign is hard to beat.
• You push more than ~1.4 million requests a month across many campaigns and want a flat bill.
• You have developers and like options. PHP, WordPress, JavaScript, React, Angular, Python and reverse-proxy integrations cover almost any stack.
• You want fine-grained routing: city-level geo, frequency caps, separate Mobile, Tablet and Mac URLs, and traffic splits across affiliate pages.
• Your pages are already built and hosted and you only need a filter in front of them.

Who should pick HidePages: the Cloakerly alternative with pages included#

HidePages is the better choice when:

• You run many campaigns at small and mid volume. Below the break-even points above (for example 600,000 requests across 10 campaigns), HidePages costs less than the matching Cloakerly plan.
• You don't want hosting or integration code. No PHP, no cURL, no plugin, no iframe.
• Real visitors should see the page with no redirect and no frame. Zero-Redirect serves the page directly.
• You build and test pages often. Clone by URL, import code, use templates, add presells, back redirects, A/B tests and upsells.
• You want to know why. Every request in the Access Logs with status and reason.
• You run native and video sources such as NewsBreak, MediaGo, Taboola, Outbrain, YouTube, TrafficJunky and Bigo.
• You want help moving. Free assisted migration and WhatsApp support; VIP with the founding team on Scale and Enterprise.

How to switch from Cloakerly to HidePages#

1. 1Bring your pages. Your safe page and affiliate pages are on your hosting: clone them by URL, import the code or rebuild them in the editor.
2. 2Point your domains to HidePages. Once the domain answers from HidePages, the Cloakerly snippet is out of the request path.
3. 3Recreate each campaign as filter rules: geo, language, device and campaign parameters, plus bot, spy-tool and suspicious-connection filtering. Use A/B tests where you rotated affiliate pages.
4. 4Swap the ad link one campaign at a time and compare the Access Logs with Cloakerly's stats.
5. 5Cancel when you're convinced. Our team does this with you for free; the full guide is in how to migrate to HidePages.

Bottom line#

Cloakerly (cloakerly.com) is a flexible filter with many integration options and a flat per-campaign price that pays off when your traffic is concentrated in a few big campaigns. You still build and host every page, and real visitors get a redirect or an iframe. HidePages hosts the pages, filters at the link with no redirect, logs the reason for every request and costs less when traffic is spread across many campaigns at small and mid volume. For one huge campaign, Cloakerly; for a portfolio of campaigns and pages, HidePages.

Start with what a cloaker is, see the best cloakers of 2026, check the cloaker pricing comparison, or compare HidePages vs TrafficShield and HidePages vs Just Cloak It, another snippet-on-your-site filter.

FAQ#