c15t is the stronger fit when your team needs consent in a custom web application. Its framework components and backend let you own the consent system independently of WordPress.
Borlabs Cookie is a WordPress product with local visitor data, individual service controls and developer tools. Self-hosting alone does not distinguish c15t from Borlabs.
<include src="../shared/comparisons/inth-hosting.mdx" />
| What you need | c15t | Borlabs Cookie |
|---|---|---|
| Build outside WordPress | Native web framework adapters, browser and headless options | WordPress only |
| Control the interface | Themes, component parts and headless APIs | Dialog settings, custom content placeholders and JavaScript API |
| Let visitors choose services | Category and individual vendor state | Service groups with individual service choices |
| Control scripts and embeds | Declared rules for scripts, requests and embeds | Script, style and content controls |
| Keep records on your servers | Deploy the supplied c15t backend | Consent logs within the WordPress setup. Visitor data stays on your server |
| Use a managed backend | Inth hosts the backend and stores records in its database. Self-hosting is optional | Consent runs within your WordPress installation |
| Discover services | No automatic scanner in the packages | Scanner with suggested service packages |
| Operate within WordPress | Developer setup. No bundled WordPress wizard | Setup assistant, package library, WP CLI and Composer support |
Sources: Borlabs product and platform scope, feature list and JavaScript API.
Borlabs already covers several reasons teams choose a consent tool: local data, service choices, embeds and consent logs. Its API also supports custom integrations.
c15t adds a native workflow across web frameworks. Your team can put privacy controls into a product screen and connect them to shared consent state.
Use headless APIs for your markup. Declare vendors beside the integrations they control.
The backend is a separate service that can run with your chosen database. That separation helps when the application frontend and consent service need their own deployment lifecycle.
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.