F

Fivetran

Moves business data into cloud analytics systems

Overview

Fivetran moves data from business applications and databases into cloud analytics systems so data teams can work with reliable records instead of building pipelines by hand. Its ready-made connectors handle changes in source tables and software interfaces, reducing the maintenance needed to keep information up to date. Teams also use its transformation tools to turn raw records into datasets for reporting, operations and AI applications. Fivetran charges for usage, measuring the distinct records changed each month and the data models run, with plans for different security and operational needs. Founded in 2012, Fivetran is headquartered in Oakland, California.

YC Company

Work here?Claim your company

About Fivetran

Simplify's Rating
Why Fivetran is rated
B-
Rated B on Competitive Edge
Rated B on Growth Potential
Rated C on Differentiation

Industries

Data & AnalyticsEnterprise Software

Company Size

1,001-5,000

Company Stage

Debt Financing

Total Funding

$852.7M

Headquarters

Oakland, CA

Founded

2012

Get referred to Fivetran

See people who can refer or advise you

Simplify Jobs

Simplify's take

What believers are saying

  • Its product scope widened: the June 2026 dbt Labs merger joins data movement with transformation and governed business definitions.
  • Customers buy measurable time savings: Okta reports nearly 1,000 hours saved annually with Fivetran.
  • New hires receive equity grants: Fivetran advertises stock grants for all new hires and annual refresh grants.

What critics are saying

  • Customer usage adds up: Fivetran counts identical source records separately when connections feed multiple destinations.
  • Delivery has limits: Fivetran delays syncs at source request quotas and reloads tables lacking support for incremental updates.
  • Plan for office attendance: Fivetran's published hybrid model calls for two office days each week.

What makes Fivetran unique

  • Sensitive data stays local: Fivetran's managed Hybrid Deployment runs pipelines inside customers' own networks.
  • Open storage reduces lock-in: Fivetran maintains Iceberg and Delta tables that multiple computing engines read.
  • Data flows both directions: Fivetran Activations sends warehouse audiences into advertising and sales tools.

Help us improve and share your feedback! Did you find this helpful?

Funding

Total Funding

$852.6M

Above

Industry Average

Funded Over

8 Rounds

Debt funding comparison data is currently unavailable. We're working to provide this information soon!
Debt Funding Comparison Coming Soon

Benefits

  • Health Insurance
  • Unlimited Paid Time Off
  • Stock Options
  • Professional Development Budget
  • Phone/Internet Stipend
  • Mental Health Support

Growth & Insights and Company News

6 month growth

0%

1 year growth

0%

2 year growth

0%
Yahoo Finance
Nov 4th, 2026
Fivetran Named a Leader in the 2026 Gartner(R) Magic Quadrant(TM) for Data Integration Tools

Fivetran Named a Leader in the 2026 Gartner(R) Magic Quadrant(TM) for Data Integration Tools

PrettyWhale.ai
Oct 8th, 2026
Data engineering trends for 2027: 5 shifts already underway.

Data engineering trends for 2027: 5 shifts already underway. Trend lists for the coming year usually start from forecasts. This one starts from what shipped in the last 12 months. In data engineering, most of 2027 is already announced: the agents are shipping, and the deadlines are written into law. The 5 shifts below are all moving now, and several have a date coming up that will make them harder to ignore. 1. The platforms ship agents that write pipelines. Snowflake launched Cortex Code in November 2025. In February, it added support for dbt and Airflow, and a subscription for teams that do not run on Snowflake. Google's BigQuery has a data engineering agent that builds pipelines and troubleshoots them. In June, Databricks announced an agent that traces a pipeline failure to its cause and proposes a fix, tested in a sandbox before a person applies it. In September, dbt Labs announced dbt Wizard, and at the end of the month Microsoft put its data engineering agent for Fabric, Project Osmos, into preview. The interesting part is what these agents now do after writing the code. Microsoft tells users to put their validation criteria in the request: row counts, null checks, uniqueness, reconciliation or business rules. In its own worked example, the agent runs the old and new pipelines against staged targets and compares their row counts, duplicate keys, schema compatibility and output totals. dbt Wizard checks the upstream and downstream impact and builds the change before anyone sees the diff. Verification is moving into the agent itself. In September, Gartner forecast that by 2029, AI agents will have automated 75% of data engineering workflows. The next wave of announcements is already scheduled, with Microsoft Ignite from 17 November and AWS re:Invent from 30 November. What none of the launches settles is ownership. Once an agent has written the pipeline and its checks, someone still has to accept code that nobody on the team wrote, and the engineer's job moves from directing an assistant to accepting what it delivers. 2. The connector stops being the product. For most of the last decade, the connector was what data integration vendors sold. They maintained it, and you often paid by the volume of rows that went through it. That is changing from 2 directions. Fivetran's AI Connector Agent, in beta since May, generates new connectors on request, which then run on Fivetran's infrastructure. Databricks opened community connectors in beta: they are built with AI-assisted workflows for Claude Code or Cursor, tested against live sources, and maintained by the community without a Databricks SLA. When a long-tail connector can be generated in an afternoon, the scarce part is everything around it: the tests, the documentation, the decisions about what the data means, and someone who answers for it when the source changes. The cost of a connector moves from the licence to the maintenance. The question to ask of each tool is what it actually hands over. A connector hosted by a vendor and a connector delivered as code in your repository look the same in a demo, and they are different families of tool the day the source changes. In 2027, the build-or-buy decision will be made connector by connector. 3. The stack consolidates. In less than a year, the data stack lost several of its independent vendors. Salesforce closed its acquisition of Informatica in November 2025. In January 2026, Microsoft bought Osmos, a startup that used AI agents to automate data engineering. IBM completed its $11 billion purchase of Confluent in March, to feed its platform with streaming data for AI. On 1 June, Fivetran and dbt Labs completed their merger, putting 2 of the best-known tools in the stack, one for ingestion and one for transformation, in the same company. And in July, SAP completed its acquisition of Dremio, an open data lakehouse platform. The picture that emerges is a handful of platforms, each with an agent on top, covering ingestion, transformation, streaming and governance in one contract. For a data team, that means fewer integration seams to maintain, and more dependence on a single vendor's roadmap and pricing. The independents that remain will increasingly be judged on 2 things: how well they fit inside one of these platforms, and how easily you can leave them. The second question is where regulation comes in. 4. Portability moves into law. Connected products placed on the EU market after 12 September 2026 must be designed so that users can access the data they generate. From 12 January 2027, the Data Act stops cloud providers from charging customers for switching to another provider, data egress included. In financial services, DORA already requires exit plans for critical ICT services, and they must be "sufficiently tested". Open table formats make the storage side of leaving easier. Iceberg v3, approved by the Apache Iceberg community in 2025, brings deletion vectors and row lineage that line up with Delta Lake's, and Snowflake made v3 generally available in May. Data held in an open format can be read by another engine without a migration project. Storage is the easy part of leaving. The pipelines are harder, because vendor lock-in is built one connector at a time: connectors that only run on one platform, and checks that live in its interface. In 2027, the ability to leave becomes something an auditor or a regulator can ask you to demonstrate. 5. Context becomes something data teams ship. Agents need to know what the data means, and over the last year the industry started treating that meaning as something to build and deliver. In January, the Open Semantic Interchange working group, started by Snowflake and now including Salesforce, dbt Labs and Databricks, published the first version of its specification, a vendor-neutral model for semantic layer definitions, under an Apache 2 licence. In September, Fivetran previewed a Context Layer that assembles context for agents from semantic layers, documents and connected applications. dbt's MCP server, now generally available, exposes a project's models, metrics, lineage and test results to AI agents. Gartner expects that by 2030, universal semantic layers will be treated as critical infrastructure, alongside data platforms and cybersecurity. For data teams, the deliverable grows. Tables and dashboards are no longer enough. The definitions behind them, and the lineage that explains each value, have to be readable by a machine, for the same reason a code-generating agent needs a harness that knows the domain. There is a limit worth keeping in mind as these layers arrive. Context added above the warehouse cannot restore what a pipeline discarded on the way in: the rows it dropped, the types it forced, the keys it invented, the nulls that carry no reason. In 2027, the quality of an agent's answers will depend on decisions made at ingestion. What the 5 have in common. Read together, the 5 trends point the same way. Building pipelines gets cheaper every quarter. What stays expensive is ownership: of the code an agent writes, of the checks that say it is right, of the right to leave with both, and of the meaning of the data. 4 questions are worth asking before 2027: * When an agent writes a pipeline for you, where does the code live, and can your team read and change it? * Who writes the acceptance criteria, and do they live with the code or inside a vendor's interface? The answer settles what production-ready means for your team, and who gets to decide. * If one of your pipelines had to move to another platform next quarter, what would you have to rewrite? * Which of your definitions and lineage could an agent read today? PrettyWhale.AI is an Engineering AI for ingestion code. Given a sample of the source, it generates the pipeline with its tests and documentation in your repository, so the code and its checks stay with your team, whatever platform runs them. You have any questions on PrettyWhale.ai?

Cyparta
Sep 16th, 2026
dbt v2 goes GA: what the Rust rewrite and dbt State mean for your data team.

dbt v2 goes GA: what the Rust rewrite and dbt State mean for your data team. At dbt Summit 2026 on September 16, Fivetran + dbt Labs made dbt v2, a full Rust rewrite, generally available alongside dbt State and a wave of agent-focused previews. By eslam elhadedy

dbt Labs
Sep 16th, 2026
Fivetran + dbt Labs announces new capabilities to make enterprise data agent-ready at dbt summit 2026.

Fivetran + dbt Labs announces new capabilities to make enterprise data agent-ready at dbt summit 2026. Last edited on Sep 16, 2026 Fivetran + dbt Labs makes dbt v2 and dbt State generally available, alongside the debut of Fivetran Context Layer, dbt Charts and a new open lakehouse vision for greater flexibility across storage and compute LAS VEGAS - September 16, 2026 - Fivetran + dbt Labs today announced the general availability of dbt v2 and dbt State, delivering new levels of speed and cost optimization, and introduced Fivetran Context Layer, new dbt Wizard experiences, dbt Charts and an open lakehouse vision for greater flexibility across storage and compute. As enterprises deploy AI agents into production, they need trusted data, context the business controls, and the flexibility to work across the platforms, models and tools already in use. To meet these demands, Fivetran + dbt Labs is advancing its vision for Open Data Infrastructure: a vendor-neutral, interoperable architecture that lets organizations independently choose and evolve their storage, compute, data movement, transformation and visualization technologies at every layer. This enables AI systems to work across platforms using data and context the enterprise owns, not a single vendor. "Every model our customers have built, every test they've written, every metric they've defined already captures the context AI agents need to do meaningful work," said Anjan Kundavaram, Chief Product Officer, Fivetran + dbt Labs. "What we're delivering now is the open infrastructure to put that context to work across systems, while giving organizations the freedom to choose how their data is stored, moved, transformed and used as AI evolves." A faster, more efficient engine with deeper SQL understanding dbt v2 is a full Rust rewrite of the dbt engine built for the scale that teams run at today and for how agents write SQL. It parses a 10,000-model project up to 10x faster than v1 and gives teams and their agents accurate real-time feedback, surfacing errors, column checks, and lineage before anything runs. With this release, the two engine era of Core and Fusion ends. Now, dbt is one engine with two versions: dbt Core v1, the python implementation, is dbt v1. Fusion, the Rust implementation, has become dbt v2. Both versions remain Apache 2.0-licensed and security-supported. dbt State determines what has changed by checking warehouse metadata and model SQL, then builds, skips, clones or defers each run accordingly. This simplifies orchestration and allows engineers to iterate faster without complex development rituals, while reducing unnecessary warehouse compute. "dbt State has been a paradigm shift for how we work," said Gordon Curzon, Head of Analytics Engineering, Virgin Media O2. "With freshness codified, simpler orchestration, and freed-up developer capacity, we focus more time on initiatives that add value to our business on top of the 25% savings on both job run time and BigQuery compute costs." More flexibility across storage and compute Open Data Infrastructure centers on a customer-owned data layer built on open formats, avoiding vendor lock-in for storage and compute so organizations can store data once and access it through different engines for different use cases. Fivetran's Managed Data Lake Service, already generally available, organizes, structures and maintains data as managed Apache Iceberg(TM) tables in customers' own cloud storage. Lake Compute, now in Private Beta, is a single-node SQL engine built on DuckDB and runs dbt models directly against Apache Iceberg(TM) tables, built and priced specifically for transformation, not general-purpose compute. Together, the two give teams the flexibility to run each workload on whichever engine fits best, optimizing cost without re-platforming. An open standard for agent context Agents are only as trustworthy as the context they can access. Fivetran Context Layer (Private Beta) unifies the data and metadata needed to give LLMs and AI agents relevant context, building on dbt's structured context and adding unstructured knowledge, like docs and Slack threads. This service uses Agents Schema, an open source standard, that centralizes context in a structured, extensible format directly in the data warehouse. The context is accessible to teams via preferred MCP or AI tools, including generally available integrations through AI marketplaces including Anthropic and a plugin in ChatGPT. One agent, grounded in your dbt project - wherever you work Coding agents can now write SQL as well as most engineers, but writing code isn't the same as understanding a governed dbt project, including its lineage, its tests, its contracts, and what breaks when something changes. dbt Wizard in the dbt platform (Public Preview) is built to close that gap. It's natively connected to your project, knows which tool to call, pulls the right context automatically, and proactively validates changes before they ship. Wizard is also expanding beyond the dbt platform with Wizard CLI (Public Beta), bringing the project-grounded agent directly into the terminal, and Wizard Desktop (Private Beta), a dedicated local workspace for longer, more complex work. Wizard Explore Mode (Public Preview) brings conversational analytics to business users, enabling them to ask questions in plain language and get answers grounded in the same dbt project the data team maintains. When an answer falls short, those questions can also surface what the data team should improve next. A shared language for BI, built for humans and agents dbt Charts (Public Beta) brings governed BI alongside the models it depends on. Instead of governance living in a separate, closed tool, they are defined as YAML and version-controlled alongside the dbt models they reference, creating a shared, declarative format that both humans and AI agents can read, write and review. Customers building with Fivetran + dbt Labs "Since rolling out dbt State, we've reduced warehouse costs by 59% on scheduled jobs in dbt platform," said Chris Shepherd, Principal Data Engineer, RxBenefits. "That's $8,173.23 in the first 60 days alone on top of a Snowflake adaptive warehouse. We've reused 716k models instead of rebuilding, which reduced query run time a total of 14 days, 11 hours, and 15 minutes over the same period." "We've been impressed by the flexibility Lake Compute gives us. Now we can choose where each dbt workload runs, and use whichever engine actually fits the job," said Tyson Doberneck, Senior Data Engineer, Obie. "dbt Wizard is changing how we work. Instead of hand-coding everything, we draft logic with an agent that already has full context on our jobs and our codebase. No more finding and uploading a manifest file just to explain myself, that step used to slow down every request. Now we're pointing it at sales and marketing data too, so analysts get answers themselves instead of waiting on my team," said Farin Fukunaga, Data Engineering Lead, Paylocity. About Fivetran + dbt Labs Fivetran + dbt Labs deliver the data infrastructure layer that makes agents trustworthy - from the moment data moves, through every transformation, to the context an agent reasons from. The Fivetran platform moves, manages, and transforms data from every system a business runs on into a secure, reliable foundation engineered to evolve, with the flexibility to work across clouds, engines, and tools. With Fivetran, analytics, operations, and AI run on data you trust and control. Thousands of organizations worldwide, including OpenAI, LVMH, Pfizer, and Verizon, rely on Fivetran to turn data into a competitive advantage. Learn more at Fivetran.com, or follow Fivetran on LinkedIn. Since 2016, dbt Labs has been on a mission to help data practitioners create and disseminate organizational knowledge. dbt is the standard for AI-ready structured data. Globally, more than 100,000 data teams use dbt, including those at Siemens, Roche and Condé Nast. Learn more at getdbt.com, and follow dbt Labs on LinkedIn, X, Instagram, and YouTube.

MarTech360
Sep 11th, 2026
Fivetran promotes Natasha Lockwood to Lead of Product-Led Growth Marketing.

Fivetran promotes Natasha Lockwood to Lead of Product-Led Growth Marketing. Fivetran has promoted Natasha Lockwood to Lead of Product-Led Growth Marketing, expanding her responsibilities within the company's marketing organization. Lockwood's role focuses on product-led growth (PLG), an approach that connects product experiences with customer acquisition, engagement, and expansion. Her appointment comes as B2B software companies continue to explore ways to make the product itself a larger part of the marketing and customer journey. At Fivetran, Lockwood has built experience in digital strategy and cross-channel marketing. Her professional profile describes her focus as PLG marketing within B2B SaaS, alongside expertise in digital strategy and cross-channel campaigns. The expanded role places product-led growth more directly within Fivetran's marketing efforts. For B2B technology companies, PLG can involve using product usage signals, customer behaviour, digital experiences, and targeted campaigns to create more connected paths from initial interest to adoption. The shift is also part of a broader change in B2B marketing, where traditional lead-generation models are increasingly being complemented by product experiences. Rather than relying only on sales outreach or content to move prospects through the funnel, PLG strategies can use how customers interact with a product to inform marketing and engagement. For marketers, this creates a closer relationship between marketing, product, data, and customer experience teams. It also places greater importance on understanding user behaviour and identifying opportunities to support adoption throughout the customer lifecycle. Lockwood's promotion reflects that evolving role of marketing within SaaS businesses, where product engagement and customer behaviour are becoming increasingly important inputs for growth strategies. Her new position at Fivetran will focus specifically on product-led growth marketing as the company continues to develop its approach to reaching and engaging B2B technology buyers.

Recently Posted Jobs

Sign up to get curated job recommendations

Fivetran is Hiring for 195 Jobs on Simplify!

Find jobs on Simplify and start your career today

Don't see your dream role? Check out thousands of other roles on Simplify.Browse all jobs