Skip to main content

c15t vs Cookiebot

Choose c15t for native application components, explicit vendor controls and backend ownership. Compare Cookiebot's scan-based setup and the gaps c15t leaves.

Get started

Choose c15t when your team owns the application.

c15t is the stronger fit when consent must work inside your product's code, design system and release process. Your team can build the interface, review vendor rules and choose where consent records stay.

Cookiebot is a strong option for teams that want a hosted banner with automatic website scans. c15t gives application teams direct control over the implementation.

<include src="../shared/comparisons/inth-hosting.mdx" />

Compare what you get.

What you needc15tCookiebot
Integrate with application codeNative framework components and reactive consent stateHosted script with JavaScript methods, events and callbacks
Build your own interfaceThemes, component parts and headless APIsBanner customisation and SDK controls
Choose the Next.js responseStream consent, await it on the server, or resolve it in the browserClient-side banner SDK. Server-side cookie use also documented
Control vendor codeDeclare categories and vendors on scripts, requests and embedsScan-based automatic blocking or manual script tags
Choose the runtime versionVersion the open-source packages with your applicationCookiebot's CMP script must load from its service
Keep consent recordsInth hosts the backend and stores records in its database. Self-hosting is optionalManaged consent log and data export
Discover cookies automaticallyNot included in the c15t packagesWebsite scans and scan reports
Budget for the serviceNo software licence fee. Backend costs remainDomain and subpage tiers. No pageview charge

Make consent part of the product.

With c15t, a video placeholder, privacy settings screen and analytics integration can use the same consent state. Your developers can review them in the same pull request.

Use the supplied interface or build your own through headless APIs. The framework guides cover React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro, TanStack Start and plain websites.

Cookiebot also exposes APIs. c15t's advantage is the native application components and the source code that your team can change.

Moving off Cookiebot across many sites?

Inth builds c15t and runs migrations for large teams, from the first audit to the day you remove the old script.

Talk to Inth

Install c15t. Get 42 integrations.

c15t maintains each typed helper. Most helpers load their vendor only after consent, and stop it when the visitor withdraws consent.

Import each helper from @c15t/integrations.

Browse the integrations

Start in minutes.

Paste this line into your agent. It reads the setup brief and does each step.

Ask your coding agent
Set up c15t in my app: c15t.com/SKILL.md

The setup brief is at /SKILL.md. For the docs, agents can read /llms.txt and /llms-full.txt, or use the MCP server at with no sign-in.

Inth hosts the backend, the policy rules and the IAB CMP ID.

Compare c15t with your consent tool.

The facts about each tool come from its own published pages.

Read the comparison overview