When to use Fivetran
Sources Summand doesn't support natively
Databricks, Redshift, BigQuery, Oracle, MongoDB, plus 300+ SaaS sources (Salesforce, HubSpot, Stripe, etc).
You want to keep credentials away from Summand
Source credentials only live in Fivetran. Summand sees only the synced tables.
Your source is rate-limited
Fivetran handles incremental sync, retries, and rate-limit backoff for you.
How it works
Setup
1
Pick a source
From Connectors → Add connector → Fivetran, choose your source type (Databricks, Salesforce, etc.).
2
Authenticate in the Fivetran popup
A Fivetran-hosted Connect Card opens in a popup. Authenticate with your source — OAuth, API key, or username/password depending on the source. Credentials go directly to Fivetran; Summand never sees them.
3
Wait for the first sync
Fivetran’s first sync may take from a few minutes to several hours depending on source size and rate limits. You’ll see Pending first sync on the connector card until the first batch lands in S3.
4
Pick tables and configure datasets
Once the first sync completes, Summand discovers the schemas and tables. From there, pick the tables to use as datasets, as with a native database connector.
Refresh
Fivetran syncs on its own schedule. Summand doesn’t expose a cadence setting for Fivetran datasets. New data is queryable as soon as each sync finishes, with no separate step in Summand. Refresh in Summand asks Fivetran to start a sync now. Resync runs a full historical sync, and Pause stops syncing until you resume it. A finished sync updates the data. Analysis components run when you ask for them in chat or through an experiment.Billing
Fivetran charges based on monthly active rows (MAR) — the count of distinct rows synced per month. Summand’s bill is independent of this; we charge the standard Enterprise rate regardless of how much data Fivetran moves. Summand provisions every Fivetran connection in its own Fivetran account. Connecting Summand to a Fivetran account you already have is not supported.Limitations
- Latency: Data is as fresh as the most recent Fivetran sync, not real-time.
- Storage: Synced data stays in Summand’s bucket; we manage retention.
- Schema changes: Column changes in the source propagate on the next sync. By default, new tables are listed for you to enable rather than added automatically.
- Transformations: Summand reads the tables as Fivetran lands them, without Fivetran transformations.