# Query engines

Use federated query engines when Pinot is one source in a broader SQL stack and you want to join or compare it with other systems. These integrations are the right fit when a data platform already standardizes on Trino for interactive analytics.

## What belongs here

| Engine | Best for                                               | Notes                                                                                                  |
| ------ | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------ |
| Trino  | Interactive federated SQL across multiple data sources | The current guide covers Kubernetes deployment, Pinot catalog configuration, and CLI-based validation. |

{% hint style="info" %}
**Presto support removed**: The Pinot Presto connector, Docker images, and Helm chart have been removed as of [apache/pinot#17947](https://github.com/apache/pinot/pull/17947). Trino (the Presto successor) is the recommended query engine for federated SQL over Pinot.
{% endhint %}

## Detailed docs

* [Trino](https://docs.pinot.apache.org/build-with-pinot/connectors-clients-apis/query-engines/trino)
* [Query engines on Kubernetes](https://docs.pinot.apache.org/build-with-pinot/connectors-clients-apis/query-engines/query-engines-kubernetes)

## What this page covered

This page covered the federated SQL engine most commonly used to query Pinot alongside other systems.

## Next step

Use the linked Trino guide, then verify the catalog configuration with a small query before rolling it into production.

## Related pages

* [BI tools](https://docs.pinot.apache.org/build-with-pinot/connectors-clients-apis/bi-tools)
* [REST / gRPC APIs](https://docs.pinot.apache.org/build-with-pinot/connectors-clients-apis/rest-grpc-apis)
* [Querying Pinot](https://docs.pinot.apache.org/build-with-pinot/querying-and-sql/querying-pinot)