Skip to main content

c15t vs Silktide Consent Manager

Choose c15t for native application state, regional policy and backend records. Compare Silktide's free browser manager and the setup c15t adds.

Get started

Choose c15t when consent needs to reach the application.

c15t is the stronger fit when your product needs consent state across components, vendor rules and backend records. It gives your team a common model for the interface and the code behind it.

Silktide Consent Manager is a free, open-source browser manager. It supports preference controls, consent-based script injection and Google Consent Mode. It is more than a decorative banner.

<include src="../shared/comparisons/inth-hosting.mdx" />

Compare the scope beyond the banner.

What you needc15tSilktide Consent Manager
Use consent in application componentsNative framework adapters and reactive stateBrowser configuration and callbacks
Choose policy by visitor contextBackend policy resolution and regional rulesConfigure consent types and defaults in the browser setup
Show preference controlsCategory and vendor choicesConfigurable consent types and preference modal
Control vendor scriptsIntegration helpers, request rules and embedsScript injection per consent type and callbacks
Use Google Consent ModeGoogle tag and GTM integrationsConsent Mode updates and GTM events
Handle withdrawalReload by default. Optional declared data cleanupReload after the visitor revokes consent for injected scripts
Keep remote recordsInth hosts the backend and stores records in its database. Self-hosting is optionalNo managed record service documented with the browser library
Customise the interfaceThemes, component parts and headless APIsConfigurable text, appearance and source code
Budget for useNo licence fee. Production backend costs remainFree browser tool without traffic or domain limits

Give the product one consent model.

With c15t, a settings screen can read the same state that controls a vendor or video embed. Your developers can test that behaviour with the rest of the application.

Use framework components or a headless interface. The backend supplies policy and receives consent records.

That gives you a defined route beyond local browser preferences. A visitor's local choice and a confirmed backend record remain separate events.

Moving off Silktide Consent Manager across many sites?

Inth builds c15t and runs migrations for large teams, from the first audit to the day you remove the old script.

Talk to Inth

Install c15t. Get 42 integrations.

c15t maintains each typed helper. Most helpers load their vendor only after consent, and stop it when the visitor withdraws consent.

Import each helper from @c15t/integrations.

Browse the integrations

Start in minutes.

Paste this line into your agent. It reads the setup brief and does each step.

Ask your coding agent
Set up c15t in my app: c15t.com/SKILL.md

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.

Inth hosts the backend, the policy rules and the IAB CMP ID.

Compare c15t with your consent tool.

The facts about each tool come from its own published pages.

Read the comparison overview