Skip to main content
Summand has five built-in connectors plus a universal Fivetran path that handles everything else. Pick the one that matches how the data lives today; you can mix and match across one account.

​
How to choose

One-time analysis on a file you already have

Use CSV upload. No setup, no credentials.

Live data from a SQL warehouse

Use the database connector for Postgres, MySQL, Snowflake, or Azure SQL — direct connection, lowest latency.

Databricks with UniForm enabled

Use Delta Sharing — Iceberg-backed, type-faithful, incremental refresh.

A source not natively supported

Use Fivetran — anything Fivetran can sync, Summand can analyze.

​
What every source has in common

No matter the source, Summand:
  • Curates a Parquet copy of your data on first analysis. The source isn’t queried again until refresh.
  • Generates a semantic-layer version with the same artifacts (column stats, EBM, surprises, UMAP).
  • Enforces the same authorization (grants + visibility) regardless of source.
  • Charges the same for analysis — pricing is per-account, not per-source.
The differences between sources are in setup, credential handling, and refresh model, not in what you can do once a dataset exists.

​
Refresh model by source

​
Privacy and credentials

  • CSV uploads stream directly to Summand’s encrypted S3 bucket via presigned URLs. The file never passes through any application server.
  • Database credentials are encrypted at rest in AWS Secrets Manager. Plaintext is never logged.
  • Delta Sharing bearer tokens are stored encrypted in Secrets Manager; rotation is supported from the connector edit page.
  • Fivetran holds your source credentials — Summand only sees the Parquet output. Your warehouse password never touches Summand servers.