Skip to main content

Whitelabeling Pro

Replace Coolify's brand identity with your own — name, logo, colors, URLs — so your customers see your brand, not Coolify's.

Pro Feature

Whitelabeling requires a Pro license. Upgrade to unlock.

Overview​

Whitelabeling lets you build a fully branded PaaS (Platform as a Service) on top of Coolify. Every instance of the Coolify name, logo, and URLs throughout the UI is replaced with your brand.

  • Build-time branding — name, logo, favicon, and sponsorship removal baked into the Docker image
  • Runtime overrides — URLs, colors, and metadata adjustable via Settings without rebuilding
  • Complete coverage — all 300+ views are branded in a single build step

Quick Start​

  1. Fork the repository
  2. Set GitHub Actions repository variables:
    • PAAS_BRAND_NAME = MyPaaS
    • PAAS_DOCS_URL = https://docs.mypaas.io
    • PAAS_WHITELABEL = true
  3. (Optional) Add brand assets to docker/brands/:
    • logo.svg — main product logo
    • favicon.svg — browser tab icon
    • og-image.png — social media preview
  4. Push to main — the CI workflow builds a fully branded image

Build-Time Configuration​

These settings are baked into the Docker image and cannot be changed at runtime:

VariableDefaultDescription
PAAS_WHITELABELfalseEnable whitelabeling
PAAS_BRAND_NAMECoolifyProduct name (replaced across all views)
PAAS_BRAND_DESCRIPTIONAn open-source...Product tagline
PAAS_HIDE_SPONSORSHIPfalseRemove sponsorship/donation UI elements
PAAS_HIDE_VERSION_LINKfalseRemove GitHub release links
PAAS_HIDE_ANALYTICStrueRemove Coolify Cloud analytics code

Runtime Configuration​

These settings can be changed via Settings > Branding without rebuilding:

VariableDefaultDescription
PAAS_DOCS_URLhttps://coolify.io/docsDocumentation base URL
PAAS_WEBSITE_URLhttps://coolify.ioMain website URL
PAAS_TWITTER_HANDLE@coolifyioTwitter/X handle
PAAS_OG_IMAGE(none)OpenGraph preview image URL
PAAS_BRAND_COLOR(none)Primary brand color (hex)

Runtime settings are resolved in order: Database value > Environment variable > Config default. This means you can set a default in your Docker build and override per-instance via the Settings UI.

Settings > Branding​

The Branding page (accessible to owners and admins) lets you adjust runtime settings:

  1. Navigate to Settings > Branding
  2. Update URLs, social handles, or brand color
  3. Click Save
  4. Changes take effect immediately for new page loads

Brand Assets​

Place brand assets in docker/brands/ in your repository:

FilePurpose
logo.svgMain product logo (appears in sidebar and login page)
favicon.svgBrowser tab icon
og-image.pngSocial media preview image (1200x630 recommended)

These files are copied into the Docker image during build and replace Coolify's default assets.

What Gets Branded​

The branding process replaces:

  • Product name — every mention of "Coolify" in the UI becomes your brand name
  • Page titles — browser tab titles use your brand name
  • Meta tags — OpenGraph and Twitter Card tags use your brand details
  • Footer text — copyright and product mentions
  • Documentation links — all "Docs" links point to your docs URL
  • Website links — all product website links point to your URL
  • Logo and favicon — replaced with your brand assets
  • Sponsorship UI — optionally removed
  • Analytics code — optionally removed
Functional Checks Preserved

The string "Coolify Cloud" is intentionally preserved in functional checks (e.g., config('app.name') == 'Coolify Cloud') to prevent breaking cloud-specific features. Only display text is replaced.

Troubleshooting​

Brand name not appearing​

  1. Verify PAAS_WHITELABEL=true is set as a build argument
  2. Rebuild the Docker image — build-time settings require a new image
  3. Check that the CI workflow completed successfully

Runtime settings not taking effect​

  1. Hard-refresh the page (Ctrl+Shift+R) to clear browser cache
  2. Verify settings were saved in Settings > Branding
  3. Runtime settings apply to overlay views immediately; some views may require a page reload

Special characters in brand name​

Brand names with special characters (e.g., Brand & Co) are handled automatically during the build process. No escaping is needed in the configuration variables.