Trino / Starburst + Querri
Querri reads tables and views from a catalog on your Trino or Starburst cluster and copies them into its Library, next to your other systems, for questions, dashboards and reports.
Querri only reads from Trino / Starburst and never changes your records. SOC 2 Type II, HIPAA and ISO 27001:2022 certified, and your data is never used to train a model.
What you can answer
Trino answers SQL clients, not the AI assistants people already have open. Querri makes the synced copy available to Claude, ChatGPT and other MCP clients, with the same row-level access as inside Querri.
Claude, ChatGPT & moreTables behind different Trino catalogs often key the same customer differently, which breaks the join. Querri's data cleansing standardizes those columns on the synced copy before you combine them.
Data cleansingA query in a SQL editor is easy to lose once the tab closes. A Querri project keeps the questions, steps and results together, so the team can rerun and extend the analysis on fresh syncs.
ProjectsWhat comes over
Querri copies this data into your Library on a schedule, next to every other system you connect, so one question can draw on all of it.
After the first load, each scheduled sync brings in only rows that are new or changed since the last one.
Querri reads from Trino / Starburst and never creates, edits or deletes anything there. Every answer runs on Querri's own copy.
Querri's own sharing and row-level access decide who sees which rows, in chat, dashboards, Claude, ChatGPT and the API.
How to connect
Say "connect Trino / Starburst" or pick it from the connector catalog.
Enter the coordinator host, port, user and catalog in the secure form, plus either a password for LDAP authentication or a JWT access token, not both. Passwords work over HTTPS only.
Pick the data you want and how often it refreshes, then approve the first load.
The data lands in your Library, ready for chat, dashboards and scheduled reports.
FAQ
Enter the coordinator's host, the port (443 for Starburst Galaxy, often 8080 for plain HTTP), your user and the catalog. Authenticate with a password for LDAP, which needs HTTPS, or with a JWT access token. Clusters without authentication need only the user name.
Tables and views from one catalog per connection, narrowed to the schema you name. Querri copies the ones you pick into its Library. To bring in a second catalog, for example hive alongside iceberg, add a second connection.
Each connection follows the schedule you set: full reloads daily, weekly or monthly, or incremental syncs hourly, daily or weekly. An incremental sync reads only rows past the last value of a cursor column you choose, rather than copying the whole table again each run.
Not through this connector. It reads whole tables and views, so to sync a query's result, save it as a view in Trino and select that view. Querri can then join it with data from your other connected systems.
No. Querri only reads from Trino / Starburst. It never creates, edits or deletes records there, and every answer runs on Querri's own copy of the data.
Yes. Querri is SOC 2 Type II, HIPAA and ISO 27001:2022 certified, credentials are stored encrypted, and your data is never used to train a model.
Keep exploring
Connect Trino / Starburst, add the rest of your systems, and get answers your whole team can check.
