c15t is the stronger fit when your developers need consent inside product features and control over the record backend. You can change the interface and engine with the rest of your application.
Termly suits teams that want consent and legal-policy tools in one hosted product. Its scanner, banner settings and policy generators address work outside the c15t packages.
<include src="../shared/comparisons/inth-hosting.mdx" />
| What you need | c15t | Termly |
|---|---|---|
| Connect to application code | Native framework components and reactive state | Hosted script, browser events and consent APIs |
| Own the interface | Themes, component parts and headless APIs | Custom banner layouts, languages and display settings |
| Control vendor code | Declared category and vendor rules for scripts, requests and embeds | Auto Blocker with custom rules and manual controls |
| Read choices on the server | Backend APIs and framework server paths | Consent API for category and cookie choices |
| Store records | Inth hosts the backend and stores records in its database. Self-hosting is optional | Termly's hosted consent records |
| Find cookies | No automatic scanner in the packages | Site scans and classification |
| Generate legal documents | Not included | Privacy, cookie policy and other document generators |
| Collect privacy requests | No bundled case management suite | Embeddable data-subject request form |
Sources: Termly consent platform, consent data flow and Consent API.
With c15t, consent can control an embed, an analytics integration or an application feature. Declare the relevant categories and vendors beside the code that uses them.
The headless APIs let your team build privacy controls into product screens. Vendor consent supports a choice about one service within a category.
Termly also exposes consent state and events. Its server API can retrieve a visitor's category and cookie choices. Developer access alone is not a reason to prefer c15t.
c15t adds a native component workflow and source code for both the engine and backend. That combination matters when your team needs to change how the system works.
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.