Run a free scan

Inth vs CookieYes

CookieYes runs consent as a hosted banner with auto-blocking and scheduled scanning. Inth Consent runs it inside your application through c15t, with the records hosted for you. Which one fits depends on what your team wants to own.

Ask your coding agent
Audit this codebase for CookieYes and estimate a move to Inth Consent, built on c15t. Find the CookieYes setup and any Consent Mode and tag manager wiring, list every analytics, advertising and chat tag, then report what c15t would replace, which consent category each tag needs, and what the page would stop loading before consent. Use https://c15t.com/docs/comparison and https://c15t.com/docs/integrations/overview.
Talk to Inth
Trusted by
  • Expo
  • Zed
  • Infisical
  • Unkey
  • Chelsea Piers
  • Mario Testino
  • Roboto Studio
  • Cal.com
  • Mastra

Which platform fits your team?

Tick the needs that matter to your team and see which platform meets more of them.

What matters to your team?

Inth Consent

Built for teams that own consent in their application.

7of 8 needs· Closer fit

CookieYes

Built for template banners with automatic blocking.

5of 8 needs

  • Consent state in your React and Next.js code

    Inth Consent, Fits: Inth Consent · c15t packages expose consent state to your components and your server

    CookieYes, Not the focus: CookieYes · Hosted installation code and CMS setup guides

  • Banner on screen in under 100 ms

    Inth Consent, Fits: Inth Consent · 89 ms to a visible banner on the CookieBench c15t Next.js example

    CookieYes, Not the focus: CookieYes · 246 ms on the CookieBench CookieYes example

  • Hosted consent records

    Inth Consent, Fits: Inth Consent · Every saved choice, region and policy version in your Inth dashboard

    CookieYes, Fits: CookieYes · Centralised consent log

  • Script, iframe and network blocking

    Inth Consent, Fits: Inth Consent · Script loader, iframe blocker and network blocker tied to consent categories

    CookieYes, Fits: CookieYes · Cookie auto-blocking

  • Google Consent Mode v2

    Inth Consent, Fits: Inth Consent · Denied defaults and consent updates through the Google integrations

    CookieYes, Fits: CookieYes · Google Consent Mode support

  • Hosted cookie scanning and classification

    Inth Consent, Not the focus: Inth Consent · Not part of Inth Consent; services are declared in code through integration manifests

    CookieYes, Fits: CookieYes · Scheduled cookie scanning

  • Consent state in server rendering

    Inth Consent, Fits: Inth Consent · Available through the c15t framework packages

    CookieYes, Not the focus: CookieYes · Tested installation is a browser script outside your server render

  • Published self-serve pricing

    Inth Consent, Fits: Inth Consent · Free, Starter and Pro plans with usage pricing on the pricing page

    CookieYes, Fits: CookieYes · Free account and paid plans

Talk to InthSee pricing

Watch the banner arrive.

Both banners were timed on the same CookieBench page on 30 September 2026. Each lane runs until its banner is on screen; the number beside it is the measured time.

  1. Inth (c15t Next.js)
    0 ms 
    Banner visible · 89 ms
  2. CookieYes
    0 ms 
    Banner visible · 246 ms

Page requested · 0 ms

 

Keep every tag you already run.

Inth Consent runs on c15t, which ships helpers for the analytics, advertising, chat and tag-manager tools you use today. Each one loads only when its consent category is granted, so consent is enforced in your implementation rather than by a script bolted on top.

Your privacy choices

Choose which optional cookies this example site can use.

Tag managersdenied defaults

  • Google Tag Manager: denied defaults

Analyticsblocked

  • Google Analytics 4: blocked
  • Ahrefs: blocked
  • Adobe Analytics: blocked
  • Amplitude: blocked
  • Cloudflare: blocked
  • Microsoft Clarity: blocked
  • Databuddy: blocked
  • Rybbit: blocked
  • Fathom: blocked
  • Heap: blocked
  • Mixpanel: blocked
  • Hotjar: blocked
  • Hightouch: blocked
  • LogRocket: blocked
  • Matomo: blocked
  • PostHog: blocked
  • Promptwatch: blocked
  • Pirsch: blocked
  • RudderStack: blocked
  • Segment: blocked
  • Plausible: blocked
  • Umami: blocked
  • Vercel Analytics: blocked

Functionalblocked

  • Crisp: blocked
  • Intercom: blocked
  • Google Maps: blocked
  • YouTube: blocked

Ads & pixelsblocked

  • Google Ads: blocked
  • Meta Pixel: blocked
  • TikTok Pixel: blocked
  • LinkedIn Insight Tag: blocked
  • Snapchat Pixel: blocked
  • Reddit Pixel: blocked
  • X Pixel: blocked
  • Microsoft UET: blocked
  • Clearbit: blocked
Talk to InthSee all integrations

Consent belongs in your implementation plan

You wire consent into the app once. After that it ships with your releases.

Install c15t, tell it which category each tag belongs to, and point it at your hosted project. That is the setup. With CookieYes the same work lives in a dashboard and a script tag, which is fine until a developer needs to know, in code, whether marketing consent was given. Either way, test it: accept, reject, change your mind, and check what actually loads.

Inth Consent

See consent in your dashboard.

Every saved choice, region and policy version in one place, so you can answer a regulator or a customer without exporting anything.

How Inth Consent and CookieYes compare

Two ways to run website consent: application-owned packages, or a hosted banner with automatic blocking.

Website consent comparison: Inth Consent and CookieYes
Team workflowConsent UI and behaviour managed alongside your application code, with a hosted dashboardTemplate-based banners and automated cookie management
Benchmark snapshotScore 95; 89 ms in the c15t Next.js example; 0 KB network impactScore 66; 246 ms; 132 KB network impact
Talk to InthSee pricing

Compare the total consent cost

Drag the slider to your monthly sessions. Inth Consent picks the cheapest published plan and adds usage at the published rate. CookieYes publishes its own plans; check them against the same traffic.

1,000

Inth Consent

$0/ mo

Cheapest published plan

Free · within included usage

Free
$0
Starter
$20
Pro
$50

CookieYes

Free tier and paid plans

≈ 33

sessions a day

See pricingTalk to Inth

Pricing

Pricing you can read before you call

Every plan runs the full Inth Consent infrastructure. Go beyond included usage for $0.001 per request, or request a custom plan.

Free

For developers evaluating or shipping internal tools.

$0/ mo
  • 1 project
  • 5,000 sessions & consent saves /mo
  • All paid features on dev instances
  • Production with usage billing
  • Community + docs support
Start for free

Starter

Most popular

For small sites moving consent into their application.

$20/ mo
  • Everything in Free
  • 2 projects
  • 25,000 sessions & consent saves /mo
  • Production instances included
  • Policy packs included
Start now

Pro

For growing businesses and agencies managing many sites.

$50/ mo
  • Everything in Starter
  • Unlimited projects
  • 100,000 sessions & consent saves /mo
  • Policy packs included
  • Chat support
Start now

Need enterprise capacity?

Custom usage, advanced SDKs, APIs, integrations, implementation guidance and priority support with a dedicated Slack channel.

Contact sales

Moving from CookieYes?

Bring your current setup, renewal date and quote. We’ll map the switch with you. If you want a head start, have your coding agent draft the plan.

Plan it with 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/comparison and https://c15t.com/docs/integrations/overview.
Talk to Inth

Inth vs CookieYes: common questions

Scope, consent architecture and evaluation.

Talk to Inth

Both approaches support consent-aware Google integrations. Review category mappings, denied defaults and updates, then verify actual tag behaviour after each visitor choice.