---
title: c15t vs Silktide Consent Manager
description: Choose c15t for native application state, regional policy and
  backend records. Compare Silktide's free browser manager and the setup c15t
  adds.
group: reference
lastModified: "2026-10-10T16:01:45+01:00"
---
## 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.

## Let Inth run your consent backend

You need a backend to store consent records outside the visitor's browser. [Inth](https://inth.com) builds c15t and hosts that backend and its database for c15t's framework integrations, browser package and headless API. Your consent interface and vendor controls stay in your application.

Connect your application to an Inth project with the [framework setup guide](/docs/frameworks). Inth also serves your consent policy, so static sites can use it without their own application server.

Offline mode keeps choices on the visitor's device and creates no remote consent records. Use it for development and tests, not production.

You can [self-host the c15t backend](/docs/self-host/overview) when your team needs to operate the service. Your team then owns the database, backups, updates and availability.

## Compare the scope beyond the banner

|What you need|c15t|Silktide Consent Manager|
|--|--|--|
|Use consent in application components|Native framework adapters and reactive state|Browser configuration and callbacks|
|Choose policy by visitor context|Backend policy resolution and regional rules|Configure consent types and defaults in the browser setup|
|Show preference controls|Category and vendor choices|Configurable consent types and preference modal|
|Control vendor scripts|Integration helpers, request rules and embeds|Script injection per consent type and callbacks|
|Use Google Consent Mode|Google tag and GTM integrations|Consent Mode updates and GTM events|
|Handle withdrawal|Reload by default. Optional declared data cleanup|Reload after the visitor revokes consent for injected scripts|
|Keep remote records|Inth hosts the backend and stores records in its database. Self-hosting is optional|No managed record service documented with the browser library|
|Customise the interface|Themes, component parts and headless APIs|Configurable text, appearance and source code|
|Budget for use|No licence fee. Production backend costs remain|Free browser tool without traffic or domain limits|

Sources: [Silktide product scope](https://silktide.com/consent-manager/) and [configuration and source](https://github.com/silktide/consent-manager).

## 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](/docs/frameworks) or a [headless interface](/docs/frameworks/react/headless). 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.

## Choose how the page receives consent

For Next.js, c15t supports [streamed, awaited and browser paths](/docs/frameworks/next/rendering). In the App Router, use the default streamed path to let the page appear before consent resolves.

The banner follows in a later chunk of the same response, before hydration. To send the page and the banner together, use an awaited path. That adds a wait, so measure the effect on your application.

Silktide's published setup runs in the browser. c15t's advantage here is its documented framework and server workflow, not a measured speed claim.

## What c15t does not include

* **A free managed record service.** Inth and self-hosted operations have costs beyond the software licence.
* **The same account-free production workflow.** The recommended c15t setup connects to a backend.
* **Automatic discovery of every site script.** Register the relevant vendors and remove their old loaders.
* **A zero-request guarantee from Consent Mode.** Some integrations run with denied signals before consent.

If local preferences and a free browser manager cover the requirement, Silktide remains a reasonable choice. c15t is the stronger choice when policy and records must be part of the application.

## Check signals and actual requests

Build a trial with [Inth and the framework guide](/docs/frameworks). Use the [Google tag](/docs/integrations/google-tag) or [GTM guide](/docs/integrations/google-tag-manager) for your setup.

Inspect the initial signals, acceptance, rejection and later withdrawal. Check the requests made by the tags inside the container too.

Use the [verification guide](/docs/guides/verify-consent) to compare browser behaviour with saved records.

Sources checked on 6 October 2026. The release covered here is an alpha. Silktide's wider paid website platform is outside this comparison.