Map Federated Starburst and Trino Catalogs Visually

Starburst and Trino answer SQL by federating it across Hive metastores, Apache Iceberg tables, relational databases, and object storage. DbSchema connects to the coordinator and turns those catalogs into ER diagrams, visual queries, and shareable documentation.

Catalog-level schemas from Hive, Iceberg, and JDBC sources on one diagram
Join across catalogs visually — skip hand-typing three-part identifiers
Sample table contents without switching to the Trino CLI
Publish the federated data model as browsable documentation

available for

ISO-27001 certified

Free Community Edition No signup required 15-day Architect trial included

Free Download

DbSchema mapping Starburst and Trino catalogs as ER diagrams

Trusted by teams at

One SQL Endpoint
Five Systems Behind It

Federation is the point of Trino: a single query joins a Hive table to an Iceberg table to a row in a relational store. It is also the problem — the complete data model exists in no single source system, only in the union of catalogs.

DbSchema renders each catalog's schemas as ER diagrams on one canvas, so cross-catalog relationships stop living only in the heads of the engineers who wrote the queries.

See, Join & Sample
Across Every Catalog

Desktop tooling for the federated layer.

Render Trino catalog schemas as ER diagrams

Catalogs Become Diagrams

Connect to the coordinator and browse catalog-level schemas as ER diagrams — Hive, Iceberg, and JDBC-connected sources rendered side by side.

Build cross-catalog Trino queries visually

Cross-Catalog Joins, Visually

Drag tables from different catalogs into the query builder; DbSchema writes the fully qualified Trino SQL, and you read it before it runs on the cluster.

Write Trino SQL from the DbSchema desktop editor

Trino SQL from the Desktop

Write and execute statements against the coordinator with schema-aware autocomplete, then export result sets to CSV, Excel, or JSON.

Governance Wants the Model
Not a Grant on the Cluster

Turn catalog metadata into interactive HTML5 documentation of the federated data model — searchable diagrams, table and column details, hover comments. New hires and governance reviewers study the data landscape from a link, with zero access to the coordinator itself.

Explore the Documentation Tool

HTML5 documentation of a Starburst and Trino federated data model

Starburst and Trino Connections — Driver, URL, Auth

Download the Trino JDBC driver (trino-jdbc-*.jar) from trino.io and register it in DbSchema's driver manager. Open-source Trino takes a URL of the form jdbc:trino://host:8080/catalog/schema; Starburst Enterprise uses jdbc:trino://host:8080 with the catalog and schema chosen separately in DbSchema's connection dialog.

Deployments secured with Kerberos or LDAP take their authentication properties in the advanced connection panel. More on the Starburst JDBC driver page.