--- title: c15t vs Complianz description: Choose c15t for consent across custom web applications. Compare Complianz's WordPress plugin and Shopify app, with clear differences in scans, records and legal tools. group: reference lastModified: "2026-10-12T12:44:54+01:00" lastAuthor: Christopher Burns --- ## Keep consent with your application as it grows c15t is the stronger fit when your product needs consent across custom web frameworks. Your team can own the interface, engine and backend independently of a CMS plugin. Complianz has a WordPress plugin and a separate Shopify app. Its WordPress product combines consent controls, scans and legal-document tools. The platform matters when you compare features. ## 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|Complianz| |--|--|--| |Build a custom web application|Native adapters for the documented web frameworks|Native WordPress plugin and separate Shopify app| |Create your own interface|Themes, component parts and headless APIs|WordPress banner settings, custom CSS and HTML templates| |Control services|Declared categories and vendors for scripts, requests and embeds|WordPress Script Center, service choices and content placeholders| |Choose the record service|Inth hosts the backend and stores records in its database. Self-hosting is optional|WordPress Premium includes Records of Consent| |Discover cookies|**No automatic scanner in the packages**|WordPress cookie scan and service detection| |Generate legal documents|**Not included**|WordPress legal-document tools, with plan-dependent scope| |Test banner designs|Presentation and theme experiments with fixed policy and policy text|WordPress Premium lists A/B tests| |Configure CMS plugins|Developer setup in your application|WordPress plugin and service integrations| Sources: [Complianz platforms](https://complianz.io/), [WordPress features](https://complianz.io/features/), [plan differences](https://complianz.io/help/wordpress/faq/complianz-pricing-faqs/) and [developer integrations](https://complianz.io/help/wordpress/configuration/developers-guide-for-third-party-integrations/). The WordPress features above do not establish the same feature set in the Shopify app. Check its separate plan and integration requirements. ## Use native consent outside the CMS c15t's [framework components](/docs/frameworks) suit a product built with React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro or TanStack Start. The browser and headless options cover other JavaScript setups. Your account settings, embeds and consent dialog can use the same state. Use [headless APIs](/docs/frameworks/react/headless) when your product needs different markup. Complianz also has developer hooks and custom integration controls. c15t's advantage is a native application workflow and backend that can run independently of WordPress. This distinction matters for a headless CMS frontend or a product that spans different web frameworks. Plan the migration of service rules and records explicitly. ## Choose the right operational scope Complianz can be the better fit when a WordPress team wants consent, plugin detection and legal documents in its administration screen. Choose c15t when consent belongs inside custom product code and your team wants control of the engine and backend. Keep a separate process for site scans and legal documents. Check individual consent records separately from snapshots of a policy or configuration. Complianz [distinguishes Proof of Consent from Records of Consent](https://complianz.io/definition/what-is-proof-of-consent/). Check the evidence your deployment saves, not only its label. ## What c15t does not include * The packages do not include a WordPress setup wizard, plugin discovery or an automatic cookie scanner. * They do not generate privacy policies or include the wider WordPress legal-document suite. * Vendor controls need configuration. CMS plugins and tags already on the site need separate checks. * Browser state 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. Budget for setup and Inth or your own servers. Add separate scan and legal services where you need them. ## Test the frontend you run Use the [framework guide](/docs/frameworks) for your application. Register one analytics vendor and one embed from the site inventory. Test refusal, acceptance, reload and withdrawal. Follow the [verification guide](/docs/guides/verify-consent) to check requests and records. Check tags that the CMS adds too. Sources checked on 6 October 2026. This comparison separates platform scope from measured performance and legal compliance.