ConsentProof vs Open-source cookie consent
ConsentProof is a cookie consent checker that scans any website with a real browser and records which cookies and third-party trackers fire before the visitor consents.
ConsentProof
ConsentProof is a cookie consent checker that scans any website with a real browser and records which cookies and third-party trackers fire before the visitor consents.
We scan every client site on a schedule, catch trackers that fire before consent, and hand you timestamped evidence you can send to the client.
ConsentProof does not serve a cookie banner, does not write your cookie policy, and cannot make a site compliant. It tests one thing — whether non-essential cookies and third-party trackers fire before a visitor consents — and records what it saw, with a timestamp. Keep whichever consent platform you already use; an independent test is worth more than one run by the vendor being tested.
Open-source cookie consent
Open-source consent banners are self-hosted libraries you configure in code: no licence fee, no vendor account, and no third-party script on your visitors' browsers.
No per-pageview or per-subpage billing, which is the single most common complaint about commercial consent platforms and the reason agencies go looking in the first place.
No third-party script loaded on every page view, which is better for both performance and for the argument that your consent tool is not itself a tracking vector.
Full control: the banner is in your repository, reviewed like any other code, and cannot change its behaviour or its pricing without you merging something.
Nobody maintains your cookie inventory for you. Commercial platforms scan and regenerate the declaration; with a self-hosted banner, the category mapping is a manual list that goes stale the moment marketing adds a tag.
Maintenance is real and unevenly distributed across projects. Before adopting one, check its commit history and its issue tracker yourself rather than trusting a round-up post — including this one.
Blocking is only as good as your integration. A self-hosted banner will happily render above scripts it was never told about.
Free to use, in the sense that there is no invoice. The cost is maintenance: someone on your side owns the configuration, the category mapping and the upgrades, and that someone is usually the developer who is busiest.
Frequently asked
- Is open-source cookie consent management good enough for GDPR?
- The banner itself can be, if it is configured to block non-essential scripts before a choice is made. What no library gives you is proof that it is still doing so after six months of site changes, which is a monitoring problem rather than a banner problem.
- What do I lose by not paying for a consent platform?
- Mostly the managed cookie inventory and the declaration widget, plus vendor support. You keep control and you lose per-pageview billing.
- How do I verify a self-hosted consent banner actually blocks scripts?
- Load the site in a clean session, record everything that fires before you touch the banner, then accept and record again. If the two captures are identical, nothing was being blocked. That is exactly what a scan here returns.
Related
Try ConsentProof
Free public scan, no account needed.