Skip to main content

c15t vs CookieHub

Choose c15t for native web framework coverage and backend ownership. Compare CookieHub's React components, consent APIs, automatic scans and hosted logs.

Get started

Keep your consent system under product-team control.

c15t is the stronger fit when you want native consent components across web frameworks and control of the backend. Your team can review and change the engine with the application.

CookieHub combines managed banners, scans and consent logs. It also has React components and developer APIs, so framework integration is an overlap.

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

Compare what you get.

What you needc15tCookieHub
Use native web componentsReact, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro and TanStack StartReact package plus browser and CMS integrations
Connect application featuresReactive state, vendor choices and headless APIsJavaScript methods, events and category controls
Control scripts and embedsDeclared categories and vendors for scripts, requests and embedsAutomatic controls plus React script, analytics and video components
Choose the record backendInth hosts the backend and stores records in its database. Self-hosting is optionalManaged consent log, enabled per domain
Find cookiesNo automatic scanner in the packagesWebsite scanner
Handle regional rulesBackend policy and framework configurationManaged region settings
Build a custom interfaceThemes, component parts or your own markupBanner settings and JavaScript controls

Compare framework depth and source ownership.

CookieHub's React package can control scripts, analytics and video embeds. Its events let an application respond when a visitor changes a category choice.

c15t combines native framework adapters with an engine and backend that your team can change. Use its components or build product-specific controls with headless APIs.

This is useful when your product uses different web frameworks or when consent changes need code review. The benefit is control of the full system.

For Next.js, c15t also documents server, streamed and browser paths. The App Router's default streamed path does not put the banner in the initial HTML. Choose and test the path your application needs.

Moving off CookieHub 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

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