Skip to main content

c15t vs OneTrust

Choose c15t to own the consent engine, framework components and backend. Compare OneTrust's headless API, cookie scans and broader privacy operations.

Get started

Which one fits your team.

Pick OneTrust if consent is one part of a larger privacy programme run by a legal or privacy team. It scans your site for cookies, and separate OneTrust products cover more of that programme.

Pick c15t if your engineers own consent. The banner, the engine that decides what may run and the backend that stores records are all code your team can read, change and ship with the rest of the product. OneTrust has a headless API too, so either one lets you build your own UI. With c15t you can also change the engine and the backend.

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

Timed on the same page.

Cookiebench loads each consent manager 15 times on the same Next.js page and times how long its banner takes to appear. Times read on 12 October 2026.

c15t

27ms

On desktop. 240 ms on a mid-tier phone.

See the evidence

OneTrust

629ms

On desktop. 3.92 s on a mid-tier phone.

See the evidence

c15t’s banner appears 602 ms sooner than OneTrust’s on desktop.

Feature by feature.

What you needc15tOneTrust
Build application consent UINative components, themes and headless APIsWeb CMP UI and a headless Server-Side CMP API
Resolve consent on the serverFramework helpers and cached public policyServer-Side CMP API
Read or change consent in codeReactive framework state and actionsJavaScript methods and consent-change callbacks
Control vendor executionDeclared integrations, request rules and embedsAutomatic blocking, tag-manager integrations and script controls
Own the backend implementationApache-2.0 backend that you can deployOneTrust platform and APIs
Store consent recordsInth hosts the backend and stores records in its database. Self-hosting is optionalConsent transaction database
Scan authenticated or hidden pagesNot included in the c15t packagesDocumented website scans
Compare banner layoutsPresentation experiments with your feature flagsA/B tests and template targeting
Run a wider privacy programmeNo complete privacy operations suite in c15tSeparate OneTrust products extend the consent scope

What owning the code gets you.

c15t is Apache-2.0. Your developers can read it, patch it and pin versions like any other dependency. Consent changes can go through the same code review as the features that depend on them.

The banner and your app share one consent state. A privacy settings screen in your account area can read the same permissions that gate a video embed or your analytics. If the stock components don't fit, build your own on the headless APIs.

Moving off OneTrust 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 44 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

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