Skip to content

Connectors

Jump to bottom
Sanni heruwala edited this page Jun 12, 2026 · 1 revision

Connectors

13 SQL engines ship in the box. No extra pip install step, no driver setup, no ODBC dance.

Pick a connector from the Configure connection dialog in the top-left of the app. Each shows the fields it needs.

The full list

Connector What you need to fill in
DuckDB Nothing. Pick in-memory or a .duckdb file path.
Trino Host, port, user, password, catalog, schema, TLS settings.
PostgreSQL Host, port, user, password, database.
MySQL / MariaDB Host, port, user, password, database.
SQLite Path to the .db / .sqlite file.
MSSQL Host, port, user, password, database. ODBC 18 driver bundled.
Snowflake Account, warehouse, role, user, password, database.
BigQuery Project, dataset, service-account JSON path.
Redshift Host, port, user, password, database.
Oracle Host, port, user, password, database or service_name.
ClickHouse Host, port (8123 HTTP), user, password, database, secure flag.
Databricks SQL Host, http_path, access token, optional catalog.

For per-dialect field reference + production-ready env defaults, see docs/connectors.md.

DuckDB — the zero-setup default

Pick DuckDB (no server) in the dialog. Two modes:

  • In-memory (:memory:) — ephemeral playground. Great for one-off SQL against local files: 
    SELECT * FROM read_csv_auto('orders.csv') WHERE region = 'EMEA'
  • File (./local.duckdb) — persistent. Use it like a single-user warehouse: CREATE TABLE customers (…), INSERT …, etc.

Optionally set a Working directory so relative file paths in read_csv_auto / read_parquet resolve where you expect.

💡 You can also just drag files onto the app — they appear as DuckDB views automatically.

Trino — for team analytics

For team analytics on real data warehouses, fill in the UI dialog or set defaults in .env:

TRINO_HOST=trino.example.com
TRINO_PORT=443
TRINO_SCHEME=https
TRINO_USER=alice
TRINO_PASSWORD=...
TRINO_CATALOG=hive
TRINO_SCHEMA=default
TRINO_VERIFY_SSL=true

Custom HTTP headers, session properties, query timeouts, and result limits are all supported via the connection dialog's advanced section.

What's not in the box (yet)

  • Athena — open issue, contributors welcome.
  • Excel (.xlsx) upload — needs the DuckDB excel extension to autoload. Drag-drop works for CSV / TSV / Parquet / JSON today.
  • Google Sheets upload — needs an OAuth flow.

See the Roadmap for full status.

Coming soon: cross-source joins

Issue #3 — Cross-source joins via DuckDB ATTACH is in design. It will let you join Postgres + S3 + DuckDB tables in a single query without standing up Trino. If you want to pick it up, the design doc has the full plan.

Clone this wiki locally