> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/kb/white-label-application/white-labelling.md). # White Labelling Present your own corporate branding by replacing the standard Xibo application, logo and splash screen White labelling services are available for both Cloud and self hosted solutions and can be applied to the Xibo CMS and Xibo Player applications. Pricing is a one time charge per brand with no limits, additional white label purchases can be made to cater for multiple branding requirements {% hint style="danger" %} White Labelling is currently not available for the Linux Player. {% endhint %} A white label for Xibo for Windows or the Xibo CMS does not change the license under which those products are licensed to you. You must retain the appropriate copyright notices and satisfy all the terms of the AGPLv3 license: [GNU Affero General Public License version 3 | Open Source Initiative](https://opensource.org/licenses/AGPL-3.0) A white label for Xibo for webOS, Xibo for Tizen or Xibo for Android is licensed to you under the general terms and conditions and the EULA - ## CMS White Label The CMS white label provided by Xibo Signage includes: * **Source** Code link on the login page * **About** Link pointing to the AGPLv3 licence * **Copyright and Licence** notices on the About Popup ### Remove Source and About links A white label can be generated for the CMS which removes the **Source** and **About** links from the login page and also alters the text that appears within the **About** page throughout the CMS. Removal of these items **does not** release the customer or end users from the terms of the [AGPLv3 licence](https://opensource.org/licenses/AGPL-3.0) and therefore the licence must be satisfied by the customer via alternative means. To enable this, the customer is required to open a [Ticket](https://account.xibosignage.com/my-account/tickets?open=true) with our helpdesk via **My Account** to request a document template for the **Alternative Provision of Licence** for you to complete which will explain how the licence terms will be met with the absence of those items. There are 3 main points to consider, this is not an exhaustive list and the AGPLv3 should be read and understood in full before submitting a request for these items to be removed: * The source code or offer of source code **must be distributed** to your users by another means. * The source code copyright and licence notifications **must not be modified** from their original appearance in the source code. * The licence **must be distributed** to your users by another means. {% hint style="warning" %} The options can only be enabled once we agree that the requirements are fully satisfied. {% endhint %} White Labels are purchased, from the **White Label** section of **My Account** {% hint style="warning" %} If you are purchasing a White Label to resell you need to be part of the Channel Partner Programme. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.xibosignage.com/kb/white-label-application/white-labelling.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.