c15t is the stronger fit when you want control of the consent engine and record service as well as the banner. Its native components and headless APIs connect consent to your application.
CookieScript combines banner settings, site scans and hosted consent records. Paid plans also let you download and host the banner's JavaScript file.
<include src="../shared/comparisons/inth-hosting.mdx" />
| What you need | c15t | CookieScript |
|---|---|---|
| Integrate with your application | Native framework components and state | Browser script with custom functions and events |
| Create a custom interface | Themes, component parts and headless APIs | Banner design settings and programmatic controls |
| Host frontend code yourself | Packages in your application | Downloadable banner JavaScript on paid plans |
| Run the record backend | Inth hosts the backend and stores records in its database. Self-hosting is optional | Hosted consent records. Banner download does not establish a deployable record backend |
| Control scripts | Declared category and vendor rules | Automatic script controls and manual setup |
| Discover cookies | No automatic scanner in the packages | Website scans and cookie declarations |
| Update a local installation | Review and deploy package upgrades | Download the banner file again after account changes |
Sources: CookieScript plans, self-hosted banner guide and custom functions.
CookieScript's local file option is useful when your team needs to control asset delivery. Its guide also notes manual file updates and unavailable geo-targeting on that path.
c15t gives your team another level of control: the framework components, consent engine and backend source. You can change the code and run the backend with your own database.
That control brings work. Your team owns deployment, updates and operations when it runs the service itself. Inth remains the recommended managed path.
Do not treat a locally hosted banner file and a complete backend deployment as the same requirement. Check where choices go and who operates that service.
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.