> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/build/stage-2-productize/connect-to-engine/trino.md).

# Trino

Trino is a distributed SQL query engine for analytics across data lakes, databases, and object storage. Vulcan connects to Trino with the `trino` engine adapter.

There are two ways to think about Trino connectivity in Vulcan.

| Path                                                                                  | Use when                                                                                               |
| ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| [External Trino](/build/stage-2-productize/connect-to-engine/trino/external-trino.md) | You already have a Trino-compatible endpoint, such as DataOS Minerva, Starburst, or self-hosted Trino. |
| [Managed Trino](/build/stage-2-productize/connect-to-engine/trino/managed-trino.md)   | The Trino cluster is attached to, or managed with, your data product deployment.                       |

***

## Common rules

* Use `type: trino` in the gateway connection.
* Use `dialect: trino` in `modelDefaults`.
* Use `vde: false`; Trino does not support `vde: true`.
* Store passwords and tokens in environment variables while working locally, and use DataOS secrets when deploying to an environment.
* Choose the guide based on who owns the Trino cluster.

***

## Which guide should I use?

Use [External Trino](/build/stage-2-productize/connect-to-engine/trino/external-trino.md) if the Trino cluster already exists and Vulcan only needs to connect to it. This is the right guide for Minerva, Starburst, and self-hosted Trino.

Use [Managed Trino](/build/stage-2-productize/connect-to-engine/trino/managed-trino.md) if the Trino cluster should be part of the data product deployment itself.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/build/stage-2-productize/connect-to-engine/trino.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.