# Relevance Tuning Toolbench Quepid now supports Elasticsearch **URL:** \ **Category:** Elastic Community and Ecosystem\ **Created:** [September 28, 2015, 2:50pm UTC](https://discuss.elastic.co/t/relevance-tuning-toolbench-quepid-now-supports-elasticsearch/31262 "2015-09-28T14:50:38Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![softwaredoug](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/softwaredoug/32/22681_2.png) [@softwaredoug](https://discuss.elastic.co/u/softwaredoug)\ **Post date:** [September 28, 2015, 2:50pm UTC](https://discuss.elastic.co/t/relevance-tuning-toolbench-quepid-now-supports-elasticsearch/31262/1 "2015-09-28T14:50:38Z")
Hello, Our product [Quepid](http://quepid.com) allows you tune relevance while immediately measuring the impact of your changes on 1000s of queries. Basically how it works is you point Quepid at your Elasticsearch instance. After adding queries, you write tests or make judgements on your ideal search results for those queries. As you modify your Query DSL to tune, you can see the impact immediately on your searches. We believe strongly in performing [test-driven relevance](http://opensourceconnections.com/blog/2013/10/14/what-is-test-driven-search-relevancy/) to measure the impact of any changes. We've been doing this with Solr for years, in Quepid, and we're happy to bring this product to the Elasticsearch crowd. More info in [this blog post](http://opensourceconnections.com/blog/2015/09/25/announcing-quepid-for-elasticsearch/). Feel free to [ping me](mailto:dturnbull@opensourceconnections.com) with any questions, complaints, or the like. ---
**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, 1:44pm UTC](https://discuss.elastic.co/t/relevance-tuning-toolbench-quepid-now-supports-elasticsearch/31262/2 "2017-07-06T13:44:59Z")