c15t is an open-source consent management platform for React, Next.js, and modern JavaScript apps. It keeps cookie banners, preference handling, and consent-aware script loading inside application code instead of a third-party widget, and stores consent records in a backend your team controls. Inth maintains the project under Apache-2.0, and the repository has about 1,900 stars.[1][2]
Quick verdict
React and Next.js teams that want consent management inside their application code benefit most from c15t. Its banner and dialog components, consent-aware script loading, and Google Consent Mode v2, Meta Pixel, and IAB TCF 2.3 integrations cover the core developer-led workflow. Teams without developers, or those expecting built-in cookie scanning and classification dashboards, should choose a hosted CMP instead. If you have developers and can run a database-backed backend or accept the managed backend, choose c15t; if you need a no-code dashboard, choose a closed hosted CMP.[1][2][3]
Key features
Banner and dialog components Teams ship cookie banners and preference dialogs with React, Next.js, or headless APIs, customizing copy, layout, and behaviour in code rather than a vendor dashboard.[1][2]
Consent-aware script loading Analytics and marketing scripts load only under configured consent rules, with iframe and network blocking that holds back restricted content until consent is granted.[1]
Google Tag Manager and Consent Mode v2 The platform connects to Google Tag Manager with Consent Mode v2 support, so tags respect stored consent choices without custom glue code.[1]
Meta Pixel and IAB TCF 2.3 Named integrations cover Meta Pixel and IAB TCF 2.3, placing c15t in the standardized ad-consent workflow publishers and advertisers expect.[1]
Three backend modes The backend runs managed through Inth, self-hosted with your own database, or in an offline browser-only mode for teams that want no server at all.[1]
Broad framework support First-class support covers React, Next.js, and vanilla JavaScript with headless APIs, plus Astro, Svelte, Nuxt, Remix, Solid, and Angular.[1][2]
Own-database consent records Consent records and audit logs live in your own database, which suits teams with data-residency or audit requirements.[1]
Customizable UI themes Banner and dialog styling is themeable in code, so the consent surface can match the product instead of looking like a third-party embed.[1]
Who will love it
React and Next.js product teams React and Next.js teams building consent into their app code will love c15t, because components, hooks, and headless APIs match how they already ship.[1][2]
Teams leaving closed CMP widgets Sites replacing a closed hosted CMP widget will love the control, since banners, logic, and data move from a vendor script into their own codebase.[1][2]
Teams needing owned consent data Teams that must keep consent records in their own database will love the self-hosted and offline modes, which avoid sending consent data to a third party.[1]
Who should avoid it
Non-technical site owners Non-technical site owners should avoid c15t, because setup is engineering-led with package installs, handler wiring, and database migrations.[1][2]
Teams wanting automatic scanning Teams expecting built-in cookie scanning and classification workflows should avoid it, since c15t documents no scanner and hosted CMP dashboards own that workflow.[1]
Teams wanting guaranteed compliance Teams looking for a tool that alone guarantees legal compliance should avoid treating any CMP that way; the c15t docs warn the tool itself does not make a site compliant.[1]
Compatibility
Ad and tag stack fit c15t fits sites running Google Tag Manager, Consent Mode v2, Meta Pixel, or IAB TCF 2.3 workflows, which it integrates with directly.[1]
Framework fit It fits React, Next.js, vanilla JavaScript, Astro, Svelte, Nuxt, Remix, Solid, and Angular codebases through components or headless APIs.[1][2]
Questions worth asking
What is the best c15t alternative for non-technical users?
Is c15t really no-code?
How much does c15t cost per month?
Can you self-host c15t?
Yes. c15t documents self-hosting with Docker or manual setup, your own Postgres database, and applied migrations, plus an offline browser-only mode that needs no server.[1]
Sources and editorial review
Source research. Reviewed on October 9, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- c15t - Developer-First Consent Management
official · Observed October 9, 2026
Official c15t homepage: developer-first positioning, banner/dialog components, headless APIs, GTM/Consent Mode/Meta Pixel/TCF integrations, deployment modes, framework list, Wappalyzer adoption figure.
- c15t/c15t repository
official · Observed October 9, 2026
Official c15t GitHub README: Apache-2.0 licence, star count, feature table (banner, blocking modes, GTM/Consent Mode/Meta Pixel/TCF, audit logs, themes, self-host/offline modes), framework support, deployment table with database and migration requirements.
- Should You Build Your Own Cookie Banner? Build vs Buy Guide
official · Observed October 9, 2026
Vendor-adjacent educational guide on build-vs-buy for cookie banners: developer-tool setup burden, missing cookie scanning in developer tools, compliance warning, geo-targeting and consent-record expectations.
- Inth pricing
official · Observed October 9, 2026
Official Inth pricing page: subscription plans plus usage credit packs, checked to scope managed-backend billing claims.