- Map where your cookies live first
- Code-owned or hosted: the fork that settles it
- If you want the banner in your repo
- If you'd rather rent the consent record
- Next.js, React and the flash of tracking
- Pricing models, and the subdomain trap
- What's new in the category this year
- Picking for your stage
- Frequently asked questions
For a SaaS company, the right cookie consent tool comes down to one decision: keep the banner in your own codebase with an open-source library, or rent a hosted consent platform that scans, logs and updates for you. Developer-led teams with one marketing site often do well with code; teams selling to buyers who ask for consent records usually want the hosted log.
Map where your cookies live first
Most SaaS teams assume the cookie problem is the marketing site. It usually starts there, but it rarely ends there. The product itself may load session replay, product analytics or a support chat widget, and those need consent too if they set non-essential cookies or read from the visitor's device. So before you compare a single tool, list three surfaces: the marketing site, the logged-in app and any mobile app. Your answer changes which kind of tool you need.
If it's only the marketing site, almost anything on this page will do. If the logged-in app sets analytics cookies, you'll want a tool you can call from your front-end framework, so one consent choice is shared across both. If you ship iOS or Android apps, you're down to vendors with mobile SDKs, and on this list that's a short group.
Code-owned or hosted: the fork that settles it
Code-owned means the banner, the preferences dialog and the rules for which scripts may run all sit in your repository. Changes go through pull requests, the banner ships with your build, and there's no third-party script on the page waiting to load. The cost is that you own the upkeep: someone has to keep the cookie list current when marketing adds a new tag, and a front-end library on its own won't keep a server-side record of who agreed to what. If you need that record, you'll build or host it.
Hosted means a consent platform loads its script on your site, scans for cookies on a schedule, sorts them into categories and logs every choice. You trade a little page weight and a monthly bill for not thinking about it. There's also a middle route: an open-source front-end you can use commercially without paying, with paid hosted plans for the managed parts once you need them.
If you want the banner in your repo
c15t
An open standard for consent banners with framework packages for Next.js, React and Vue, so the banner and script rules ship with your code.
CookieConsent
Written in plain JavaScript with no framework attached, this lightweight library blocks scripts until a visitor agrees and suits a static marketing site.
Klaro
Teams wanting open-source code today and the option of a managed tier later can start here; the front-end carries a BSD-3 licence.
If you'd rather rent the consent record
Termly
A hosted consent platform that pairs a cookie scanner and banner with Google Consent Mode v2 support, aimed at growth teams running ads.
Secure Privacy
Banners, cookie scanning and consent logging from a smaller vendor, with an entry tier pitched at basic Google Consent Mode v2 compliance.
Axeptio
Founders shipping iOS and Android apps alongside the website should look here, since it covers web and mobile consent with native SDKs.
Cookie Compliance
A banner service that documents setup recipes for Next.js and other stacks, plus a manual written for AI coding agents.
CookieYes
Its SDK and an MCP server let you manage consent settings from AI assistants such as Claude or ChatGPT, on top of a scanner and logs.
Osano
Part of a wider privacy platform, its cookie consent honours opt-outs and Global Privacy Control signals and keeps a record of each choice.
Cookiebot
The Usercentrics consent platform, with plans that scale to the size of the site, for teams expecting to grow into a bigger tier.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Next.js, React and the flash of tracking
On a server-rendered framework, the consent choice has to be known before the first script runs, not after the page hydrates. Get this wrong and you'll render a tracking pixel, fire it, and only then show the banner that was meant to stop it. Whichever tool you choose, check three things on a fresh visit in a private window:
- Analytics and ad scripts are held back until consent, not just hidden behind the banner.
- The stored choice can be read on the server, so a returning visitor who said no never gets the script in the first place.
- The banner doesn't shove page content down as it loads, which shows up as layout shift in your Core Web Vitals.
A framework package handles the first two inside your own code, which is the strongest argument for the code-owned route on a modern stack. A hosted script can do them too, but you'll need to set its blocking mode and load order with care and recheck them after every marketing change.
Pricing models, and the subdomain trap
Four of the six tools here that publish a price charge per domain or per website, per month. That sounds tidy until you count your hosts: marketing site, docs, status page, the app on its own subdomain, a regional site. Before you sign, ask the vendor in writing how subdomains and staging hosts are counted, and keep the reply. The entry tiers that are published are small monthly sums; the jump to the enterprise tiers is steep, so check which features you'd need before you outgrow the first plan.
The open-source libraries cost nothing to licence. What you pay instead is developer time to wire them up, keep the cookie list current and build somewhere to store consent if a buyer asks for proof. For a team of two engineers that trade is often worth it; for a team where marketing owns the site and engineering is busy shipping product, it usually isn't.
Do you make cookie consent tools for software companies? Tool makers can ask to be considered for a featured place on this list.
What's new in the category this year
AI has reached consent tooling from an odd angle. At least two vendors on this list now pitch ways to set up consent through AI assistants or coding agents, one with an MCP server and one with a manual written for agents. That's handy if your team already builds that way; it tells you nothing about whether the banner blocks what it should, so test that separately.
The steadier change is Global Privacy Control. US privacy laws in several states treat the browser signal as an opt-out, and some platforms now say outright that they honour it. If you sell to American companies, ask any tool on your shortlist how it handles the signal before you ask about colours.
Picking for your stage
- Early stage, one marketing site, a developer on the team: an open-source library in your codebase, with a simple consent log you control.
- Selling to companies whose procurement asks for consent records: a hosted platform with logs you can export on request.
- Mobile app plus web: a vendor with native iOS and Android SDKs, chosen for that before anything else.
- Marketing site on WordPress, run by the marketing team: a plugin-based tool they can manage without a deploy.
For that last case, the guide to the cookie consent WordPress plugins small teams use goes further. And if the company also runs things outside the product, a shop or a community site, the wider list of consent management platforms for small businesses covers tools built for owners who'll never open a terminal.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Do I need a cookie banner if I only use cookieless analytics?
If your analytics sets no cookies and doesn't read anything from the visitor's device, and nothing else on the page does either, EU and UK rules generally don't ask for consent for it. Most SaaS sites also run chat widgets, embedded videos or ad tags, so check the whole page before you drop the banner.
Does consent given on the marketing site carry into the app?
Only if you set it up that way. A cookie set on one subdomain isn't readable on another unless it's scoped to the parent domain, so either share the consent cookie across your domain or store the choice against the user's account and read it from your back end.
Do login and session cookies need consent?
No. Cookies the service can't work without, such as a session cookie for a logged-in user or a load-balancer cookie, don't need consent. List them in your cookie policy and make sure the banner doesn't offer a switch that would break sign-in.


