Compare c15t and iubenda to choose how much control you need over consent, your application, and your records.

c15t is the stronger fit when your product team wants to own the consent interface, vendor rules and record backend. Your developers can change its open-source code. They can build consent into the application they already build.

Choose iubenda if you want consent tools, website scans, and legal documents in one managed package. Its plans combine these products with different features and usage limits.

This page covers the current alpha release. Check the upgrade guide before you change a current installation.

c15t

65ms

On desktop. 241 ms on a mid-tier phone.

See the evidence

iubenda

436ms

On desktop. 2.69 s on a mid-tier phone.

See the evidence

c15t’s banner appears 371 ms sooner than iubenda’s on desktop.

IAB TCF means the IAB Transparency and Consent Framework. It defines rules for consent to vendors and purposes.

What you need	c15t	iubenda
Use your application framework	Native adapters for web frameworks	A hosted script and integrations for site platforms
Read consent in your code	Reactive state through framework hooks	Browser functions and callbacks
Send the banner from your server	Supported when your server waits for consent resolution	The web guide uses a hosted banner script
Match your product design	Themes, components, or your own interface	Custom styles and banner content
Set when vendors run	Category and vendor rules for scripts and embeds	Automatic blocking, manual tags, and tag-manager integrations
Give visitors vendor choices	Vendor switches outside IAB TCF, plus IAB controls	Purpose categories and IAB vendor controls
Choose where records stay	Inth hosts the backend and stores records in its database. Self-hosting is optional	A managed consent service
Keep evidence of consent	Records in the selected backend	Consent logs in all current plans
Manage legal documents	Your documents, with helpers for versions and signed snapshots	Generated policies and other legal tools
Discover cookies automatically	Not included in the c15t packages	Website scans
Get help from an assistant	Docs and skills in installed packages	A Claude and ChatGPT connector

iubenda sources: integration guide, automatic blocking, consent logs, and assistant connector.

Build the consent interface you want while c15t handles consent state. Start with the c15t banner and preference centre. Change the theme, replace component parts, or build the interface yourself.

c15t supports React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro, and TanStack Start. A script-tag package serves sites without these frameworks.

Your video placeholders, vendor scripts, and privacy controls can use the same consent state. Framework hooks let application code read changes to that state.

Your team can review those changes with the rest of the product code. See the guides for custom styles and your own interface.

iubenda also has custom styles and browser functions. c15t adds native framework components that your developers can compose into the application.

Get started

docs/comparisons/iubenda.md