# Launch video: keep the Elasticsearch client, change the engine

Here is the short launch video for Qdrant ES Gateway:

<video controls preload="metadata" poster="https://dstockton.github.io/qdrant-es-gateway/assets/qdrant-es-gateway-launch.jpg" width="960">
  <source src="https://dstockton.github.io/qdrant-es-gateway/assets/qdrant-es-gateway-launch.mp4" type="video/mp4">
  Your browser does not support embedded video. [Download the MP4](https://dstockton.github.io/qdrant-es-gateway/assets/qdrant-es-gateway-launch.mp4).
</video>

The story is simple: an existing application keeps its Elasticsearch-shaped client requests, while the gateway translates the supported application-search subset to the Qdrant engine. The video compares compatibility, retrieval, mixed workloads, memory, and the supported feature boundary.

See the [compatibility matrix](https://dstockton.github.io/qdrant-es-gateway/compatibility/) and [production notes](https://dstockton.github.io/qdrant-es-gateway/production/) for the detail behind the demo.