Free
For developers evaluating or shipping internal tools.
- 1 project
- 5,000 sessions & consent saves /mo
- All paid features on dev instances
- Production with usage billing
- Community + docs support
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.
Privacy settings
Choose which cookies and tracking technologies this site may use.
Your privacy choices
Choose how this site uses cookies. You can accept, reject, or customise optional analytics and marketing.
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
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.
Choose which optional cookies this example site can use.
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.
Two ways to run website consent: application-owned packages, or a hosted consent platform.
| Requirement | Inth Consent | Didomi |
|---|---|---|
| Primary shape | Developer-first consent platform | Hosted consent platform |
| Control model | Open-source packages plus a hosted or self-hosted backend | SaaS dashboard and APIs |
| Benchmark snapshot | Score 95; 89 ms in the c15t Next.js example; 0 KB network impact | Score 71; banner visibility not detected; 395 KB network impact |
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.
Inth Consent
$0/ mo
Cheapest published plan
Free · within included usage
Didomi
Quote-based
≈ 33
sessions a day
Every plan runs the full Inth Consent infrastructure. Go beyond included usage for $0.001 per request, or request a custom plan.
For developers evaluating or shipping internal tools.
For small sites moving consent into their application.
For growing businesses and agencies managing many sites.
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.