Skip to content
These docs are a preview of Self-Managed Kindo 2026.11, an upcoming release.

Brand Kindo as your own

Set your own app name, logo, favicon, footer disclaimer, and policy URLs for Self-Managed Kindo. Set defaults for the whole instance, and use a feature flag for per-organization changes.

Branding uses the first available value in this order:

  1. The JSON value set for the organization.
  2. The environment-variable default for that field.
  3. The built-in Kindo default for an optional field without an environment-variable value.

Omit a field to inherit its environment-variable default. The app name also changes the API documentation titles; the other fields affect only the Kindo web app.

Every field has a Kindo default, so branding is optional. Set the values below to rebrand.

Environment variableApplicationSet to rebrandPurpose
NEXT_PUBLIC_DEFAULT_APP_NAMEnextYesProduct name in the web app
NEXT_PUBLIC_DEFAULT_LOGO_URLnextYesHTTPS URL to the logo image
NEXT_PUBLIC_DEFAULT_FAVICON_URLnextYesHTTPS URL to the favicon
NEXT_PUBLIC_DEFAULT_PRIVACY_URLnextYesHTTPS URL to the privacy policy
NEXT_PUBLIC_DEFAULT_TERMS_OF_USE_URLnextYesHTTPS URL to the terms of use
NEXT_PUBLIC_DEFAULT_TERMS_OF_SERVICE_URLnextYesHTTPS URL to the terms of service
NEXT_PUBLIC_DEFAULT_MARKETING_WEBSITE_CONTACT_URLnextYesHTTPS URL for the “Contact us” link
NEXT_PUBLIC_DEFAULT_PUBLIC_DOCS_URLnextNoHTTPS URL to your Kindo Docs site
NEXT_PUBLIC_DEFAULT_DISCLAIMERnextNoFooter disclaimer text
NEXT_PUBLIC_DEFAULT_DISCLAIMER_POLICY_URLnextNoHTTPS URL linked from the disclaimer
DEFAULT_APP_NAMEapi, task-worker-tsYesProduct name in API documentation and server-rendered text
DEFAULT_PUBLIC_DOCS_URLtask-worker-tsNoBase URL for Kindo Docs search results

Configured URL fields must use HTTPS.

To set the defaults for the whole instance, set each value for the application the table names, then apply:

Terminal window
kindo config set overrides.serviceEnv.next.NEXT_PUBLIC_DEFAULT_APP_NAME="Acme AI"
kindo config set overrides.serviceEnv.next.NEXT_PUBLIC_DEFAULT_LOGO_URL=https://cdn.acme.example.com/logo.svg
kindo config set overrides.serviceEnv.api.DEFAULT_APP_NAME="Acme AI"
kindo config set overrides.serviceEnv.task-worker-ts.DEFAULT_APP_NAME="Acme AI"

Apply the change:

Terminal window
kindo config apply

Kindo Docs search is off until all of these are true:

RequirementName
The Kindo Docs search flag is on.KINDO_DOCS_SEARCH
The docs URL, empty by default, points to a Kindo Docs site for the same version as your instance.DEFAULT_PUBLIC_DOCS_URL
The requesting organization has no enabled branding flag. Enabling it for an organization turns off Kindo Docs search for that organization, even when its JSON value sets a docs URL or is invalid.CUSTOM_WHITELABEL, publicDocsUrl

Use a JSON value to override fields for an organization. All fields are optional; omitted fields inherit the environment-variable defaults.

FieldTypePurpose
appNamestringProduct name in the web app, API documentation, and server-rendered titles
logoUrlHTTPS URLTop navigation and login logo
faviconUrlHTTPS URLBrowser tab favicon
disclaimerstringFooter disclaimer text
disclaimerPolicyUrlHTTPS URLLink from the disclaimer
privacyUrlHTTPS URLPrivacy policy link
termsOfUseUrlHTTPS URLTerms of use link
termsOfServiceUrlHTTPS URLTerms of service link
marketingWebsiteContactUrlHTTPS URL”Contact us” link
publicDocsUrlHTTPS URLPublic docs link

An invalid value, such as malformed JSON, a non-HTTPS URL, or a wrong type, produces a warning in the logs. Branding falls back to the environment-variable defaults for the whole value.

{
"appName": "Acme AI",
"logoUrl": "https://cdn.acme.example.com/branding/logo.svg",
"faviconUrl": "https://cdn.acme.example.com/branding/favicon.png",
"disclaimer": "Acme AI is for internal use only. Do not paste customer PII.",
"disclaimerPolicyUrl": "https://acme.example.com/legal/ai-policy",
"privacyUrl": "https://acme.example.com/legal/privacy",
"termsOfUseUrl": "https://acme.example.com/legal/terms",
"termsOfServiceUrl": "https://acme.example.com/legal/tos",
"marketingWebsiteContactUrl": "https://acme.example.com/contact",
"publicDocsUrl": "https://docs.acme.example.com"
}

This applies once Kindo’s applications read their flags from Flagsmith.

  1. Sign in to Flagsmith and open the project and environment your instance uses.

  2. Open the CUSTOM_WHITELABEL feature. Flagsmith may list it in lowercase. Create it if it is missing. Leave it off for the environment, so organizations without an override keep the environment-variable defaults.

  3. Create a segment for the organization, named after it. Add one rule: the trait orgId equals the organization’s ID.

  4. Add a segment override for that segment on the feature. Turn it on and paste the JSON from the example above into its Value field.

  5. Verify the branding. Sign in to Kindo as a user of the organization. Check the app name, logo, favicon, and disclaimer. Sign in as a user of another organization and confirm the environment-variable defaults still apply there.

To brand another organization, create another segment and override with its own JSON.

SymptomLikely causeFix
Branding shows Kindo defaults even with the flag enabledBranding defaults are unset and the JSON value does not supply themSet and apply the values using the config settings above
Logo or favicon does not loadAsset URL uses http://Re-host the asset over HTTPS
Flag value is ignoredInvalid JSON, URL, or field typeIn the browser developer console, look for Feature flag CUSTOM_WHITELABEL JSON failed to parse; in the api and task-worker-ts pod logs, look for Failed to parse feature flag JSON
Wrong organization sees the brandingThe feature is on for the whole environment, or the segment’s orgId rule is wrongTurn the feature off for the environment, keep it on only in the segment override, and check the rule’s orgId
Branding flickers between defaults and the overrideBranding can take a short time to appear after a JSON value changeWait briefly and check again