Skip to main content

c15t vs Complianz

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.

Get started

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.

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

Compare what you get.

What you needc15tComplianz
Build a custom web applicationNative adapters for the documented web frameworksNative WordPress plugin and separate Shopify app
Create your own interfaceThemes, component parts and headless APIsWordPress banner settings, custom CSS and HTML templates
Control servicesDeclared categories and vendors for scripts, requests and embedsWordPress Script Center, service choices and content placeholders
Choose the record serviceInth hosts the backend and stores records in its database. Self-hosting is optionalWordPress Premium includes Records of Consent
Discover cookiesNo automatic scanner in the packagesWordPress cookie scan and service detection
Generate legal documentsNot includedWordPress legal-document tools, with plan-dependent scope
Test banner designsPresentation and theme experiments with fixed policy and policy textWordPress Premium lists A/B tests
Configure CMS pluginsDeveloper setup in your applicationWordPress plugin and service 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 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 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.

Moving off Complianz 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 42 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