---
title: c15t vs CookieScript
description: Choose c15t to own the consent engine, framework components and
  backend. Compare CookieScript's scans, developer controls and self-hosted
  banner option.
group: reference
lastModified: "2026-10-12T12:44:54+01:00"
lastAuthor: Christopher Burns
---
## Own the consent system from interface to backend

c15t is the stronger fit when you want control of the consent engine and record service as well as the banner. Its native components and headless APIs connect consent to your application.

CookieScript combines banner settings, site scans and hosted consent records. Paid plans also let you download and host the banner's JavaScript file.

## 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 what you get

|What you need|c15t|CookieScript|
|--|--|--|
|Integrate with your application|Native framework components and state|Browser script with custom functions and events|
|Create a custom interface|Themes, component parts and headless APIs|Banner design settings and programmatic controls|
|Host frontend code yourself|Packages in your application|Downloadable banner JavaScript on paid plans|
|Run the record backend|Inth hosts the backend and stores records in its database. Self-hosting is optional|Hosted consent records. Banner download does not establish a deployable record backend|
|Control scripts|Declared category and vendor rules|Automatic script controls and manual setup|
|Discover cookies|**No automatic scanner in the packages**|Website scans and cookie declarations|
|Update a local installation|Review and deploy package upgrades|Download the banner file again after account changes|

Sources: [CookieScript plans](https://cookie-script.com/pricing), [self-hosted banner guide](https://cookie-script.com/download-and-host-javascript-files.html) and [custom functions](https://help.cookie-script.com/en/articles/30246-custom-functions).

## Compare what self-hosting gives you

CookieScript's local file option is useful when your team needs to control asset delivery. Its guide also notes manual file updates and unavailable geo-targeting on that path.

c15t gives your team another level of control: the framework components, consent engine and backend source. You can change the code and run the backend with your own database.

That control brings work. Your team owns deployment, updates and operations when it runs the service itself. Inth remains the recommended managed path.

Do not treat a locally hosted banner file and a complete backend deployment as the same requirement. Check where choices go and who operates that service.

## Keep consent beside the features it controls

Use c15t's [framework components](/docs/frameworks) to connect product settings, embeds and vendor choices to one consent state. Use [headless APIs](/docs/frameworks/react/headless) when you need different markup.

CookieScript also has functions to read consent state and events for banner actions. c15t's advantage is the combined application and backend workflow.

Choose CookieScript when site scans and banner administration are the main tasks. Choose c15t when your developers need to own the full consent system.

## What c15t does not include

* The packages do not scan the site or generate cookie declarations automatically.
* They do not generate privacy policies or replace a legal review.
* Vendor controls cover the targets you configure. Tags already on the site need separate checks.
* A local choice does not prove a successful remote save.

Some integrations load with denied signals. Withdrawal normally reloads the page, and optional cleanup cannot remove all vendor data.

The software has no licence fee. Setup, Inth or your own servers still have costs.

## Test the ownership you need

Set up c15t with the [framework guide](/docs/frameworks). Add one vendor and one embed, then test refusal, acceptance, reload and withdrawal.

Check requests and saved records with the [verification guide](/docs/guides/verify-consent). Compare a package upgrade with CookieScript's hosted and downloaded-file workflows.

Sources checked on 6 October 2026. Self-hosting details describe the documented options, not a measured speed advantage.