---
title: c15t vs Usercentrics
description: Choose c15t for native framework components and control of the
  consent engine. Compare Usercentrics Web CMP features, service scope and
  costs.
group: reference
lastModified: "2026-10-11T22:43:08+01:00"
---
## Choose c15t for consent your developers can own

c15t is the stronger fit when your team wants native components, consent state in application code and an open-source backend. You can change the interface and the engine that drives it.

This page compares Usercentrics Web CMP. Its App CMP, CTV CMP and other services have separate scope. [Cookiebot has its own comparison](/docs/comparisons/cookiebot).

## 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 control and service scope

|What you need|c15t|Usercentrics Web CMP|
|--|--|--|
|Use application consent state|Native framework hooks and components|Browser UI APIs and events|
|Create a custom interface|Themes, component parts and headless APIs|Banner customisation. Headless Browser SDK for the earlier version, plus a headless SDK for the current version in beta|
|Choose the Next.js response|Server resolution, streamed state or browser resolution|Web script integration. Confirm the required SDK version|
|Own the consent engine|Apache-2.0 source and a deployable backend|Commercial managed service|
|Keep remote records|Inth hosts the backend and stores records in its database. Self-hosting is optional|Central consent log|
|Compare banner variants|Presentation experiments with your flags or built-in assignment|A/B tests, subject to plan or add-on|
|Discover site technologies|**No scanner in the c15t packages**|Automated website scans|
|Budget for use|No software licence fee. Backend costs remain|Session and domain allowances, with plan-dependent features|

Sources: [Usercentrics pricing and features](https://usercentrics.com/pricing/), [developer documentation](https://usercentrics.com/docs/), [earlier Browser SDK](https://usercentrics.com/docs/web/features/v2/browser_sdk/browser_sdk/) and [current-version headless SDK](https://www.npmjs.com/package/@usercentrics/cmp-web-sdk).

## Build consent into your own interface

c15t lets the consent banner, video placeholders and privacy controls use the same application state. Your team can change those components through its normal review and test process.

Start with the stock components, then use [custom styles](/docs/frameworks/react/customize) or a [headless interface](/docs/frameworks/react/headless). You control the markup and can build the interface that your product needs.

Usercentrics also supports custom UI. Its documented headless Browser SDK targets the earlier version, and a headless SDK for the current version is in beta. Confirm support for the edition you plan to use.

Choose c15t for the combination of native adapters and source ownership. Custom colours or API access alone do not distinguish the products.

## Keep experiments and deployment in your workflow

c15t [banner experiments](/docs/guides/banner-experiments) can use your current feature flags. Compare layouts and themes while the policy, categories and policy text stay fixed.

Usercentrics also offers A/B tests. With c15t, your developers can define the experiment with the application and choose the backend that receives the records.

In the Next.js App Router, [choose when the page waits for consent](/docs/frameworks/next/rendering). The default streamed path sends the banner in the server response, before hydration.

## What c15t does not include

* **Automated website scans or a generated library of legal clauses.** These are separate from the c15t consent packages.
* **Every Usercentrics administration workflow.** Do not assume that the open-source backend includes its bulk changes, approval process or enterprise account controls.
* **Automatic migration of current choices.** Map services, purposes and policy versions before you reuse records.
* **A free managed service.** Compare current Inth terms with the Usercentrics plan for your actual traffic.

The c15t backend supports identity links, but that alone does not establish parity with Usercentrics' cross-device workflow. Test the account and device flow that you need.

## Prove the fit on one property

Choose c15t when your application team wants control over the interface, runtime and backend. Usercentrics remains a strong fit for centrally managed website operations.

Start with [Inth and a framework guide](/docs/frameworks). Test one direct vendor and one tag-manager vendor, then check withdrawal and saved records.

Check each property's policy, language and origin configuration before a wider rollout. Use the [verification guide](/docs/guides/verify-consent) to confirm the actual requests.

Sources checked on 6 October 2026. The release covered here is an alpha. Prices and service inclusions depend on the selected plan.