Finance & compliance
Geo-Flat Cookie Consent
Cookie consent for sites with visitors in many countries. One flat yearly price per site, unlimited pageviews, logs you host.
Founder thesis
The bet: sites with mostly non-EU traffic get no consent gate at all from GDPR-only banners, and the tools that exist either meter pageviews or cap domains. CookieYes has 1M+ WordPress installs and claims 1.5M businesses, Osano sells a $500,000 No Fines Guarantee, so the incumbents are not weak, but nobody sells one flat yearly price with multi-law geo-gating. Complianz already covers the flat-price angle at $59 a year, so the opening is narrower than it looks.
What others got wrong
CookieYes shows its GDPR banner only to visitors it reads as EU/EEA, so a mostly Thai site running GDPR-only settings fires tracking scripts for Thai visitors with no banner at all.
CookieYes attribute-blocking re-injects the script with only src and type, dropping data-website-id, so data-attribute-configured trackers send zero events.
CookieYes meters pageviews, charging $0.30 per 1,000 overage pageviews beyond the plan limit on Basic and Pro.
What should work
Price flat per site per year with unlimited pageviews and unlimited consent records, the way Complianz does at $59 a year for 1 site up to $399 a year for 25.
Ship a free WordPress.org plugin as top-of-funnel. CookieYes turned 1M+ installs at 4.8 stars into web-app subscriptions this way.
Gate scripts per region and check it against real visitor locales, so a Thai visitor gets a PDPA banner and trackers stay blocked, fixing the gap CookieYes leaves open.
What kills it
- Complianz already sells flat per-site pricing at $59 to $399 a year with unlimited pageviews, so price alone wins nothing.
- Consent logs export to CSV and banner code is portable, so customers can leave whenever.
- CookieYes and Osano hold the certifications and directory installs enterprise buyers filter on.
- No proof exists that anyone switches CMPs for a flat fee or for multi-law gating.
What users want
4A banner that gates non-EU visitors, not just the EU.
A Thai property site ran CookieYes with GDPR-only settings and showed no banner while tracking scripts fired for a Thai visitor, a GitHub issue reports.
Tracker gating that does not quietly break analytics.
A site gated Umami with CookieYes attribute-blocking and got zero events, because the script came back with data-website-id dropped, a GitHub pull request documents.
A one-click way to refuse everything.
One HN commenter wrote that refusing all means walking each vendor's own category screens while accepting is one click.
Consent still collected when ad blockers run.
An HN commenter whose filters block cdn-cookieyes.com never saw a prompt, leaving the site owner with no audit trail.
- Sources
- 11
- Checked
- 11
- Competitors
- 3
- Gaps
- 4
- Page checked
- 11 · 100%
- Snippet only
- 0 · 0%
- Documented
- 6 · 67%
- Interpreted
- 3 · 33%
- complaint4
- pricing3
- market3
- playbook1
Competitors
3Parsed from public pricing blurbs (entry paid tier when available). Max in set: $10/mo.
| Competitor | From | Free tier | Source |
|---|---|---|---|
| CookieYes | $10/mo | Yes | cookieyes.com✓ |
| Osano | Free | Yes | osano.com✓ |
| Complianz | See notes | — | complianz.io✓ |
What customers complain about
4| Gap | Src |
|---|---|
GDPR-only settings leave non-EU visitors with no gate. A Thai property site (kkdproperty.co.th) with a mostly Thai audience runs CookieYes with applicable_laws: [gdpr], and a Thai IP in incognito fires tracking scripts with no banner, because the GDPR banner only shows to EU/EEA visitors. Thailand's PDPA is a separate law, so GDPR-only settings do not give PDPA-compliant consent. | |
Attribute-blocking breaks trackers. A site gated analytics with type=text/plain plus data-cookieyes=cookieyes-analytics, sent zero events across two browsers, and on accept CookieYes re-injected the script with only src and type, dropping data-website-id, so any tracker configured this way fails the same way, silently. | |
Banners force visitors through many screens to refuse. Saying no to all means walking each vendor's own category settings screens, while accepting is one click. | |
Privacy tools block the CMP CDN, so consent is never collected. A visitor running filters that block cdn-cookieyes.com never saw a prompt, so the site owner has no audit trail for that traffic. |
Documented Interpreted
How competitors find customers
2| Tactic | Src |
|---|---|
| CookieYes runs a free WordPress.org plugin as top-of-funnel, 1M+ active installs at 4.8 stars from 3,200+ reviews, with the plugin page carrying the upsell to metered web-app plans. | wordpress.org✓ |
| Osano runs a free URL compliance scan as a lead magnet, capturing high-intent URLs. No conversion number is published. | osano.com✓ |
Your angle & pricing wedge
| Piece | Claim | Src |
|---|---|---|
| Angle | One account ships every law's banner (GDPR plus Thailand PDPA, LGPD, and US state laws), gates scripts per region against real visitor locales, charges a flat yearly price per site, and stores consent logs in the customer's own database and region. | |
| Wedge | Charge the site, not the pageview or the domain: one flat yearly price per site with unlimited pageviews and self-hosted logs, against CookieYes at $10-55/mo per domain plus $0.30 per 1,000 overage pageviews, or Osano Plus at $199/mo capped at 3 domains and 30,000 visitors. The meter being removed shows up on the pricing pages, but that the flat price holds and that buyers switch for it is unproven. |
How others got traction
3| Move | Why | Src |
|---|---|---|
| CookieYes ships a free WordPress.org plugin with 1M+ active installs that upsells to pageview-metered web-app plans. | The plugin page states premium features come with a premium plan on the CookieYes web app account. The free listing builds a SaaS funnel at near-zero acquisition cost, a number the company does not give. | wordpress.org✓ |
| Complianz prices per site per year with unlimited pageviews and unlimited consent records on every tier. | Its pricing FAQ says it does not limit consent records or monthly pageviews, a direct contrast with metered rivals and CookieYes's $0.30 per 1,000 overage pageviews, though no switching data is published. | complianz.io✓ |
| Osano offers a No Fines Guarantee covering regulatory fines up to $500,000. | The plans page states the terms. It takes fine fear out of the enterprise purchase, but nothing ties it to a measured lift in conversions. | osano.com✓ |
Market heat
CookieYes says 1.5+ million businesses use it, a company figure on its homepage.
The CookieYes WordPress plugin reports 1M+ active installs and a 4.8-star rating from 3,200+ reviews.
Osano states 1000+ companies use it, with 4.6/5 from 150+ reviews shown on its plans page.
Revenue signals
3| Signal | Src |
|---|---|
CookieYes: 'Trusted by 1.5+ million businesses worldwide' on its homepage, self-reported and not independently checked. | cookieyes.com✓ |
Osano: 'Join 1000+ Companies using Osano' on its plans page, self-reported and not independently checked. | osano.com✓ |
Self-serve prices run $0 to $199 a month, from CookieYes Basic at $10/mo to Osano Plus at $199/mo. Whether a flat $49-79 a year per-site entrant wins share is unproven. | cookieyes.com✓ |
Should you build this?
The category earns real money on company-reported numbers, and the pain is in users' own words: no PDPA gate for Thai visitors, tracker gating that sends zero events, refusing that takes many screens, and banners that never load under filters. But Complianz already owns the flat price at $59-399 a year with unlimited pageviews, and certifications plus 1M+ directory installs favor the incumbents, so only multi-law geo-gating plus verified script-blocking might hold. Test before building: recruit 15 WordPress owners with mostly non-EU traffic who already pay for a CMP, reproduce the PDPA gap and the attribute-drop failure on their staging sites, then offer $79 a year flat for multi-law geo banners with self-hosted logs. Kill it if fewer than 5 prepay, or if neither failure reproduces on at least 8 of the 15 sites.
More ▾
All sources
11| Source | Kind | Status | Accessed |
|---|---|---|---|
| pricing | page checked | 2026-09-18 | |
| pricing | page checked | 2026-09-18 | |
| pricing | page checked | 2026-09-18 | |
| playbook | page checked | 2026-09-18 | |
| market | page checked | 2026-09-18 | |
| complaint | page checked | 2026-09-18 | |
| complaint | page checked | 2026-09-18 | |
| complaint | page checked | 2026-09-18 | |
| complaint | page checked | 2026-09-18 | |
| market | page checked | 2026-09-18 | |
| market | page checked | 2026-09-18 |