Product Principles

Product principles provide a framework for making product decisions. They ensure that difficult product decisions are consistent with our use and value to users.

The Fivetran product strategy and resulting solutions are guided by five principles:

1. The core of Fivetran is and will always be connectors

Fivetran is a one-stop shop for all your data pipelining needs. Connectors are the base of everything we do and our primary offering. We build every product extension on top of our connectors (for example, Transformations, Fivetran REST API, and Powered by Fivetran).

Examples:

• We continue to expand the breadth of our connector offering
• We continue to enhance the experience of our key connectors

2. One default, simple, predictable choice

Our industry is rife with unnecessary complexity. Fivetran is as easy as possible for as many users as possible. We only provide advanced configuration to work around unavoidable system and environment complexity.

Examples:

• All table and column names become lowercase by default, so they can be queried more easily in SQL
• A single, standard schema for application connectors
• A default sync frequency of every six hours (or choose from our other sync frequency options)

3. Connectors just work

Fivetran's primary value is ensuring you don't have to think about your data pipelines - you can set it and forget it.

Examples:

• Automatically retry syncs if they fail
• Idempotent data loading so data is always correct
• Automatic support escalations when connectors are broken

4. Your data is secure

You trust us with your most important data, which is an enormous responsibility.

Examples:

• TLS and SSH verification protect against MITM attacks
• Unique service accounts and keys guarantee your data remains segmented
• Yearly pen tests and a strong compliance program (SOC2) help us stay ahead of security issues

5. Fast data movement

You need lightning-fast data integration to power your decisions and business operations. Fivetran has a quick setup process, fast historical syncs, and end-to-end updates with low latency.

Examples:

• Use incremental sync strategies in every place possible
• Automatically split large database table imports into multiple parallel threads
• Priority-first syncs for some connectors allow us to deliver the most important data much faster