Data Connectors: Postgres, Snowflake, BigQuery & More

Connect once, ask anything

Plug in Postgres, Snowflake, BigQuery, a CSV or a live market feed in under a minute — credentials encrypted, schema synced, ready for natural-language querying. No config files, no driver hunting, no setup tax between you and your first answer.

In data work, the hardest part is often the first five minutes. Before you can ask a single question you're chasing connection strings, installing drivers, copying credentials between tools, and hoping the SSL handshake works first time. That friction is where momentum goes to die.

DBx Studio connector layer exists to erase that tax. A connector is the bridge between DBx and wherever your data actually lives — a production Postgres database, a cloud warehouse, a spreadsheet on your desktop, a live market feed. Set it up once, and every part of DBx reads from it immediately: the SQL worksheet, AI chat, dashboards and generated artifacts.

What a connector is

A saved, secure link to a data source. Instead of re-entering credentials every time you open a worksheet or start a chat, you define the connection once and DBx remembers it — encrypted, and available everywhere.

• Broad coverage. Relational databases, cloud data warehouses and flat files are all first-class citizens.
• Secure by default. Credentials are encrypted and never stored in plain text, with optional SSL on every database connection.
• Schema-aware. On connect, DBx syncs your tables and columns so the AI knows your real structure — no manual mapping step.
• Universal across the app. One connector powers worksheet queries, AI chat, dashboards and artifacts alike.

Every source your stack runs on

Connectors come in three categories, with a search box and tabs — All, Data Warehouses, Databases, Sample Database — so finding the right one is immediate.

Databases — PostgreSQL, MySQL, SQLite (including local .db files) [complete the list]

Data warehouses — Snowflake, BigQuery [complete the list]

Files & sample data — CSV upload; Chinook sample (SQLite, 11 tables, ~15,000 rows); Live Stock Data (historical and live prices, cached locally)

What the connector layer does for you

1. Encrypted credentials. Every connection form says it plainly: credentials are encrypted and never stored in plain text. Passwords and secret keys are masked in the interface.
2. Test before you commit. Database connectors include a Test Connection button, so host, port and credentials are validated before saving.
3. SSL on by default. The Use SSL Connection toggle ships enabled for database connectors, protecting data in transit with no extra configuration.
4. Sync all databases. Show all databases pulls every database on the server after connecting, so you can browse a whole instance from one connector.
5. Built-in sample data. No data of your own yet? The Chinook sample and Live Stock Data get you exploring in seconds.
6. Local caching for live feeds. The Live Stock connector caches historical and live prices to a local .db file — fast queries without hammering the source.

Adding a live data source in under a minute

The full flow for a brand-new connector, with no SQL or config files involved.

1. Open Connectors and pick a source. From the left sidebar, open the Connectors panel and choose Live Stock Data under the Sample Database tab. [screenshot: connector gallery]
2. Name your connection. Something memorable — "Live Stocks Test." DBx auto-generates a local database filename for the cached data. [screenshot: naming step]
3. Choose an exchange and pick your tickers. Select a market (US Markets — NYSE/NASDAQ), then add the symbols you care about: AAPL, NVDA, TSLA. Selections appear as removable chips. [screenshot: ticker selection]
4. Set a history window and confirm. Choose how far back to pull data — say from 2024-01-01 — and DBx shows a connection summary before you commit. [screenshot: summary]
5. Add the connection and start querying. The new source appears instantly in your database list. Write SQL, or just ask: "Show the average closing price per ticker." DBx reads the schema, generates the query, and returns the answer. [screenshot: first query result]

For database connectors like Postgres or Snowflake the flow is just as short: enter your credentials, flip on SSL if you need it, hit Test Connection, and connect. The schema syncs and you're querying in seconds.

Security you don't have to think about

DBx encrypts credentials at rest, masks secrets in the interface, and defaults SSL on for database connections. Live feeds are cached locally on your machine, so queries stay fast and source systems stay un-hammered. Connect with confidence, without a security review for every new source.

What teams do with it

• Analysts point a connector at the production warehouse and ask questions in plain English, without waiting on a SQL backlog.
• Data engineers keep one connector for the worksheet and schema browser, moving between Postgres, Snowflake and a quick CSV without switching tools.
• Founders and PMs drop in a CSV export or spin up the live stock feed to explore a question in the moment, then turn the answer into a dashboard.

---

Connect in a minute, ask in the next one. Start with the Chinook sample if you want to see it work first, or point a connector at your own database and ask it something you already know the answer to.

Query it. Analyze it. Visualize it. — all with DBx.