c15t is the stronger fit when your main task is consent inside a web application. Your team can change the components, review vendor rules and release the consent code with the product.
Ketch serves a broader need: consent across identities and connected systems, with privacy operations in the same platform. It also offers APIs, SDKs and custom interfaces.
<include src="../shared/comparisons/inth-hosting.mdx" />
c15t’s banner appears 1.65 s sooner than Ketch’s on desktop.
| What you need | c15t | Ketch |
|---|---|---|
| Integrate with web application code | Native framework components and reactive consent state | Web APIs and SDKs. Ketch also advertises React support |
| Build your own interface | Themes, component parts and headless APIs | Visual editor, SDKs and custom integration APIs |
| Choose the backend | Inth, or the Apache-2.0 backend on your own infrastructure | Managed platform. Reviewed public sources do not establish a deployable equivalent backend |
| Review vendor behaviour | Explicit rules for registered scripts, requests and embeds | Tag controls and connectors to other systems |
| Keep consent records | Inth hosts the backend and stores records in its database. Self-hosting is optional | Managed records tied to the visitor and connected systems |
| Find trackers automatically | Not included in the c15t packages | Tracker scans and related analysis |
| Manage data-subject requests and assessments | Not included as a privacy operations suite | Broader platform products |
| Support native mobile apps | No equivalent native mobile SDKs in this comparison | iOS and Android SDKs |
Sources: Ketch consent platform, product documentation, plans and Android SDK.
With c15t, your banner, account settings and embedded content can use the same consent state. Your developers can review those changes beside the features that use them.
The framework guides cover React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro, TanStack Start and plain websites. Use headless APIs when the supplied interface does not fit.
Declare each integration and its consent rules in application code. Individual vendor choices let a visitor refuse one vendor within an accepted category.
Ketch also connects consent to application code. c15t's advantage for this task is the combined framework interface, inspectable engine and deployable backend.
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.