Three levels of support
Not every connector does the same thing, and the difference changes what you can build on top of it. There are three levels, and the new-connection screen shows which one an engine is at.
| Level | What you can do |
|---|---|
| Query + schema | Reports, schedules, autocomplete and table browsing |
| Query | Reports and schedules; no autocomplete and no catalog |
| Availability | Health and version checks only — the query text is ignored |
Snowflake, Databricks, Amazon Athena and Vertica are marked beta: the provider is written and compiles, but has never been exercised against a live instance. The first real run will be yours, and we would rather say so than find out alongside you.
Why MongoDB and Redis produce no report
Because they are not SQL. Those executors ignore the query text by design: they open the connection, run the native protocol ping, and return the server version. That is useful for watching a dependency — knowing Redis is up — and useless for extracting data. Add them as connections if you want to watch them; do not attach a report.
Credentials
- Credentials are encrypted with AES-GCM before they touch the database, and the key does not live in the same table.
- The connection to your database uses TLS when the server offers it; hostless engines — BigQuery, Athena, Snowflake — authenticate through their own SDK.
- A password is never returned by the API after it is saved. On edit the field is blank and is only rewritten if you type something.
- Business workspaces can point at their own key (KMS) instead of using the service key.
Plan limits
| Plan | Connections | Queries per month | Rows per query |
|---|---|---|---|
| Free | 1 | 1,000 | 10,000 |
| Pro | 25 | 50,000 | 1,000,000 |
| Business | 100 | 500,000 | 10,000,000 |