---
title: c15t vs Ethyca
description: Choose c15t for native web consent components and a deployable
  backend. Compare Ethyca's Fides code and Janus platform without confusing
  their scope.
group: reference
lastModified: "2026-10-12T12:44:54+01:00"
lastAuthor: Christopher Burns
---
## Choose c15t for consent that fits your web product

c15t is the stronger fit when your team needs consent components, vendor choices and backend records inside a web product. You can build the interface in your framework and review its behaviour with the application.

Ethyca addresses a wider set of privacy and data governance tasks. Its current Janus product offers consent APIs across web, mobile and backend systems.

Ethyca also publishes Fides source code. This comparison distinguishes that code from current commercial products and services.

## 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|Ethyca|
|--|--|--|
|Build consent into a web product|Native components across the supported web frameworks|Janus offers headless APIs and SDKs|
|Build a custom interface|Themes, component parts and headless APIs|Custom applications through Janus APIs. Fides includes a Privacy Center|
|Inspect source code|Apache-2.0 client and backend source|Fides source is Apache-2.0. Check commercial product scope separately|
|Operate the backend yourself|Supplied c15t service with your own database|Fides documents local deployment. Ethyca archived its public repository|
|Control application vendors|Category and vendor rules for registered scripts, requests and embeds|Janus describes consent enforcement across connected systems|
|Carry choices across devices and systems|Application and backend integration required|Janus describes persistent consent state across devices and downstream services|
|Fulfil data-subject requests|**No bundled case management or fulfilment suite**|Fides includes request workflows. Ethyca also offers automated DSR products|
|Discover data and assess risks|**Not included in the c15t packages**|Broader Ethyca governance products|

Sources: [Janus consent product](https://www.ethyca.com/janus), [Fides repository](https://github.com/ethyca/fides), [Ethyca open source](https://www.ethyca.com/open-source) and [Ethyca platform](https://www.ethyca.com/).

## Give your product team one consent workflow

c15t connects the banner, privacy settings and vendor integrations through application state. Your team can change them in the same release.

Use [native framework components](/docs/frameworks) or build the interface through [headless APIs](/docs/frameworks/react/headless). The guides cover React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro, TanStack Start and plain websites.

The [vendor controls](/docs/frameworks/react/vendor-consent) let a visitor refuse one named vendor within an accepted category. Registered scripts, requests and embeds can respect that choice.

For Next.js, choose the [consent response path](/docs/frameworks/next/rendering). The App Router's default streamed path shows the page first and does not include the banner in initial HTML.

Ethyca also supports headless consent. Choose c15t for its documented web component workflow and the backend that accompanies it.

## Compare the actual deployment options

Both c15t and Fides publish source code. Open source alone is not a reason to claim that only c15t offers control.

Ethyca archived the public Fides repository on 28 August 2026. Its README still describes local deployment and privacy request workflows.

That status does not establish the support terms or release process for commercial Janus. Confirm those separately before you choose a Fides deployment.

Evaluate the required integrations and operational work before production use.

## What c15t does not include

c15t does not replace Ethyca's wider governance products. The packages do not include enterprise data discovery, risk assessments or automated data-subject request fulfilment.

c15t also does not supply an equivalent native mobile SDK suite or automatic consent propagation across an enterprise's complete data estate.

Your team must configure the application integrations. A banner does not automatically stop every tracker already on the site, and withdrawal cannot erase data already sent elsewhere.

The software has no licence fee. Hosting, maintenance and implementation still cost money.

## Try the difference in your application

1. Start with [Inth and your framework guide](/docs/frameworks).
2. Add a consent control to a product screen.
3. Register a vendor and test a refusal inside an accepted category.
4. Inspect the requests, interface and backend record.
5. List any wider governance workflows that still need a separate system.

Follow the [verification guide](/docs/guides/verify-consent). Choose c15t when the web consent workflow is the main requirement.

Sources checked on 6 October 2026. We did not benchmark either product or check commercial deployment terms. Archived Fides source is not evidence of every current Janus capability.