Skip to main content

Backend

Backend overview

Start with Inth

Inth is the recommended backend for c15t applications. Use the endpoint supplied by your project in the framework quickstart. You get a backend connection without running the SQL service described in these guides.

Self-hosting runs @c15t/backend in your own server, and your app connects to it with the same hosted mode it would use for Inth. Choose it when you need to operate the service yourself. You own database provisioning, migrations, backups, policy configuration, signing secrets, availability and upgrades.

What the backend provides

CapabilityHow clients use it
Reusable configuration/manifest publishes policy rules, translation configuration and IAB metadata for caching and local resolution.
Request initialization/init resolves the policy for a request's location, language and privacy signals.
Consent persistenceSubject endpoints record confirmed category receipts and retrieve current choices.
Identity linksPATCH /subjects/:id links a device subject to an external identity, such as a signed-in account.
Legal-document versionsAn authenticated release endpoint stores the current document identity. Exported helpers sign and verify document snapshots.

For Next.js request rendering, prefer the cached manifest path described in data fetching. A browser-only application can use regular initialization. A static frontend can use either Inth or a separately deployed self-hosted backend; static hosting does not require offline mode.

What offline mode changes

offline() resolves policy in the browser and keeps choices in browser storage. It never calls a backend, so no consent records exist and policy lives in your code. Use it for local development and tests. Not recommended for production environments. See choose your setup.

Operate your own backend

Start with the self-hosted quickstart, then review database setup and configuration. Use HTTP endpoints to integrate a custom server client, and policy configuration when you own the policy manifest.