# Free/Libre Open-Source (FLOSS) and Elastic **URL:** \ **Category:** Elasticsearch\ **Created:** [January 26, 2018, 6:04pm UTC](https://discuss.elastic.co/t/free-libre-open-source-floss-and-elastic/117247 "2018-01-26T18:04:43Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![chlarsen](https://avatars.discourse-cdn.com/v4/letter/c/9e8a1a/32.png) [@chlarsen](https://discuss.elastic.co/u/chlarsen)\ **Post date:** [January 26, 2018, 6:04pm UTC](https://discuss.elastic.co/t/free-libre-open-source-floss-and-elastic/117247/1 "2018-01-26T18:04:44Z")
Dear All, I have been monitoring, if that is the right expression, Elastic's core component, i.e. LogStash, Elasticsearch and Kibana for a number of years now, and have started using them more intensively recently. While in the old days, there were separate plugins that were not freely available, but could quite easily be replaced by FLOSS alternatives, things have become a bit less clear with the arrival of the Kibana X-Pack. While version 5.3 offers a trial for the X-Pack's monitoring functionality, only, with subsequent versions there seems to be an explosion of locked (trial) features. I need clarity here, as the intended implementation has FLOSS as a precondition, and any drift from FLOSS to dual licensing with an increasing limited set of features will be unacceptable. Rather disconcertingly, I noted a similar trend with Kibi, which is trial only, for up-to-date releases, after several years of promoting itself as a FLOSS and friendly fork of Kibana. Maybe there is someone out there to enlighten me, as a durable, robust and consistently free/libre licensing and development approach will be of paramount importance for the next steps from my end. Your kind assistance is highly appreciated! Chris ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [January 26, 2018, 8:05pm UTC](https://discuss.elastic.co/t/free-libre-open-source-floss-and-elastic/117247/2 "2018-01-26T20:05:09Z")
I do not have answers, but there was an interesting exchange on the subject a couple of months ago: > [@Conflict of interest between open source Elasticsearch and closed source Swifttype?](https://discuss.elastic.co/t/conflict-of-interest-between-open-source-elasticsearch-and-closed-source-swifttype/107063): > > First congrats on the [acquisition](https://www.elastic.co/blog/swiftype-joins-forces-with-elastic?blade=tw&hulk=social)! Second, I wonder how this will work in practice? Are there conflicts of interest? Could such conflicts of interest threaten the health of the Elasticsearch project? Imagine a search feature. If I put my open source hat on, I want that search feature to be as usable as possible in the open source Elasticsearch. I want to advocate for usability -- better than the proprietary options! For example, I'm personally passionate about building more in the Elasticsearc… ---
**Author:** ![chlarsen](https://avatars.discourse-cdn.com/v4/letter/c/9e8a1a/32.png) [@chlarsen](https://discuss.elastic.co/u/chlarsen)\ **Post date:** [January 26, 2018, 8:27pm UTC](https://discuss.elastic.co/t/free-libre-open-source-floss-and-elastic/117247/3 "2018-01-26T20:27:05Z")
Thank you, Ivan, this pretty much reflects my concerns. I am very actively looking into Grafana as replacement for Kibana, as I am very concerned about the creep towards closed source. I trust that Elasticsearch is important enough to the Community at large that any similar developments there my trigger a "LibreOffice/MariaDB/..." event - I hope this is not just wishful thinking. Have a great weekend! Chris ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 23, 2018, 8:27pm UTC](https://discuss.elastic.co/t/free-libre-open-source-floss-and-elastic/117247/4 "2018-02-23T20:27:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.