# White labeling Kibana **URL:** \ **Category:** Elasticsearch\ **Created:** [March 19, 2015, 1:09pm UTC](https://discuss.elastic.co/t/white-labeling-kibana/22761 "2015-03-19T13:09:59Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Jatinpreet\_Singh](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@Jatinpreet\_Singh](https://discuss.elastic.co/u/Jatinpreet_Singh)\ **Post date:** [March 19, 2015, 1:09pm UTC](https://discuss.elastic.co/t/white-labeling-kibana/22761/1 "2015-03-19T13:09:59Z")
Hi, I wish to use Elasticsearch and Kibana in a commercial product. I wish to understand the licensing concerns if I replace the Kibana logo by my own logo. Also, some text may be modified to suit my needs. Is it fine if I do this by giving proper attribution in source code and not on UI? Is it necessary to redistribute the code? If yes, is it only Kibana code or the whole application that it is integrated with? Thanks -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/2fe45703-5a22-4ef5-b6df-62f9def3409e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2fe45703-5a22-4ef5-b6df-62f9def3409e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 19, 2015, 4:55pm UTC](https://discuss.elastic.co/t/white-labeling-kibana/22761/2 "2015-03-19T16:55:32Z")
Elasticsearch uses the Apache 2 license - [http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0) The relevant part of that license says; _4. Redistribution_. You may reproduce and distribute copies of the Work or > Derivative Works thereof in any medium, with or without modifications, and > in Source or Object form, provided that You meet the following conditions: > > 1. You must give any other recipients of the Work or Derivative Works > a copy of this License; and > 2. You must cause any modified files to carry prominent notices > stating that You changed the files; and > 3. You must retain, in the Source form of any Derivative Works that > You distribute, all copyright, patent, trademark, and attribution notices > from the Source form of the Work, excluding those notices that do not > pertain to any part of the Derivative Works; and > 4. If the Work includes a "NOTICE" text file as part of its > distribution, then any Derivative Works that You distribute must include a > readable copy of the attribution notices contained within such NOTICE file, > excluding those notices that do not pertain to any part of the Derivative > Works, in at least one of the following places: within a NOTICE text file > distributed as part of the Derivative Works; within the Source form or > documentation, if provided along with the Derivative Works; or, within a > display generated by the Derivative Works, if and wherever such third-party > notices normally appear. The contents of the NOTICE file are for > informational purposes only and do not modify the License. You may add Your > own attribution notices within Derivative Works that You distribute, > alongside or as an addendum to the NOTICE text from the Work, provided that > such additional attribution notices cannot be construed as modifying the > License. > > You may add Your own copyright statement to Your modifications and may > provide additional or different license terms and conditions for use, > reproduction, or distribution of Your modifications, or for any such > Derivative Works as a whole, provided Your use, reproduction, and > distribution of the Work otherwise complies with the conditions stated in > this License. On 19 March 2015 at 06:09, Jatinpreet Singh [jatinpreet@gmail.com](mailto:jatinpreet@gmail.com) wrote: > Hi, > > I wish to use Elasticsearch and Kibana in a commercial product. > > I wish to understand the licensing concerns if I replace the Kibana logo > by my own logo. Also, some text may be modified to suit my needs. > > Is it fine if I do this by giving proper attribution in source code and > not on UI? > > Is it necessary to redistribute the code? If yes, is it only Kibana code > or the whole application that it is integrated with? > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/2fe45703-5a22-4ef5-b6df-62f9def3409e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2fe45703-5a22-4ef5-b6df-62f9def3409e%40googlegroups.com) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8b4tOsPN%3DfA5yvCDb6in5imzbgj%3Dt22xYbYwxn4AVq4A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8b4tOsPN%3DfA5yvCDb6in5imzbgj%3Dt22xYbYwxn4AVq4A%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jatinpreet\_Singh](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@Jatinpreet\_Singh](https://discuss.elastic.co/u/Jatinpreet_Singh)\ **Post date:** [March 19, 2015, 5:00pm UTC](https://discuss.elastic.co/t/white-labeling-kibana/22761/3 "2015-03-19T17:00:14Z")
Thanks for the reply. Going by the mentioned clauses it should be possible to white label the software because I would only need to specify the modification in source code only and not on the UI. I hope this makes sense. It would be great if someone can share their experience of doing the same. Thanks -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/64cad878-376d-4075-80d2-35e9bbfffeab%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/64cad878-376d-4075-80d2-35e9bbfffeab%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:25am UTC](https://discuss.elastic.co/t/white-labeling-kibana/22761/4 "2017-07-06T00:25:34Z")