Borlabs Cookie Review: Local Script Blocking, Version 3 Growing Pains, and German Privacy Standards
German privacy enforcement is strict. Ever since regional court rulings targeted websites loading external Google Fonts without prior consent, European WordPress administrators have faced a consent dilemma. Cloud-hosted platforms like Cookiebot charge recurring fees based on scanned subpage counts or monthly visitor traffic, turning high-traffic compliance into an ongoing tax. Worse, cloud banners route visitor IP addresses to external servers before anyone consents.
Borlabs Cookie, developed in Hamburg by Borlabs GmbH, approaches the problem from the opposite direction. It is a completely self-hosted WordPress plugin. Every consent record, cookie classification, and blocking rule runs on your local server and stays in your WordPress database. No visitor telemetry leaves your infrastructure simply to display a consent prompt.
Blocking at the Source: Content and Script Isolation
Most basic cookie banners display an advisory notice without stopping trackers from firing. Borlabs Cookie takes an enforcement stance by intercepting assets before browsers fetch them.
Its Content Blocker replaces embeds like YouTube, Vimeo, and Google Maps with visual preview cards. Visitors see a placeholder explaining which external service receives data; clicking to accept loads the media immediately or unblocks that provider site-wide.
For scripts, web fonts, and tracking tags, Borlabs maintains a cloud library of over 370 pre-configured packages for tools like Google Tag Manager, Meta Pixel, and Matomo. A built-in scanner detects active plugins and recommends matching packages, sparing you from writing custom regex rules. It also covers Google Consent Mode v2 (Basic and Advanced) and IAB TCF 2.4 certification.
The Version 3 Overhaul and Cache Collisions
Borlabs Cookie 3.0 was an architectural rewrite rather than an incremental update. It introduced a Setup Assistant with Quick (roughly 48 seconds), Custom, and Guided modes, plus a consent banner engineered to meet WCAG 2.1 AA accessibility standards across more than 300 settings.
However, the rewrite created friction. Forum threads and Reddit discussions note that upgrading from version 2.x was not a one-click process; owners had to run manual migration routines or reconfigure service groups on staging.
Script optimization conflicts remain a recurring headache. Because Borlabs intercepts assets early in the page load cycle, performance plugins like WP Rocket, Autoptimize, or LiteSpeed Cache easily break banner behavior. If an optimizer merges or defers JavaScript indiscriminately, the consent dialog freezes or fails to trigger scripts after opt-in. Fixing this requires configuring explicit script exclusions in your caching stack.
Pricing Without Discount Tricks
Borlabs Cookie licenses are sold strictly as annual subscriptions:
- Personal: €49 per year for 1 website
- Business Small: €79 per year for 3 websites
- Business Medium: €109 per year for 5 websites
- Business Large: €179 per year for 10 websites
- Agency Small: €229 per year for 25 websites
- Agency: €499 per year for 99 websites
All prices are billed in euros and exclude VAT, with payments handled by Paddle.
Licensing is straightforward: every tier includes all features, from agency client overview panels and WP-CLI automation to multilingual sync with WPML and Polylang. You only pay for domain capacity. The vendor also refuses promotional discounting, stating on its pricing page that it never runs sales events or Black Friday deals. There is no free repository tier, only a 30-day money-back guarantee.
Real Limits and the Complianz Trade-Off
In community discussions, the main rival cited against Borlabs is Complianz. Complianz offers a free version on WordPress.org and includes wizards that generate legal documents. Borlabs Cookie does not draft policies; you must supply your own legal text. It is an enforcement engine, not a document generator.
The second hard boundary is CMS lock-in: Borlabs is strictly a WordPress plugin. It cannot protect Shopify, Webflow, or headless setups.
Who Should Buy Borlabs Cookie, Who Should Skip It
Pick Borlabs Cookie if you manage WordPress sites for European audiences, need strict opt-in blocking for embeds and scripts, and want consent logs kept on your own infrastructure. For agencies maintaining fleets via WP-CLI, paying €229 for 25 sites or €499 for 99 sites easily beats variable cloud meter bills.
Skip Borlabs Cookie if you need a tool that generates privacy policies, want a free plugin for a simple portfolio, or dislike troubleshooting script exclusions in caching plugins.