A CookieYes alternative with consent in your server render
CookieYes runs consent as a hosted banner, plus a React and Next.js SDK. Inth Consent runs the open source c15t banner as code in your app and hosts the records.
16×sooner on screen than CookieYes. Median, Next.js on desktop.
Why switch from CookieYes
A banner that shows late
On CookieYes
In CookieBench, the CookieYes banner reached the screen in a median 393 ms on Next.js desktop.
With Inth Consent
The c15t banner showed in a median 25 ms in the same run, and Next.js pages can resolve consent on the server.
A server that does not know the choice
On CookieYes
With the CookieYes Next.js SDK, the server does not know the visitor’s decision by default unless you pass it in.
With Inth Consent
In Next.js and TanStack Start, c15t resolves consent on the server for each request.
A switch nobody has time to plan
On CookieYes
Moving off CookieYes means finding every tag, category and script it controls.
With Inth Consent
Paste the prompt under How to move from CookieYes into your coding agent. It maps your setup to c15t and plans a staging run.
How Inth Consent and CookieYes compare
For privacy and legal teams: Inth records every choice with its region and policy version, applies each region’s own rules and honors Global Privacy Control.
Where CookieYes is ahead: its script adds less to the first load (31 KB against 104 KB), though the c15t banner is still on screen sooner. CookieYes scans your site for cookies, where Website audit shows what your pages load. CookieYes generates policies, where Inth Consent pairs with your current policy tool.
| Your requirements | Inth Consent | CookieYes |
|---|---|---|
| Inth ahead | ||
| Banner speedVisitors cannot act on the page until the banner is up. | On screen in a median 25 ms | On screen in a median 393 ms |
| Open source, no lock-inYou can read, fork and keep the code that decides when each script runs. | c15t is open source under Apache-2.0. See Inth open source | Commercial CMP and SDK |
| Agent migration briefYour coding agent can plan the move from your own codebase. | Copy the prompt under How to move from CookieYes into your coding agent | No brief for this move |
| Both | ||
| Consent state in your code and server renderThe first render already knows the visitor’s choice, so nothing flashes or starts early. | Next.js and TanStack Start resolve consent on the server, per request | Next.js SDK with server helpers; the server knows the choice only when you pass it in |
| The banner as your own componentCopy and design changes ship in a pull request, in your design system. | Ready components in your framework, with themes, component parts or headless hooks | React components, headless primitives and hooks |
| Hosted consent recordsYou can show what each visitor chose, and when. | Every saved choice, region and policy version in your Inth dashboard | Consent log with CSV export |
| Regional rules and Global Privacy ControlEach visitor sees the banner their region requires. | Opt-in, opt-out or no banner by country and US state; reads the Global Privacy Control signal. See regional banners | Geo-targeting and Global Privacy Control on Pro and Ultimate |
| IAB TCFAd tech partners read consent through the IAB framework. | IAB TCF 2.4 through @c15t/iab. Inth is a registered IAB Europe CMP, ID 490 | IAB TCF v2.4 on Pro and Ultimate |
| Google Consent Mode v2Google Ads and Analytics need denied defaults and an update after each choice. | The Google Tag Manager helper sends the denied default before gtm.js, then an update after each choice | Google Consent Mode |
| Script, iframe and network blockingNothing optional runs before the visitor says yes. | Script loader, iframe blocker and network blocker tied to consent categories | Auto-blocking, and network blocking in the SDK |
| Pricing you can work outYou can budget for growth before you talk to sales. | Priced on consent sessions, and bots and AI agents do not count. $474 a month at 100,000 visits, on the pricing page | Published plans, priced by pageviews per domain |
| CookieYes ahead | ||
| Added first-load sizeBytes the banner adds before the page is usable. | +104 KB | +31 KB |
| Automatic cookie scanningSomeone has to find each new cookie and sort it into a category. | Not part of Inth Consent. Website audit shows what your pages load | Scheduled cookie scanning |
| Policy generatorsLegal pages have to match what the site does. | Not part of Inth Consent. Keep your current policy tool | Cookie policy and privacy policy generators |
CookieYes details come from its public docs and pricing pages, read on October 30, 2026. Read the developer comparison.
What each costs as traffic grows
| Traffic | Inth Consent | CookieYes |
|---|---|---|
| 10,000 visits a month | $86 a month on Starter | $10 /month /domain (Basic, 100,000 pageviews/month) |
| 100,000 visits a month | $474 a month on Pro | $10 /month /domain (Basic, 100,000 pageviews/month) |
| 1,000,000 visits a month, or talk to us about Enterprise | $4,374 a month on Business | $55 /month /domain (Ultimate, unlimited pageviews) |
CookieYes pricing, . Bots and AI agents don't count as sessions, and reloads within 30 minutes count once, so you may pay for fewer sessions than your visits. CookieYes counts pageviews, not visits: it prices each domain by pageviews and bills extra pageviews on Basic and Pro. A visit can count as several pageviews. Geo-targeting, Global Privacy Control and IAB TCF start on the Pro plan.
How to move from CookieYes
Bring your current setup, renewal date and quote. We’ll map the switch with you.
Contact salesPaste this into your coding agent
Plan a migration from CookieYes to Inth Consent, built on c15t, for this codebase. Find the CookieYes setup and Consent Mode wiring, map every tag to a c15t integration and consent category, propose how to run c15t on a staging route while CookieYes stays live, and list what to verify before cutting over. Use https://c15t.com/docs/comparisons/cookieyes and https://c15t.com/docs/integrations/overview.
Questions about the switch
Yes. The c15t Google Tag Manager helper sends the Consent Mode v2 denied default before gtm.js loads, then an update after each choice. Map your categories, then check each tag after a visitor choice.
CookieBench publishes each framework and profile separately. The current Next.js banner median is 25 ms on desktop and 252 ms on emulated mobile. Compare tools within the same framework and profile. These are lab results, not a guarantee for your site. See current c15t results.
We’ll map your records with you. There is no importer, so we plan together which CookieYes records to keep, where they live and what Inth records from the switch on. Ask counsel how long to keep the old records.
Yes. Use c15t themes, replace component parts or build your own markup with the headless hooks. The banner then uses your design system.
Yes. Each region gets its own rule: opt-in, opt-out or no banner. c15t reads the Global Privacy Control signal and never stores it as a refusal the visitor did not make. See regional banners.
Not inside Inth Consent. Website audit shows what your pages load, so you can declare each service in c15t and review it in a pull request.
Keep your policy tool. Inth Consent pairs with it, and each recorded choice carries the policy version the visitor saw.
Inth Consent runs on c15t, which is open source under the Apache-2.0 license. See Inth open source.
Yes. Inth has a SOC 2 Type 2 report, shared under NDA. Request it from the Trust center or read about the audit.
Paste the prompt under How to move from CookieYes into your coding agent to map your CookieYes categories and tags. Then run both banners against the same visitor journeys on a staging route. Talk to us about your setup.