Skip to main content
Access Dune’s blockchain data from your favorite BI tools and clients using the DuneSQL Trino/Presto connector. Connect Dune with popular tools like Hex, Metabase, DBeaver, and any Trino, Presto, or Starburst-compatible application for seamless data analysis.
Dune Trino Presto connector architecture diagram showing integration flowDune Trino Presto connector architecture diagram showing integration flow

Trino/Presto client → Dune connector → Dune Query Engine

The DuneSQL Trino Connector is currently only available to Plus and Enterprise customers.

Compatible Tools

Dune’s Trino connector supports any tool that works with Trino, Presto, or Starburst connectors. Popular Dune integrations include:
Any of the supported client applications listed in the Trino ecosystem are supported. Please visit their documentation to learn about their specific connection instructions, though the configuration should generally follow the same pattern using the connection parameters below.

Connection Parameters

Use these values in your Trino, Presto, or Starburst client configuration:
ParameterValueDescription
Hosttrino.api.dune.comDune’s Trino/Presto endpoint
Port443Standard HTTPS port
UsernameduneFixed username for all connections
Password<your-dune-api-key>Your Dune API key
Catalogdelta_prodMain data catalog
SSL/TLStrueAlways use encrypted connections
HTTP schemehttpsRequired for secure connections
If you need an API key, see our guide on Authentication. Remember to keep your API keys secret and rotate them immediately if they are ever exposed.

Supported SQL Operations

Queries executed via the connector align with what you can run on the Dune platform. See the Query Engine overview for more information on supported functions and syntax.

Rate Limits

Rate limits for the connector mirror those of the Dune Analytics API. Please refer to the Rate Limits documentation for details.

Billing & Cost

All queries run via the connector are executed on the Large Query Engine. Credits are consumed based on actual compute resources used. In addition, fetching results consumes credits proportional to the number of datapoints returned. For a full breakdown, please see our documentation on Billing.

Limitations

The connector currently has limited support for metadata discovery queries such as SHOW TABLES or SHOW SCHEMAS. This may impact the data source browsing and autocomplete experience within some BI tools. For schema and table discovery, see the Data Explorer guide. If you encounter timeouts with large result sets, consider paginating your queries using LIMIT and OFFSET, narrowing your filters, or splitting complex queries into smaller, more manageable parts.