Custom Domains & Sandboxes¶

Kiket can run behind any domain — production, staging, or isolated sandboxes — without editing source code. Set the following environment variables (or Cloud Build substitutions) before deploying:

Variable	Description	Default
`KIKET_BASE_DOMAIN`	Canonical domain for the workspace	`kiket.dev`
`APP_HOST`	Hostname that serves the web app	`KIKET_BASE_DOMAIN`
`DOCS_HOST`	Documentation hostname	`docs.${KIKET_BASE_DOMAIN}`
`STATUS_HOST`	Status page hostname	`status.${KIKET_BASE_DOMAIN}`

Cloud Build / Cloud Run¶

Example deployment snippet:

substitutions:
  _BASE_DOMAIN: sandbox.acme.dev
  _APP_HOST: sandbox.acme.dev
  _DOCS_HOST: docs.sandbox.acme.dev
  _STATUS_HOST: status.sandbox.acme.dev

steps:
  - name: gcr.io/google.com/cloudsdktool/cloud-sdk
    args:
      - run
      - deploy
      - kiket
      - --set-env-vars=KIKET_BASE_DOMAIN=${_BASE_DOMAIN},APP_HOST=${_APP_HOST},DOCS_HOST=${_DOCS_HOST},STATUS_HOST=${_STATUS_HOST}

PlatformHost (built into the app) uses these values for URLs, email links, telemetry, and Action Cable host allow-lists.

Terraform & Cloudflare¶

Provide the same domains to Terraform (domain_name, docs_domain_name, status_domain_name) so Cloudflare DNS and HTTPS bindings match your deployment. When creating sandboxes, generate a dedicated tfvars file per tenant and run terraform apply with those values.

CLI / SDKs¶

Set KIKET_API_URL (CLI) or KIKET_BASE_URL (SDKs) to point at the sandbox host. When the platform is deployed with the environment variables above, the command palette, workflows, and extensions automatically reference the correct URLs.