---
title: c15t vs Osano
description: Choose c15t for native consent components and control of vendor
  code and records. Compare Osano's classification, managed operations and
  service guarantees.
group: reference
lastModified: "2026-10-10T16:01:45+01:00"
---
## Choose c15t for control your developers can inspect

c15t is the stronger fit when your product team needs to understand and change how consent affects the application. Its components, vendor rules and backend are open source.

This page compares Osano's commercial consent platform. Its separate open-source Cookie Consent project has a [different licence scope](https://www.osano.com/cookieconsent/documentation/license/).

## 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 implementation and the service

|What you need|c15t|Osano commercial CMP|
|--|--|--|
|Integrate with application code|Native framework components and hooks|Hosted CMP with JavaScript functions and events|
|Match your interface|Themes, component parts or headless UI|Banner editor and custom CSS|
|Control vendor execution|Registered integrations and explicit consent rules|Cookie classification and configured tag blocking|
|Choose the Next.js response|Server, streamed or browser consent resolution|Hosted script integration|
|Keep consent records|Inth hosts the backend and stores records in its database. Self-hosting is optional|Managed records with consent search|
|Change and run the engine|Apache-2.0 source and a deployable backend|Commercial platform|
|Classify site cookies automatically|**Not included in the c15t packages**|AI-assisted cookie classification|
|Get a contractual fines guarantee|**Not included with the open-source software**|Advertised guarantee with conditions|
|Budget for the service|No software licence fee. Backend costs remain|Contracted traffic based on delivery of Osano.js|

Sources: [Osano CMP](https://www.osano.com/solutions/consent-management-platform), [JavaScript API](https://docs.osano.com/en-US/osano/article/4iKPKFqX-developer-documentation-consent-javascript-api), [consent search](https://docs.osano.com/en-US/osano/article/rtirm0V6-cookie-consent-consent-search) and [traffic definition](https://docs.osano.com/en-US/osano/article/7Xe6qqNl-how-does-osano-price-for-consent-management).

## Review consent with the feature that needs it

With c15t, your team declares a vendor beside the application feature that introduces it. The [integration](/docs/integrations/overview) connects that vendor to consent state.

The same state can drive a privacy settings screen or a blocked video placeholder. Use [headless APIs](/docs/frameworks/react/headless) when your design needs different markup.

Osano also has a JavaScript API. c15t gives you native framework state and the implementation behind that state, so your team can trace behaviour through its own code.

## Keep the backend choice open

With Inth, you do not need to run a database. If your requirements change, the c15t backend is available for your team to deploy and change.

That choice is useful when your organisation needs its own infrastructure or record access. It also makes your team responsible for availability, migrations and backups.

Osano has consent records and a search workflow. c15t's distinction is control of the record system, not the existence of consent evidence.

## What c15t does not include

* **Automatic cookie discovery or AI classification.** Keep the vendor inventory and configure the relevant integrations.
* **Osano's wider privacy operations.** Subject-rights case management and enterprise data discovery are outside the c15t packages.
* **A promise to pay regulatory fines.** The open-source licence does not include that commercial guarantee.
* **Automatic control of every current tag.** A banner alone cannot stop code loaded elsewhere.

Some c15t integrations use denied consent signals while the vendor code still loads. Check the integration's behaviour before you expect zero requests.

## Prove control on the tags you run

Choose c15t when application control and backend ownership are the priorities. Osano can fit better when you need managed privacy operations and contractual services.

Start with [Inth and your framework guide](/docs/frameworks). Test a direct vendor and a vendor inside your tag manager.

Remove duplicate loaders, then check rejection, acceptance, reload, withdrawal and the saved record. Follow the [verification guide](/docs/guides/verify-consent).

Sources checked on 6 October 2026. The release covered here is an alpha. Compare service quotes based on each provider's traffic definition.