c15t is the stronger fit when your product team needs to understand and change how consent affects the application. Its components, vendor rules and backend are open source.
This page compares Osano's commercial consent platform. Its separate open-source Cookie Consent project has a different licence scope.
<include src="../shared/comparisons/inth-hosting.mdx" />
c15t’s banner appears 543 ms sooner than Osano’s on desktop.
| What you need | c15t | Osano commercial CMP |
|---|---|---|
| Integrate with application code | Native framework components and hooks | Hosted CMP with JavaScript functions and events |
| Match your interface | Themes, component parts or headless UI | Banner editor and custom CSS |
| Control vendor execution | Registered integrations and explicit consent rules | Cookie classification and configured tag blocking |
| Choose the Next.js response | Server, streamed or browser consent resolution | Hosted script integration |
| Keep consent records | Inth hosts the backend and stores records in its database. Self-hosting is optional | Managed records with consent search |
| Change and run the engine | Apache-2.0 source and a deployable backend | Commercial platform |
| Classify site cookies automatically | Not included in the c15t packages | AI-assisted cookie classification |
| Get a contractual fines guarantee | Not included with the open-source software | Advertised guarantee with conditions |
| Budget for the service | No software licence fee. Backend costs remain | Contracted traffic based on delivery of Osano.js |
Sources: Osano CMP, JavaScript API, consent search and traffic definition.
With c15t, your team declares a vendor beside the application feature that introduces it. The integration connects that vendor to consent state.
The same state can drive a privacy settings screen or a blocked video placeholder. Use headless APIs when your design needs different markup.
Osano also has a JavaScript API. c15t gives you native framework state and the implementation behind that state, so your team can trace behaviour through its own code.
Switch a category off. Its vendors wait.
42 of 42 running
Always loads and gets consent signals.
- Cloudflare Zaraz, always loads and gets consent signals
- Google Tag Manager, always loads and gets consent signals
- Google Tag, always loads and gets consent signals
- Databuddy, always loads and gets consent signals
- Mixpanel, always loads and gets consent signals
- PostHog, always loads and gets consent signals
- Microsoft UET, always loads and gets consent signals
- Ahrefs Analytics
- Adobe Analytics
- Amplitude
- Cloudflare Web Analytics
- Microsoft Clarity
- Fathom Analytics
- Heap
- Matomo Analytics
- OneDollarStats
- Hotjar
- Hightouch
- LogRocket
- Plausible Analytics
- Promptwatch
- Pirsch
- RudderStack
- Segment
- Rybbit Analytics
- Umami Analytics
- Vercel Analytics
- Klaviyo
- Clearbit
- Meta Pixel
- OpenAI Pixel
- Pinterest Tag
- Reddit Pixel
- TikTok Pixel
- LinkedIn Insight Tag
- Snapchat Pixel
- X Pixel
- YouTube
- Crisp
- Front Chat
- Intercom
- Google Maps
Import each helper from @c15t/integrations.
Paste this line into your agent. It reads the setup brief and does each step.
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.
The CLI plans the setup. You check the plan, then apply it.
To do each step yourself, read the quickstart. To get JSON results for scripts and agents, read the automation guide.
Inth hosts the backend, the policy rules and the IAB CMP ID.