Skip to main content

Inth vs Didomi

Didomi runs consent as a hosted platform built around proofs, reports and APIs. Inth Consent runs it inside your application through c15t, with the records hosted for you. Which one fits depends on what your team wants to own.

Ask your coding agent
Audit this codebase for Didomi and estimate a move to Inth Consent, built on c15t. Find the Didomi setup and any Consent Mode and tag manager wiring, list every analytics, advertising and chat tag, then report what c15t would replace, which consent category each tag needs, and what the page would stop loading before consent. Use https://c15t.com/docs/comparisons/didomi and https://c15t.com/docs/integrations/overview.
Talk to Inth
Trusted by
  • Expo
  • Zed
  • Infisical
  • Unkey
  • Chelsea Piers
  • Mario Testino
  • Roboto Studio
  • Cal.com
  • Mastra

Which platform fits your team?

Tick the needs that matter to your team and see which platform meets more of them.

What matters to your team?

Inth Consent

Built for teams that own consent in their application.

5of 6 needs· Closer fit

Didomi

Built for hosted proofs, reports and consent workflows.

3of 6 needs

  • Consent state in your React and Next.js code

    Inth Consent, Fits: Inth Consent · c15t packages expose consent state to your components and your server

    Didomi, Not the focus: Didomi · Hosted platform APIs and snippets

  • CookieBench score above 90

    Inth Consent, Fits: Inth Consent · Score 95 on the CookieBench c15t examples

    Didomi, Not the focus: Didomi · Score 71; banner visibility could not be detected in the test

  • Hosted consent records

    Inth Consent, Fits: Inth Consent · Every saved choice, region and policy version in your Inth dashboard

    Didomi, Fits: Didomi · Consent proofs, versions and reports

  • Google Consent Mode v2

    Inth Consent, Fits: Inth Consent · Denied defaults and consent updates through the Google integrations

    Didomi, Fits: Didomi · Google Consent Mode support

  • Central CMP administration

    Inth Consent, Not the focus: Inth Consent · Consent dashboard and hosted records; vendor lists and banner copy ship with your releases

    Didomi, Fits: Didomi · Hosted proofs, reports and platform workflows

  • Consent state in server rendering

    Inth Consent, Fits: Inth Consent · Available through the c15t framework packages

    Didomi, Not the focus: Didomi · Usually outside your app’s server render

Keep every tag you already run.

Inth Consent runs on c15t, which ships helpers for the analytics, advertising, chat and tag-manager tools you use today. Each one loads only when its consent category is granted, so consent is enforced in your implementation rather than by a script bolted on top.

Your privacy choices

Choose which optional cookies this example site can use.

Tag managersdenied defaults

  • Google Tag Manager: denied defaults

Analyticsblocked

  • Google Analytics 4: blocked
  • Ahrefs: blocked
  • Adobe Analytics: blocked
  • Amplitude: blocked
  • Cloudflare: blocked
  • Microsoft Clarity: blocked
  • Databuddy: blocked
  • Rybbit: blocked
  • Fathom: blocked
  • Heap: blocked
  • Mixpanel: blocked
  • Hotjar: blocked
  • Hightouch: blocked
  • LogRocket: blocked
  • Matomo: blocked
  • PostHog: blocked
  • Promptwatch: blocked
  • Pirsch: blocked
  • RudderStack: blocked
  • Segment: blocked
  • Plausible: blocked
  • Umami: blocked
  • Vercel Analytics: blocked

Functionalblocked

  • Crisp: blocked
  • Intercom: blocked
  • Google Maps: blocked
  • YouTube: blocked

Ads & pixelsblocked

  • Google Ads: blocked
  • Meta Pixel: blocked
  • TikTok Pixel: blocked
  • LinkedIn Insight Tag: blocked
  • Snapchat Pixel: blocked
  • Reddit Pixel: blocked
  • X Pixel: blocked
  • Microsoft UET: blocked
  • Clearbit: blocked

Consent belongs in your implementation plan

You wire consent into the app once. After that it ships with your releases.

Install c15t, tell it which category each tag belongs to, and point it at your hosted project. That is the setup. With Didomi the same work lives in a dashboard and a script tag, which is fine until a developer needs to know, in code, whether marketing consent was given. Either way, test it: accept, reject, change your mind, and check what actually loads.

Inth Consent

See consent in your dashboard.

Every saved choice, region and policy version in one place, so you can answer a regulator or a customer without exporting anything.

How Inth Consent and Didomi compare

Two ways to run website consent: application-owned packages, or a hosted consent platform.

Website consent comparison: Inth Consent and Didomi
Primary shapeDeveloper-first consent platformHosted consent platform
Control modelOpen-source packages plus a hosted or self-hosted backendSaaS dashboard and APIs
Benchmark snapshotScore 95; 89 ms in the c15t Next.js example; 0 KB network impactScore 71; banner visibility not detected; 395 KB network impact

Compare the total consent cost

Drag the slider to your monthly sessions. Inth Consent picks the cheapest published plan and adds usage at the published rate. Didomi prices through a sales conversation.

1,000

Inth Consent

$0/ mo

Cheapest published plan

Free · within included usage

Free
$0
Starter
$20
Pro
$50

Didomi

Quote-based

≈ 33

sessions a day

Pricing

Pricing you can read before you call

Every plan runs the full Inth Consent infrastructure. Go beyond included usage for $0.001 per request, or request a custom plan.

Free

For developers evaluating or shipping internal tools.

$0/ mo
  • 1 project
  • 5,000 sessions & consent saves /mo
  • All paid features on dev instances
  • Production with usage billing
  • Community + docs support

Starter

Most popular

For small sites moving consent into their application.

$20/ mo
  • Everything in Free
  • 2 projects
  • 25,000 sessions & consent saves /mo
  • Production instances included
  • Policy packs included

Pro

For growing businesses and agencies managing many sites.

$50/ mo
  • Everything in Starter
  • Unlimited projects
  • 100,000 sessions & consent saves /mo
  • Policy packs included
  • Chat support

Need enterprise capacity?

Custom usage, advanced SDKs, APIs, integrations, implementation guidance and priority support with a dedicated Slack channel.

Contact sales

Moving from Didomi?

Bring your current setup, renewal date and quote. We’ll map the switch with you. If you want a head start, have your coding agent draft the plan.

Plan it with your coding agent
Plan a migration from Didomi to Inth Consent, built on c15t, for this codebase. Find the Didomi setup and Consent Mode wiring, map every tag to a c15t integration and consent category, propose how to run c15t on a staging route while Didomi stays live, and list what to verify before cutting over. Use https://c15t.com/docs/comparisons/didomi and https://c15t.com/docs/integrations/overview.
Talk to Inth

Inth vs Didomi: common questions

Scope, consent architecture and evaluation.

Both approaches support consent-aware Google integrations. Review category mappings, denied defaults and updates, then verify actual tag behaviour after each visitor choice.