# 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:** 1\ **Showing post:** 2
**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… --- _[View the full topic](https://discuss.elastic.co/t/free-libre-open-source-floss-and-elastic/117247)._