c15t is the stronger fit when your developers want to own the consent interface, vendor rules and backend implementation. Changes can follow the same code review and release process as the application.
Didomi combines a shared notice console with SDKs, APIs and consent analytics. It also supports React and custom interfaces, so developer access is common to both products.
<include src="../shared/comparisons/inth-hosting.mdx" />
c15t’s banner appears 433 ms sooner than Didomi’s on desktop.
| What you need | c15t | Didomi |
|---|---|---|
| Integrate with application code | Native adapters across web frameworks | Hosted Web SDK and a React component |
| Build a custom interface | Themes, component parts and headless APIs | Notice customisation and APIs for your own UI |
| Read vendor and purpose choices | Framework state and vendor controls | Web SDK methods and events |
| Choose the Next.js response | Streamed, awaited or browser paths | Hosted SDK integration. Test the required server flow separately |
| Run the backend yourself | Open-source backend with your own database | Didomi platform and consent APIs |
| Keep consent evidence | Inth hosts the backend and stores records in its database. Self-hosting is optional | Consent events and history |
| Compare banner variants | Presentation experiments with your flags or built-in assignment | A/B tests and consent analytics |
| Publish notices from a shared console | Inth service workflow. No equivalent business console bundled in the packages | Console for marketing, legal and engineering teams |
Sources: Didomi platform, Web SDK and React setup, JavaScript API and custom-UI consent events.
c15t lets your privacy controls, gated content and registered vendors use the same state. A designer can change the interface while a developer checks its behaviour in application tests.
Start with the supplied components or build a headless interface. Use vendor controls to connect an individual service to the visitor's choices.
Didomi's React component loads its SDK and receives notice configuration from the Console. c15t gives you native components plus source code for the consent engine.
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.