Docs
Sign in
Reference

Hosted Backend

In hosted mode, c15t clients call your project's consent backend URL. Many apps use an application-local proxy such as /api/c15t so application code stays stable across environments.

Responsibilities

The hosted backend handles:

  • initialization data for the client
  • location and jurisdiction context
  • policy-pack resolution
  • translations and UI configuration
  • consent writes and sync
  • server-side consent awareness

Origins

Each consent project has trusted origins. The hosted runtime checks the request origin before serving browser consent requests. Add every production, preview, and local origin that should be allowed to call the project.

Operational checks

Use the dashboard and consent records to confirm that requests reach the expected project, policies resolve as expected, and trusted origins are configured correctly.

Keep the backend URL configurable

Application code should depend on the c15t client contract and keep the backend URL configurable across local, preview, staging, and production environments.