> ## Documentation Index
> Fetch the complete documentation index at: https://docs.summand.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data sources overview

> Every source Summand supports, what it's good for, and which tier it requires.

Summand has six 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.

| Source | Best for | Tier required |
| - | - | - |
| [CSV upload](https://docs.summand.com/data-sources/csv-upload.md) | One-off analyses, files up to 4 GB | Free + |
| [PostgreSQL / MySQL / Snowflake / Azure SQL](https://docs.summand.com/data-sources/databases.md) | Live data in your warehouse | Enterprise |
| [Delta Sharing](https://docs.summand.com/data-sources/delta-sharing.md) | Databricks UniForm shares with Iceberg metadata | Enterprise |
| [Fivetran](https://docs.summand.com/data-sources/fivetran.md) | Anything Fivetran supports — Databricks (non-UniForm), Redshift, Oracle, BigQuery, 300+ SaaS APIs | Enterprise |

## How to choose

> [card] [One-time analysis on a file you already have](https://docs.summand.com/data-sources/csv-upload.md)
>
> Use **CSV upload**. No setup, no credentials.

> [card] [Live data from a SQL warehouse](https://docs.summand.com/data-sources/databases.md)
>
> Use the **database connector** for Postgres, MySQL, Snowflake, or Azure SQL — direct connection, lowest latency.

> [card] [Databricks with UniForm enabled](https://docs.summand.com/data-sources/delta-sharing.md)
>
> Use **Delta Sharing** — Iceberg-backed, type-faithful, incremental refresh.

> [card] [A source not natively supported](https://docs.summand.com/data-sources/fivetran.md)
>
> Use **Fivetran** — anything Fivetran can sync, Summand can analyze.

## What every source has in common

No matter the source, Summand:

* **Keeps a copy** of your data as an Iceberg table (Parquet files) in Summand's S3 storage. Queries and analysis read that copy, not your source. For Fivetran, Fivetran writes the table into Summand's storage directly.
* **Generates a computed-context version** with the same artifacts (column stats, EBM, surprises, UMAP).
* **Enforces the same authorization** (sharing grants) 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

| Source | Refresh trigger | Notes |
| - | - | - |
| CSV | Upload a new version | Each upload writes a new snapshot of the same dataset. |
| Database (Postgres / MySQL / Snowflake / Azure SQL) | Manual refresh, or a schedule from hourly to weekly | Full refresh by default. Incremental append (by cursor column) and incremental merge (by cursor column and primary keys) are also available. |
| Delta Sharing | Manual refresh, or a schedule from hourly to weekly | Full refresh by default, or incremental append by cursor column. |
| Fivetran | Fivetran's sync schedule, or a manual sync | A manual refresh asks Fivetran to sync now. New data is queryable as soon as the sync finishes. |

## 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 synced tables. Your warehouse password never touches Summand servers.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.