Fivetran
品类龙头且企业客户证据扎实,但当前后期估值仍需打披露折扣
Fivetran 是质量很高的企业数据集成资产,但缺少私有财务披露支撑时,当前 $8.42B 的资格估值仍显得偏高。
封面要素
公司概况
Fivetran 是一家后期私有数据集成公司,凭托管式、感知 schema 的 ELT 进入现代数据仓库成名;2026 年与 dbt Labs 合并后,叙事进一步扩展到有治理的转换和面向 AI 的数据工作流。平台具备有分量的企业级信任功能、强有名客户证据和广泛的云 / 数据仓库生态触达,但公司披露的运营和资本细节仍远少于投资人通常会要求匹配超过 $8B 估值的水平。
- 成立时间
- 2012-01-01
- 创始人
- George Fraser, Raj Bhatnagar, Taylor Brown, Jen Streicher
- 创立地点
- Oakland, California, USA
- 总部
- Oakland, California, USA
- 产品
- Fivetran 销售按用量计费的托管式数据移动平台,提供数百个预构建连接器、混合部署、强信任控制、面向目标端原生的数据仓库和湖仓交付、自定义连接器工具,以及正在扩展的工作流叙事;该叙事如今包括与 dbt 关联的转换和 AI 智能体就绪能力。
- 客户
- 中型市场和企业数据团队、平台团队以及受监管组织;它们需要将数据可靠送入 Snowflake、Databricks 等云数据平台,同时不自己维护连接器。
- 商业模式
- 主要围绕月活跃行数(MAR)按用量变现,套餐包括 Free、Standard、Enterprise 和 Business Critical,配合年度合同 / ELA,并向受监管企业买家销售更高价值的部署和安全控制。
- 阶段
- Late-stage private / post-merger growth stage
- 融资情况
- 官方口径是到 2021 年 Series D 已至少融资 $730M;2026 年追踪源暗示还有额外融资,当前估值标记大约在 $5.9B 至 $8.4B 之间,资格事件集中在 2026 年 5 月按 $8.42B 估值完成的 D-1 延展轮。
执行摘要
主要优势
- 托管式、理解 schema 的产品,信任控制扎实,也支持混合部署。
- 连接器目录很宽,与 Snowflake、Databricks 和超大规模云厂商生态嵌合很深。
- 在受监管行业和全球企业里,具名客户证据异常扎实。
- 并购 dbt Labs 后,战略叙事从数据摄取扩展到受治理的数据工作流。
- AI 和多云推高数据移动复杂度,所在市场仍然庞大且在增长。
主要风险
- 面对超过 $8B 的后期估值,公开收入、利润率、留存和集中度披露都太薄。
- 基于用量的 MAR 定价反复引发公开市场对成本可预测性的担忧。
- 现有追踪来源对 2026 年准确估值分歧很大。
- 业务依赖源 API、云平台和数据仓库伙伴;这些外部方都可能改变经济性或复杂度。
- 并购整合必须拿出真实交叉销售和工作流扩张证据,不能只停留在叙事上。
未决问题
- 经审计收入、毛利率、烧钱速度和现金流材料。
- 客户集中度、NRR、GRR 和续约期限数据。
- 最新股权结构表、权利堆叠和已落定的 2026 年融资条款。
- 并购后 dbt 附加率、产品收入结构和交叉销售证据。
- 按严重程度队列划分的事故历史和 SLA 赔付表现。
目录
01公司概况
1.1 身份、历史,以及 2026 年的公司形态
Fivetran 当前的公开身份已经远不止“托管式 ETL”这个旧简称。官方页面把公司锚定为一家自动化数据移动平台:2012 年成立,总部在 Oakland,从 Y Combinator 起步,扩展成全球分布的基础设施厂商。2026 年 6 月与 dbt Labs 合并后,这个身份又向前推了一步:Fivetran 现在把合并后的平台描述为可信 AI 智能体的基础设施,而不只是连接器自动化。因此,本报告后续最稳妥的可复用事实底座是:这是一家总部位于 Oakland 的后期私有数据集成平台,拥有托管连接器、重企业级信任要求,并围绕有治理的数据移动加转换扩展产品叙事。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CO001, CO002, CO003, CO004, CO005, CO006]
| 指标 | 当前公开值 | 重要性 | 来源质量 |
|---|---|---|---|
| 创立时间 | 2012 | 锚定公司年龄和历史 | 高 |
| 总部 | Oakland, California | 为尽调提供地理锚点 | 高 |
| 全球办公室 | 10 个国际办公室 | 显示成熟运营足迹 | 中 |
| 连接器 | 700+ 个已记录连接器 | 核心产品广度证据 | 高 |
| 来源 + 目的地 | 900+ | 显示比连接器文档更宽的端点数量 | 中 |
| 定价模型 | 月活跃行数 | 解释变现方式和定价风险 | 高 |
| 客户数下限 | 5,000+ 客户(2022 年说法) | 官方历史页里最清晰的公开下限 | 中 |
| 最新独立估值信号 | 约 $8.4B 至 $8.42B,但有争议 | 带保留地设定后期背景 | 中 |
表中有意混合官方运营事实和独立估值信号;用于概览足够,但不能等同于经审计披露。
[CO001, CO004, CO005, CO010, CO011, CO013]| 日期 | 事件 | 类型 | 公开影响 |
|---|---|---|---|
| 2012-01-01 | Fivetran 创立 | 创立 | 确立标准起点 |
| 2013-01-01 | 参加 Y Combinator 批次 | 创立 | 获得早期创业验证和网络入口 |
| 2020-06-30 | $100M Series C 轮,估值 $1.2B | 融资 | 首个独角兽级估值锚点 |
| 2021-09-20 | $565M Series D 轮和 HVR 收购公告 | 融资 | 资本规模和产品范围大幅上台阶 |
| 2025-11-12 | 领导层扩充新闻稿 | 治理 | 显示公司在准备下一阶段增长 |
| 2026-04-10 | HITRUST i1 认证公告 | 信任 | 增加企业级合规信号 |
| 2026-06-01 | dbt Labs 合并完成 | 战略 | 平台从摄取延伸到受治理转换和 AI 工作流 |
| 2026-05-12 | 老股交易跟踪器记录 Series D 延展轮 / D-1 活动 | 估值 | 带来当前估值争议,而不是官方新闻稿式清晰度 |
时间线突出那些实质改变公司身份、资本结构、信任姿态或市场叙事的里程碑。
[CO001, CO003, CO019, CO020, CO017, CO007]一张紧凑的逻辑图,展示创始人、托管连接器、合规功能、合作伙伴和 dbt 合并如何共同强化 Fivetran 当前定位。
[CO001, CO006, CO013, CO017, CO035, CO007]1.2 商业模式和产品形态
公开产品和定价记录足以说明商业模式,尽管财务信息仍不完整。Fivetran 文档列出 700 多个连接器,官网首页则宣传 900 多个来源和目标端;最合理的理解是,前者是有文档的连接器子集,后者是更宽的端点数量。定价围绕 Monthly Active Rows 按用量计算,套餐包括 Free、Standard、Enterprise 和 Business Critical,并逐级增加同步频率、部署和安全功能。混合部署、私有网络、客户托管密钥和长合规清单都很重要,因为这些解释了公司为什么能卖给受监管企业,而不只是卖给价格敏感的 SMB 自动化买家。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CO010, CO011, CO012, CO013, CO014, CO015]
从连接器端点到转换和信任控制,用五层拆解 Fivetran 业务。
[CO006, CO010, CO013, CO015, CO016, CO018]定义 Fivetran 当前公司形态的方向性公开 KPI。
KPI 值是公司披露的下限指标或取整后的公开信号,并非独立审计数字。
[CO001, CO010, CO011, CO031, CO032]1.3 融资形成与当前估值标记
较早的融资历史证据扎实,但 2026 年的精确估值标记尚未完全敲定。Fivetran 自己的新闻稿清楚确认了 2020 年按 $1.2B 估值完成的 $100M Series C、2021 年 $565M Series D 及 HVR 收购、截至当时累计融资 $730M,以及 $5.6B 估值。但到 2026 年,二级市场和市场数据追踪源开始分化。Caplight 显示大约 $8.4B 的投后估值信号,PM Insights 报道 2026 年 5 月一轮接近 $257.4M、估值 $8.42B 的 Series D-1 延展轮,而 Stock Analysis / Hiive 仍显示明显更低的已确认估值。这种分歧是公司概况尽调中最重要的提醒:投资人可以确认战略动能,却还不能确认入场价格质量。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CO019, CO020, CO021, CO022, CO023, CO024]
| 利益相关方 | 角色 | 公开信号 | 待尽调问题 |
|---|---|---|---|
| General Catalyst / Andreessen Horowitz / ICONIQ / 其他 | 具名后期股权投资方 | Series D 与 Tracxn 投资者页面 | 确认当前持股和按比例跟投权 |
| Vista Credit Partners | 债权投资方 / 贷款方 | Tracxn 投资者页面 / 跟踪器记录 | 确认债务条款和担保包 |
| dbt Labs 利益相关方基础 | 合并交易对手方 | 合并完成新闻稿 | 厘清股权交换和治理组合 |
| 超大规模云厂商伙伴 | 分销和部署渠道 | AWS / Snowflake / Databricks 伙伴页面 | 量化按伙伴划分的收入集中度 |
| 企业客户 | 使用和背书基础 | 案例研究和评价页面 | 衡量客户标识集中度和续约暴露 |
| 员工和人才市场 | 运营能力来源 | 招聘页面和 Tracxn 员工估计 | 确认真实员工数和流失 |
这是公开利益相关方地图,不能替代私下股权结构表或合并对价明细。
[CO020, CO021, CO007, CO035, CO027]跟踪平台可见的 2026 公开估值信号,与 2021 最后一轮官方融资估值之间的区间。
2026 年数值来自独立跟踪平台,不是 Fivetran 新一轮官方融资新闻稿,因此该区间展示的是公开分歧,而非管理层指引。
[CO022, CO023, CO024, CO025, CO026]1.4 规模信号和可复用运营事实
Fivetran 最好的公开规模信号来自公司披露的运营指标,以及外部页面的交叉印证。公司仍引用 2022 年超过 5,000 家客户的数据;合并后,它又引用合并生态内超过 100,000 个数据团队。官网宣传 99.97% 正常运行时间、每月同步超过 2T 行、移动超过 9.1PB 数据、处理超过 33.5M 次 schema 变更,以及每月超过 156.5M 次同步。Tracxn 对员工数的估计约为 1,797,说明员工规模可能明显高于用户给出的 1,000 多人概括;Gartner、FeaturedCustomers、GitHub 和合作伙伴页面也都显示公司拥有可信的外部足迹。这些事实可以复用,但仍不能替代经审计的收入、董事会或股权结构披露。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CO027, CO028, CO029, CO030, CO031, CO032]
| 个人 / 群体 | 公开角色 | 证据 | 重要性 | 披露限制 |
|---|---|---|---|---|
| George Fraser | 联合创始人兼 CEO | 合并新闻稿 / 领导层新闻稿 | 战略与融资叙事的主要公开操盘者 | 董事会权利未披露 |
| Raj Bhatnagar | 创始人 / 早期公司架构者 | 关于页面叙述 | 锚定原始公司创建记录 | 已审阅记录未显示当前运营角色 |
| Taylor Brown | 创始人 / 产品技术骨干 | 关于页面叙述 | 显示公司不只是 CEO 单点身份 | 当前日常角色披露不清 |
| Jen Streicher | 创始人 / 运营骨干 | 关于页面叙述 | 让创始团队不止于工程师刻板印象 | 当前公开能见度低于 Fraser |
| Tristan Handy | 合并后总裁 | 2026 年合并新闻稿 | 重要,因为 dbt 整合改变公司身份 | 合并后权限范围仍处早期 |
| 扩大的领导层梯队 | 成长期高管 | 领导层新闻稿 | 暗示公司准备承接更大运营规模 | 完整董事会和委员会地图仍缺失 |
公开记录足以锚定创始人和合并后具名领导层,但还不是完整治理或董事会资料包。
[CO002, CO008, CO007, CO004]1.5 图表
02市场分析
2.1 市场规模很大,但品类边界很重要
保留的市场来源都支持数据集成是一个大机会,但它们描述的是不同切片。Precedence Research 指向数据集成市场在 2026 年约 $19.2B、到 2035 年超过 $51B;Research and Markets 则给出一个更宽口径、到 2030 年超过 $33B 的路径。Integrate.io 和 Peliqan 的 ETL / 管道聚焦摘要显示当前数字更小,但增长方向相近。正确结论不是挑一个神奇的 TAM 数字,而是承认 Fivetran 所在的是一个拥有持久增长的数十亿美元级市场,同时记住 ELT、数据管道和更宽的数据集成平台标签不能互换。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CM001, CM002, CM003, CM004, CM005, CM025]
| 视角 | 2026 年数值 | 增长信号 | 尽调用途 |
|---|---|---|---|
| 广义数据集成 TAM | ~$19.2B | 到 2035 年可超过 $51.8B | 最好的广义品类锚点 |
| 到 2030 年的更广义市场路径 | 到 2030 年约 $33.2B | 低双位数 CAGR | 显示市场成熟但仍在增长 |
| ETL 子市场 | 高个位数十亿美元 | 两位数增长 | 更适合作为 Fivetran 核心业务代理 |
| 管道工具视角 | 小于广义 TAM,但增长快 | 两位数增长 | 适合做估值敏感性分析 |
| 云数据平台需求 | 伙伴驱动,以数据仓库为中心 | 结构性扩张 | 解释进入市场路径的契合度 |
表格有意混合不同市场视角;这些视角相互重叠,不能相加。
[CM001, CM002, CM003, CM005, CM025]| 品类 | 代表供应商 | 与 Fivetran 的重叠方式 | 差异原因 |
|---|---|---|---|
| 托管 ELT / 数据摄取 | Fivetran, Hevo, Stitch | 直接重叠 | 核心连接器同步品类 |
| 开源数据集成 | Airbyte | 在大量连接器上竞争 | 成本更低 / 偏自托管 |
| 转换工作流 | dbt Labs | 相邻领域,现已合并 | 主要是摄取后的建模 |
| 更广义 iPaaS / 应用集成 | Boomi, SnapLogic | 在集成预算上重叠 | 通常比数据仓库摄取更宽 |
| 数据编织 / 企业集成 | Informatica, Qlik Talend | 在企业架构交易中重叠 | 更强调治理和遗留资产 |
这张地图有意简化:实际业务里品类边界会变模糊,但区分它们对可服务市场测算很重要。
[CM015, CM016, CM017, CM018, CM024]从宽口径数据集成 TAM 到 Fivetran 更窄的可服务托管 ELT 机会的嵌套视图。
各层是分析性子集,不是可相加桶。
[CM001, CM003, CM024, CM034]公开市场规模估算因口径不同而差异很大,但保留来源都指向有意义的类别规模。
保留来源只直接给出了宽口径 TAM 和长期上限;ETL 区间是根据多页 2026 统计数据取整综合而成。
[CM001, CM002, CM003, CM004, CM005]2.2 需求为何持续:AI、多云蔓延和有治理的分析
2026 年的需求驱动比早期云端 ETL 周期更强。AI 项目需要新鲜、有治理、可直接进仓库的数据,而不只是原始 API;这让可靠的连接器自动化具备战略重要性。多云蔓延和来源系统增多抬高了内部自建的运营成本,schema 漂移又带来许多买家不想自己承担的维护负担。同时,GDPR、HIPAA 和企业安全审查让部署灵活性与信任功能成为市场需求的一部分,而不是可选附加项。因此,即使低成本工具不断增多,一个托管式、重合规的平台仍能获得买家兴趣。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CM006, CM007, CM014, CM026, CM027, CM020]
| 用户画像 | 主要任务 | 预算所有者 | Fivetran 有望胜出的原因 |
|---|---|---|---|
| 数据工程负责人 | 可靠搬运生产数据 | 平台 / CIO | 托管连接器减少维护 |
| 分析工程 / dbt 负责人 | 保持数据仓库模型新鲜 | 数据平台 | 干净的数据摄取提升模型可靠性 |
| 安全 / 合规 | 批准数据流转路径 | CISO / 风险 | 私有网络和部署控制 |
| 平台 / 云运维 | 标准化数据仓库数据流 | CIO / 基础设施 | 与伙伴对齐的部署 |
| 业务分析使用者 | 使用数据,很少直接采购 | 只影响职能预算 | 需要新鲜、可信的仪表盘 |
这些用户画像来自产品、定价和竞品材料反复暗示的角色,而不是某一份公司披露的分层备忘录。
[CM011, CM012, CM013, CM031]需求如何从原始系统蔓延,推进到托管数据移动的采购决策。
[CM006, CM007, CM011, CM014, CM031]示意企业从识别集成痛点到生产平台标准化的漏斗。
漏斗数值是方向性估计,不是 Fivetran 披露的转化率。
[CM007, CM008, CM020, CM029]2.3 谁在买,实际买的是什么
买家通常不是随手试用的业务用户。典型选择职能是数据工程、分析工程、平台、安全和 IT 领导层,预算权更接近 CIO、CDO 或平台组织。这些团队最常围绕 Snowflake、Databricks 或相邻云数据平台标准化,因此和初始设置速度一样重视可靠性、治理和生态契合度。大型企业主导当前支出,因为它们要连接的系统更多,管道失败的风险也更高。SMB 增长存在,但低成本替代品拿走了这部分需求中的相当份额。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CM011, CM012, CM013, CM008, CM009, CM031]
2.4 Fivetran 的位置,以及市场反推的边界
Fivetran 可服务市场小于整个集成 TAM,这一点对承销很重要。开源和自托管工具在低端压制定价,而 Boomi、Informatica、Qlik Talend 和 SnapLogic 能赢下更宽的平台交易,范围包括 API 和应用集成。dbt 仍更靠近转换环节,而不是上游抽取;反向 ETL 会扩大预算,但并不完全定义同一个市场。结果是一个好但有边界的品类位置:Fivetran 在面向数据仓库的企业托管式 ELT 中位置不错,但不能假定自己能拿下每一条工作流、编排或集成预算线。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CM015, CM016, CM017, CM018, CM024, CM029]
2.5 图表
03竞争格局
3.1 托管式 ELT 的直接战场
Fivetran 最接近的竞争对手,是那些承诺无需大量自定义编码即可把数据摄取到数据仓库的厂商。Airbyte、Hevo、Matillion 和 Stitch 都在这场讨论中出现,但它们并不相同。Airbyte 是最清晰的开源和自托管替代品。Hevo 销售类似的易用性叙事,包装更明确。Matillion 在同样看重转换效率的云数据团队买家中保持强位置。Stitch 仍与品类相关,不过其当前公开存在感似乎不如云端 ELT 周期早期那么核心。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CP001, CP002, CP003, CP011, CP004, CP006]
| 供应商 | 主要品类 | 核心强项 | 对 Fivetran 最相关的威胁 |
|---|---|---|---|
| Fivetran | 托管 ELT | 运营可靠性和信任 | 价格可预测性 |
| Airbyte | 开源数据集成 | 自托管灵活性和低成本进入 | 挤压中端市场和技术型买家 |
| Hevo | 托管管道 / ELT | 更简单的打包和易用性 | 在可预测性和见效速度上竞争 |
| Matillion | 云数据集成 | 贴近转换的工作流,并适配云团队 | 争夺现代数据团队 |
| Stitch / Qlik | 云 ETL / 产品组合产品 | 老牌认知和组合打包 | 在更简单的 ETL 交易中相关 |
本表隔离出多数买家在数据仓库主导交易中最可能拿来与 Fivetran 一起入围的直接替代集合。
[CP001, CP002, CP011, CP004, CP006]按托管便利性和平台宽度衡量的相对定位。
分数是基于公开定位页面的分析师序位判断,不是用户评价综合。
[CP001, CP002, CP011, CP009, CP010, CP007]3.2 更宽套件型竞争对手会影响企业采购
Fivetran 不只是在和长得像 Fivetran 的工具竞争。企业想要一个覆盖数据集成、应用集成、治理和 API 编排的单一供应商时,Boomi、Informatica、Qlik Talend 和 SnapLogic 都很重要。因此,有些交易根本不是连接器比拼,而是平台标准化决策。买家以数据仓库为中心、把托管可靠性置于覆盖广度之上时,Fivetran 能赢;更宽的企业集成范围比同类最佳 ELT 执行更重要时,Fivetran 会输。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CP007, CP008, CP009, CP010, CP018, CP024]
| 供应商 | 出现在交易中的原因 | 更强之处 | Fivetran 更强之处 |
|---|---|---|---|
| Boomi | 单一供应商集成要求 | 应用 / API 广度 | 以数据仓库为中心的 ELT 深度 |
| Informatica | 复杂遗留企业治理 | 企业集成广度 | 托管云数仓易用性 |
| Qlik Talend | 数据织构和更宽的工程叙事 | 产品组合范围 | 聚焦托管式摄取 |
| SnapLogic | 集成加 AI 工作流打包 | 工作流 / 平台广度 | 专门化 ELT 执行 |
公开产品页面支持范围对比,但不支持逐客户细分的赢率对比。
[CP009, CP010, CP007, CP008, CP018]按数据仓库驱动的企业交易中最关键采购标准,定性比较功能匹配度。
[CP012, CP018, CP017, CP030]3.3 Fivetran 最强的地方
Fivetran 公开可见的最强差异化不是炫技,而是运营能力。客户重视零维护连接器、强目标端支持、受监管企业信任控制,以及与 Snowflake、Databricks、AWS 紧密对齐时,公司看起来最强。Connector SDK 和社区目录也有助于削弱“只有开放平台才能覆盖长尾”的说法。如果 Fivetran 要守住溢价定价,这些运营强项正是它必须持续在规模上证明的东西。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CP012, CP013, CP015, CP020, CP029, CP033]
| 维度 | Fivetran 评级 | 理由 | 尽调要验证什么 |
|---|---|---|---|
| 托管可靠性 | 高 | 核心产品承诺是低运维同步 | 验证 SLA 和事故历史 |
| 连接器广度 | 高 | 数百个有文档的连接器,加自定义 SDK | 验证目标垂直行业的连接器深度 |
| 企业信任 | 高 | 混合部署、网络和密钥管理控制 | 检查受监管客户能否作为参考 |
| 价格可预测性 | 中低 | MAR 仍受批评 | 索取扩张和超额用量数据 |
| 自托管灵活性 | 中 | 混合部署有帮助,但本质不是开源自托管 | 用受监管潜在客户测试 |
| 开发者心智 | 中 | 有 SDK,但开源竞争对手声量更大 | 衡量社区贡献节奏 |
评级来自保留来源的分析总结,不是供应商提供的基准。
[CP012, CP013, CP014, CP016, CP031, CP022]方向性条形图,展示买方在 Fivetran 与直接竞争对手之间面对的主要取舍。
数值是序位判断,不是调研百分比。
[CP028, CP023, CP024, CP029]3.4 Fivetran 暴露的地方
公司的主要竞争弱点同样清楚。按用量计费经常被批评难以预测,开源和自托管对手在中型市场施压;当采购想要一个拥有更多应用层覆盖的单一供应商时,更宽的套件也能从侧翼包抄。dbt 合并有助于拓宽叙事,但也抬高了期待:如果合并后的平台无法比更便宜或更宽的替代品拿出更好的经济性、信任和集成工作流价值,单独的摄取层会越来越像商品化能力。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CP016, CP017, CP019, CP021, CP023, CP031]
| 风险 | 主要竞争对手组 | 为什么重要 | 监控指标 |
|---|---|---|---|
| MAR 反弹 | Hevo / Airbyte / Matillion | 可能削弱新客户转化和续约基调 | 按 ARR 区间看折扣和流失 |
| 平台捆绑失单 | Boomi / Informatica / Qlik / SnapLogic | 更宽的套件可能拿下架构型交易 | 企业 RFP 失单原因 |
| 连接器商品化 | 开源加数仓原生功能 | 可能侵蚀溢价倍数 | 毛利率和附加率 |
| 转换价值叙事缺口 | dbt / 集成套件 | 客户想要端到端工作流价值 | 合并后产品的交叉销售 |
| 内部自建替代 | 工程主导客户 | 可能压低窄场景 ACV | 简单数据源部署的赢率 |
每项风险都能在公开材料里看到,但没有内部管线和失单分析数据,无法完全量化。
[CP016, CP018, CP027, CP021, CP019, CP034]3.5 图表
04财务情况
4.1 业务如何赚钱
Fivetran 的变现模式是财务叙事中最清晰的部分之一。公司主要按月活跃行数(MAR)定价,用免费层播种采用,然后随着数据量、同步需求和安全要求增长,把客户推向 Standard、Enterprise 或 Business Critical 套餐。年度合同和 ELA 提供可预测性,但基本经济现实仍与数据量挂钩。客户集中更多系统时,Fivetran 因此拥有有意义的扩张上行;但预算收紧时,客户也可能遭遇账单冲击,或激进优化行数。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CI001, CI002, CI003, CI004, CI005, CI006]
| 要素 | 公开描述 | 财务含义 | 风险 |
|---|---|---|---|
| MAR 计费 | 按移动行数用量计费 | 收入随数据增长扩张 | 客户账单可能波动 |
| 免费计划 | 受限入门层 | 低摩擦获客漏斗 | 可能吸引低价值试用 |
| 企业套餐 | 更高频率和控制项 | 支撑更高 ACV 和增购 | 企业销售周期更长 |
| Business Critical | 顶级信任 / 合规档 | 最高价值打包 | 需要持续证明可靠性 |
| ELA / 年度条款 | 固定价格选项 | 提高可预测性和采购适配度 | 定价过低会压缩上行 |
该表刻画商业机制,不代表已实现收入结构。
[CI001, CI003, CI004, CI005, CI031, CI006]| 问题 | 证据 | 潜在财务影响 | 缓释 |
|---|---|---|---|
| 账单意外 | 独立定价批评 | 可能拖慢新客户转化和续约 | 提供 ELA / 年度条款 |
| 用量增长集中度 | MAR 模型 | 收入对客户数据扩张敏感 | 分散客户基础 |
| 成本敏感型竞争 | Airbyte / Hevo / Matillion 页面 | 可能迫使打折 | 证明可靠性与合规 ROI |
| 转换功能附加不确定性 | 包含基础转换 | 变现增量未知 | 跟踪合并后交叉销售 |
| 支持 / 审核负担 | 企业控制项抬高预期 | 可能推高服务成本 | 守住 SLA 和支持质量 |
各行结合了观察到的定价结构,以及分析师对财务影响的推断。
[CI007, CI008, CI006, CI029, CI030]用量如何从源采用流向变现,再通向财务上行或账单冲击风险。
[CI001, CI006, CI005, CI028]从免费获客到 Business Critical 企业打包的商业阶梯。
[CI002, CI003, CI004, CI031]4.2 公开融资历史扎实;公开运营指标并不扎实
到 2021 年为止,官方融资历史证据很强。Fivetran 自己的公告确认了 2020 年 Series C 和 2021 年按 $5.6B 估值完成的 $565M Series D,且截至当时至少已融资 $730M。之后,记录变得嘈杂得多。独立追踪源暗示还有额外融资活动和更高估值,但公司没有给出公开的 2026 年收入运行率、ARR、利润率、烧钱速度或留存框架来匹配这些估值。因此,这是一个具备可信动能、但运营透明度薄弱的后期资本故事。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CI009, CI010, CI011, CI012, CI013, CI014]
| 日期 | 事件 | 金额 / 估值标记 | 启示 |
|---|---|---|---|
| 2020-06-30 | Series C 轮 | $100M,估值 $1.2B | 独角兽规模里程碑 |
| 2021-09-20 | Series D 轮 | $565M,估值 $5.6B | 大幅估值跃升和 HVR 整合资本 |
| 2021-09-20 | 官方累计融资 | 至少 $730M | 最稳妥的硬资本下限 |
| 2026-05-12 | PM Insights 跟踪器事件 | $257.4M,估值 $8.42B | 若准确,支撑溢价估值标记 |
| 2026-05-12 | Stock Analysis / Hiive 跟踪器事件 | 上次确认 $5.87B | 显示明显分歧 |
| 2026-04 to 2026-08 | Caplight 老股交易信号 | ~$8.4B 投后估值 | 显示投资者需求仍在 |
2026 年行基于跟踪器,而非公司官方融资披露。
[CI009, CI010, CI011, CI013, CI014, CI015]以十亿美元计的公开历史估值和跟踪平台估值信号。
2026 项并非公司官方融资披露。
[CI009, CI010, CI015, CI014, CI013]4.3 关于财务质量,我们能推断什么、不能推断什么
最强的正向推断是:当可靠性、信任和受监管部署很重要时,企业似乎愿意为产品付费。客户证据页面引用了大额运营收益,例如 HubSpot 节省 $100,000、NAB 获得成本和 ML 收益;产品页面也声称托管落地模式显著降低摄取成本。但这些案例无法解决分母缺失问题。公开材料仍没有经审阅的 ARR、毛利率、烧钱速度、现金或 NRR 披露。因此,财务故事是可信的,但还没被证明。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CI022, CI023, CI024, CI025, CI017, CI018]
| 指标 | 公开可得性 | 最佳保留信号 | 尽调需求 |
|---|---|---|---|
| ARR / 收入运行率 | 保留来源未披露 | 无可靠信号 | 索取经审计的月度经常性收入和用量收入 |
| 毛利率 | 未披露 | None | 按云、支持、合作伙伴类别索取 COGS |
| 烧钱速度 / 现金跑道 | 未披露 | None | 索取现金流和现金余额 |
| NRR / GRR | 未披露 | None | 按 ARR 区间索取队列留存 |
| 债务条款 | 仅在跟踪器 / 投资者提及中弱可见 | Vista Credit / 监管文件搜索线索 | 索取债务协议和契约 |
这张表刻意直白:财务数据缺口是核心问题。
[CI017, CI018, CI019, CI020, CI033]财务论证有多少已被证明、多少仍不透明的评估区间。
分数是基于公开记录的分析师序位评级,不是管理层指标。
[CI001, CI032, CI033]4.4 核心财务承销问题是不透明,而不是品类需求
核心财务问题因此不是客户是否会为数据集成花钱,而是 Fivetran 的按用量计费模式能否维持溢价增长和利润率,同时不制造足够大的定价摩擦、引来下沉市场替代。批评者反复盯着意外账单和 MAR 膨胀,竞争对手定价页面则强调更简单的包装。二级市场估值暗示一些投资人依然看多,但这些估值无法替代内部收入、队列和利润率披露。任何严肃的承销案例都必须向管理层索要公开定价外壳背后的真实运营模型。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CI007, CI008, CI028, CI031, CI034, CI035]
4.5 图表
05产品与技术
5.1 核心架构是向企业级目标端的托管式数据移动
Fivetran 的产品架构最容易理解为一个托管控制平面,夹在大量杂乱来源系统与数量较少的战略目标端之间。官方页面持续强调低维护同步、感知 schema 的自动化和目标端原生交付。连接器广度已经足以产生商业意义;只要报告表述谨慎,700 多个有文档连接器与 900 多个总来源和目标端之间的差异可以接受。这是真正的企业级数据产品形态,而不是围绕少数 API 做一层薄封装。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CE001, CE002, CE003, CE004, CE005, CE006]
| 层 | Fivetran 做什么 | 为什么重要 | 证据质量 |
|---|---|---|---|
| 源端连接 | 覆盖 SaaS、数据库、文件和事件系统的托管连接器 | 广度拉动采用 | 高 |
| 目标端交付 | 数据仓库和湖仓交付 | 核心价值兑现点 | 高 |
| 转换 / 激活邻近能力 | 转换与激活打包 | 显示价值链扩张 | 中 |
| 信任控制 | 网络、密钥、合规、数据驻留 | 受监管交易的关键 | 高 |
| 可扩展性 | SDK、社区连接器、Terraform | 改善长尾适配 | 高 |
能力反映公开材料,并刻意按买家关心的层次分组,而不是按产品页导航标签。
[CE001, CE002, CE016, CE010, CE024]分层展示 Fivetran 如何把源系统蔓延转成可治理、可进入目标端的数据。
[CE001, CE005, CE015, CE010, CE033]从连接源到可信分析 / AI 就绪数据的典型路径。
[CE001, CE005, CE016, CE017, CE035]5.2 信任、部署与企业控制是核心产品功能
对受监管买家而言,最重要的技术主张不是原始同步次数,而是信任控制。混合部署、私有网络、客户托管密钥、支持边界选项和广泛合规引用,都指向一个能通过企业审查的产品。这些很关键,因为它们解释了 Fivetran 为什么能争取严肃的数据平台预算,而不是被挤进商品化 SMB 工具箱。它们也让后续客户和风险分析更容易理解。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CE007, CE008, CE009, CE010, CE011, CE012]
| 控制项 | 公开证明 | 买方收益 | 剩余问题 |
|---|---|---|---|
| 混合部署 | 安全和产品页面 | 将敏感数据留在客户环境 | 实际有多少客户使用? |
| 私有网络 | 安全页面 | 降低在公网暴露 | 是否有吞吐量取舍? |
| 客户管理密钥 | 安全态势 | 为受监管工作负载提供更多控制 | 按 ARR 区间的附加率? |
| 数据驻留选项 | 信任 / 安全页面 | 帮助区域合规 | 按连接器划分的确切地域覆盖? |
| 合规认证 | 安全 / 信任表面 | 缩短供应商审核周期 | 范围和续期时间? |
控制项的公开证明很强;采用情况和运营细节仍属私有。
[CE007, CE008, CE009, CE012, CE010]围绕企业买方最关心的合作伙伴生态,展示公开可见的适配度。
[CE018, CE021, CE022, CE020, CE019, CE033]对公开记录中最可见的产品领域做定性成熟度判断。
[CE030, CE029, CE031, CE035]5.3 平台正在超越单纯的连接器同步
2026 年的产品故事比经典 SaaS 到数据仓库摄取更宽。官方材料指向托管式数据湖落地、定价页面上的转换和激活能力,以及合并后通过 dbt 工作流和可信 AI 智能体定位展开的扩张。这并不意味着 Fivetran 已经摆脱对核心摄取的依赖,但确实说明公司正在拓宽自己拥有的价值链。产品现在更像一个有治理的数据移动层,并向邻近工作流收口,而不是狭窄的管道供应商。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CE015, CE016, CE017, CE034, CE035]
5.4 开发者和生态界面提高可扩展性,但护城河仍是运营能力
Connector SDK 文档、GitHub 仓库、Terraform provider、PyPI package 和合作伙伴页面都说明可扩展性很重要。这有助于抵消常见批评:只有开源平台才能覆盖长尾。不过,可见护城河并不是 SDK 文档本身存在,而是在许多合作伙伴目标端之间以最少客户维护保持大量连接器可用的运营能力。这条护城河真实存在,但也暴露在第三方 API 变化和公司自报性能主张的限制之下。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CE023, CE024, CE025, CE026, CE027, CE028]
5.5 图表
06客户情况
6.1 对私有基础设施软件而言,公开客户证据异常强
在私有数据基础设施公司中,Fivetran 拥有更强的公开客户证据面之一。官方客户故事库很广,FeaturedCustomers 增加了第三方案例库存,Gartner 则提供独立评论界面。更重要的是,具名案例并不全是模糊 logo。Pfizer、NAB、Coke One North America、HubSpot、LVMH、Saks、Cemex 和 Activision 合在一起覆盖多个受监管和高规模环境。这让客户证据成为真正的尽调资产。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CU001, CU017, CU018, CU002, CU003, CU004]
| 客户 | 行业 | 公开成效 | 重要性 |
|---|---|---|---|
| Pfizer | 医疗健康 / 制药 | 实时临床试验数据工作流 | 受监管、任务关键场景的证明 |
| National Australia Bank | 金融服务 | 客户体验和生成式 AI 赋能 | BFSI 级信任证明 |
| Coke One North America | CPG / 制造 | 35,000 名用户访问 SAP 洞察 | 大规模内部用户覆盖 |
| HubSpot | SaaS | 公开声称节省 $100k | ROI 表述具体 |
| Cemex | 工业 | 1,800 多个设施实时连接 | 全球运营规模 |
行聚焦最可复用的公开案例事实,不是完整客户名单。
[CU002, CU003, CU004, CU005, CU008, CU001]从数据蔓延痛点到跨团队标准化生产使用,公开证据显示出这样的路径。
[CU020, CU021, CU030]对信号最强的具名客户,比较其公开验证质量。
[CU002, CU003, CU004, CU005, CU022]6.2 最强公开案例指向生产规模、跨职能使用
最好的案例看起来像企业级项目,而不是孤立测试。Pfizer 把 Fivetran 与临床试验提速连接起来,NAB 连接到客户体验和 GenAI,Coke 连接到面向 35,000 名用户的 SAP 洞察交付,Cemex 连接到 1,800 多个设施,HubSpot 则连接到清晰的成本节省。这些结果正是数据移动供应商已经嵌入生产运营时会出现的类型。它们也暗示公司可在分析、运营报表和 AI 相邻工作流之间做跨职能扩张。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CU008, CU009, CU012, CU013, CU014, CU015]
| 行业 | 具名案例 | 证明强度 | 尽调解读 |
|---|---|---|---|
| 医疗健康 / 生命科学 | Pfizer, Adragos | 高 | 高度契合受监管工作流 |
| 金融服务 | NAB | 高 | BFSI 可信度较好 |
| 零售 / 奢侈品 | Saks, LVMH | 高 | 支撑商品运营和 AI 叙事 |
| 游戏 / 媒体 | Activision | 中-高 | 展示大型活动和受众用例 |
| 工业 / 制造 | Cemex, Coke, Adragos | 高 | 运营数据契合度较好 |
| SaaS / 初创公司 | HubSpot, Fountain | 中-高 | 展示数字原生客户采用 |
行业跨度是有意义的正面信号,因为它削弱了单一垂直行业依赖的印象。
[CU012, CU013, CU027, CU001]| 客户 | 具体成效可见? | 运营规模可见? | AI / 实时角度? |
|---|---|---|---|
| Pfizer | 是 | 是 | 是 |
| NAB | 是 | 是 | 是 |
| HubSpot | 是 | 中 | 是 |
| Coke One | 是 | 是 | 是 |
| LVMH | 中 | 中 | 实时 |
| Saks | 中 | 中 | AI 赋能 |
具体性评分反映已审阅案例页面中可见的具体成效文本有多少。
[CU015, CU016, CU021, CU001]从首次部署连接器,到企业把数据平台使用标准化。
[CU013, CU019, CU021]6.3 客户足迹全球化,且以数据仓库为中心
保留证据横跨北美、欧洲和亚太,并与主流数据仓库和湖仓生态深度绑定。Snowflake、Databricks 和 AWS 的页面进一步说明,客户部署位于常见企业云数据栈内部,而不是定制本地报表项目。这种生态契合度很重要,因为它提高了客户采用随着更广泛数据平台标准化而扩张的概率。它也说明公司的最佳客户是拥有有意义长期数据资产的成熟团队。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CU019, CU020, CU027, CU028, CU029]
| 阶段 | 典型动作 | 公开证明 | 扩张含义 |
|---|---|---|---|
| 需求识别 | 源系统蔓延、报表痛点突出 | 官方客户故事定位 | 催生集中化紧迫感 |
| 初始部署 | 先连接高价值系统 | Fountain / HubSpot 式案例 | 快速兑现价值很重要 |
| 生产信任 | 安全性和可靠性审查 | Pfizer / NAB / Coke 的规模证明 | 控制能力成为采购关口 |
| 跨团队扩张 | 更多职能采用共享数据流 | 零售、制造和 AI 用例拓宽 | 推高 ACV 和切换成本 |
| 续约 / 嵌入 | 平台成为基础设施层 | 主要 Logo 随时间反复出现 | 暗示耐久性,但不能证明 |
这是一张根据案例模式综合出的分析型旅程图,不是公司发布的漏斗。
[CU020, CU030, CU025]按客户类型构建的示意性留存代理,依据是反复出现的公开引用质量,而不是已披露的续约数据。
数值是分析师根据重复公开引用质量和产品关键性构建的代理,不是已披露的客户留存。
[CU025, CU031, CU024]6.4 客户质量看起来强,但客户经济性大多仍属私有
主要限制在于,几乎所有证据都只是公开证明质量的证据,而不是客户经济性证据。记录没有披露集中度、按 logo 划分的 ARR、续约期限、NRR 或 GRR。公开案例研究很可能偏向成功故事,社区评论也确实显示一些成本和支持摩擦。最稳妥的结论是,客户质量看起来可信,而且可能是优势,但真正承销仍需要内部队列、集中度和流失数据。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CU022, CU023, CU024, CU025, CU026, CU036]
6.5 图表
07风险
7.1 主要公开风险是定价、依赖和不透明
Fivetran 最强的公开可见风险并不耸人听闻;它们在经济上严肃,在运营上也合理。第三方评论中反复出现对按用量计费的反弹,而对云、数据仓库、来源 API 和合作伙伴渠道的依赖则内嵌在商业模式里。同时,公开融资和运营披露仍不完整,放大了承销风险。即使产品真实、公司明显可行,这些风险也正是可能严重影响投资人的类型。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。从尽调角度看,本节的价值在于把分散的公开信号整理成后续章节可复用的底层事实。重点不是假装公开记录已经完整,而是说清楚哪些有证据支撑、哪些仍只是公司单方面说法,以及私下尽调最可能在哪些地方改写投资结论。[CR001, CR002, CR003, CR012, CR016, CR029]
| 风险 | 重要性 | 公开置信度 | 主要缓释措施 |
|---|---|---|---|
| 定价反弹 | 可能伤害转化、扩张和续约 | 高 | ELA 和基于价值的 ROI 证明 |
| 合作伙伴 / 平台依赖 | 品类建立在合作伙伴生态和源 API 之上 | 高 | 覆盖大量合作伙伴 |
| 隐私 / 合规失败 | 敏感数据流动抬高风险权重 | 高 | 安全与信任控制 |
| 估值不透明 | 追踪机构结论不一致,指标稀疏 | 高 | 要求提供私有财务包 |
| 并购执行 | 整合可能分散注意力或过度承诺 | 中 | 领导层延续性清晰 |
该表只纳入重大且有留存公开证据支撑的风险。
[CR001, CR002, CR004, CR012, CR013]| 问题 | 公开回答质量 | 已知信息 | 缺失信息 |
|---|---|---|---|
| 状态透明度 | 部分 | 存在公开状态页面 | 事故率和详细历史较弱 |
| 安全态势 | 强 | 列出大量控制和认证 | 实际泄露历史和审计发现 |
| 融资披露 | 弱 | 存在搜索表面 | 当前股权结构表 / 融资文件 |
| 客户风险指标 | 弱 | 存在评价表面 | 集中度、流失、SLA 索赔历史 |
该表把公开透明度和实际运营质量拆开。
[CR007, CR008, CR016, CR017, CR026]按发生可能性和影响程度,映射最高的剩余风险项。
[CR001, CR002, CR013, CR004, CR012]在下行情景中,核心商业模式依赖如何相互放大。
[CR001, CR002, CR015, CR028]7.2 安全、隐私、法律与监管执行极其重要
Fivetran 的核心工作是把客户数据搬过系统边界,这天然带来长期隐私与合规暴露。GDPR、HIPAA、客户隐私预期、SLA 和免费套餐规则都意味着,执行失误可能升级为合同、监管或声誉问题。好消息是,官方材料显示公司有几项扎实缓释:混合部署、私有网络、客户自管密钥,以及覆盖面很广的合规认证,其中包括 2026 年 HITRUST 公告。正确结论是:风险真实存在,但更像执行风险,不是鲁莽经营。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。[CR004, CR005, CR006, CR009, CR010, CR020]
7.3 运营透明度是局部的,不是全面的
Fivetran 的公开状态页显示,公司承认需要披露一部分可靠性信息,但可读的历史页面细节不够,无法量化宕机模式或 SLA 抵扣风险。保留下来的证据也没有发现重大且未解决的公开数据泄露新闻;但不能把这一点过度解读为事故暴露为零。客户集中度未知、留存未知、监管文件细节有限,意味着几类关键下行情景仍更像叙事,难以计量。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。[CR007, CR008, CR011, CR017, CR026, CR031]
可见控制措施能降低重大下行情景风险,但不能消除它们。
[CR006, CR009, CR007, CR030]7.4 关键问题是执行风险是否已经体现在价格里
最可能的下行情景是价格被压缩、支持摩擦、并购整合失手,以及市场对一个缺少公开经营分母的私募估值过度自信。短期看,这些问题都不致命。但如果投资人把激进留存和扩张假设写进模型,任何一项都足以打断后期估值逻辑。最强的反向缓释是,Fivetran 看起来服务的是任务关键环境,并配有严肃的信任控制。最终风险判断因此更接近「有执行风险,但不明显脆弱」。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。[CR013, CR014, CR015, CR021, CR027, CR028]
| 风险领域 | 应要求提供的指标 | 重要性 | 升级信号 |
|---|---|---|---|
| 定价 | 按 MAR 冲击队列拆分的 NRR 和总流失 | 量化账单冲击风险 | 中端市场或低 ACV 区间流失陡增 |
| 可靠性 | 事故数量和 SLA 抵扣 | 检验任务关键稳定性 | 抵扣上升或连接器反复故障 |
| 并购整合 | dbt 附着率和路线图滑期 | 检验战略执行 | 交叉销售疲弱或发布延迟 |
| 合规 | 审计例外和客户安全升级 | 检验信任态势 | 重大未解决发现 |
| 合作伙伴集中度 | 按数据仓库 / 云渠道拆分的收入 | 检验生态依赖 | 任何单一合作伙伴主导新 ARR |
这些尽调要求最能把叙事型风险画像转成可衡量指标。
[CR021, CR015, CR013, CR030, CR002]| 项目 | 公开解读 | 重要性 | 下一步尽调 |
|---|---|---|---|
| 商业模式 | 方向上可见 | 支撑章节判断 | 要求提供私有运营数据 |
| 客户证明 | 部分可见 | 显示需求是否持久 | 要求提供队列细节 |
| 风险 / 约束 | 有意义但不完整 | 会改变承销判断 | 要求提供更深入的尽调包 |
| 估值 / 规模锚点 | 只能部分观察 | 最终投资委员会观点需要该信息 | 与管理层数据核对 |
该表用于补齐计划中的成果物结构:公开证据已经存在,但源章节还需要一张综合表。
[CR001, CR002]对投资承销中最可能影响判断的风险领域,给出方向性严重度评分。
数值是分析师给出的序数严重度评分,不是事件概率。
[CR012, CR021, CR002, CR004, CR013]7.5 图表
08估值
8.1 公开估值明显上台阶,但具体价格仍有争议
Fivetran 现在的价值显著高于 2021 年官方 Series D 的 $5.6B 估值,这一点没有太大争议。争议在于高出多少。Caplight 和 PM Insights 支持 2026 年接近 $8.4B 至 $8.42B 的溢价估值;Stock Analysis / Hiive 指向的最后确认水平则明显更低。Tracxn 更新更慢,仍围绕旧的 2021 年图景,也放大了这个问题。也就是说,合格事件在方向上可信,但仅靠公开来源,确切入场价仍没有完全定案。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。[CV001, CV002, CV003, CV004, CV005, CV006]
| 来源 | 2026 信号 | 重要性 | 置信度 |
|---|---|---|---|
| Caplight | 投后估值约 $8.4B | 支撑较高的私募估值标记 | 中 |
| PM Insights | D-1 轮 $257.4M,估值 $8.42B | 与用户资格事件高度匹配 | 中 |
| Stock Analysis / Hiive | 上次确认估值 $5.87B,当前隐含值更低 | 提供下行情景标记和冲突 | 中 |
| Tracxn | 历史估值 $5.6B,累计融资 $730M | 显示追踪机构滞后 / 分歧 | 中 |
| 官方新闻稿 | 2020 年 $1.2B 和 2021 年 $5.6B | 坚实的历史锚点 | 高 |
该表有意透明呈现来源冲突,而不是强行给出虚假的单一真相。
[CV003, CV004, CV005, CV006, CV002]从 2020 年到 2026 年,公开和追踪器信号显示出的估值变化。
[CV001, CV002, CV004, CV005]仅基于公开证据给出的悲观、基准和乐观估值包络。
情景区间对这项高质量战略资产施加了披露折价。
[CV020, CV021, CV022, CV023, CV024]8.2 溢价为何说得通
相比规模更小、企业级准备不足的 ELT 工具,Fivetran 确实值得拿战略溢价。市场仍在增长,产品有严肃的信任控制,客户证据异常强,和 dbt 的合并又把故事从数据摄取扩到更宽的受治理数据工作流。合作伙伴覆盖广、生态适配度高,也提高了落地概率。合在一起,这些因素让「高质量后期资产」叙事站得住。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。[CV008, CV009, CV010, CV012, CV016, CV018]
| 支持因素 | 公开证明 | 值得给估值的原因 | 限制 |
|---|---|---|---|
| 类别增长 | 分析师市场报告 | 巨大且仍在扩张的 TAM | 定义口径不一 |
| 客户质量 | Gartner + 案例研究数量 | 支撑持久的企业需求 | 经济性仍未公开 |
| 信任态势 | 安全 / 信任触点 | 有助于受监管客户的 ACV 和留存 | 认证徽章不等于单位经济性 |
| 合并策略 | 与 dbt 合并 | 拿到更宽的工作流主导权 | 整合仍未验证 |
| 合作伙伴生态 | 云与市场触点 | 降低采用摩擦 | 也增加依赖 |
这些是不能只锚定跟踪平台数据低端的最强理由。
[CV008, CV009, CV010, CV016, CV031]在不同叙事和披露机制下,方向性的估值结果。
数值是分析师设定的情景锚点,不是观察到的市场出清价。
[CV013, CV021, CV020, CV022]以 IC 风格概括当前估值判断。
[CV008, CV018, CV011, CV023, CV025]8.3 当前估值为何仍显得偏高
溢价逻辑撞上的硬问题是:分母缺失。投资人仍看不到公开收入、利润率、留存或股权结构细节,而这些通常才足以支撑对 8B 以上入场估值的信心。价格压缩风险真实存在,更宽的平台正在逼近,较低的老股交易估值也近到不能忽视。组合起来,公司可以很优秀,但这个估值点仍显得偏贵。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。[CV011, CV013, CV014, CV015, CV019, CV029]
8.4 正确立场是谨慎乐观,并打披露折扣
公开记录支持的情景区间很宽,但仍可操作。乐观情景下,Fivetran 成为企业 AI 数据栈里可信的数据搬运与转换控制平面,估值靠近跟踪器高位区间。基准情景下,它是一项强资产,但仍应给披露折扣。悲观情景下,定价压力和弱于假设的留存,让跟踪器低位区间成为更好的锚。今天最安全的立场因此是观察,而不是追价。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。站在尽调角度,本节把零散公开信号整理成后续章节可复用的基础事实。重点不是假装公开记录已经完整,而是讲清哪些有证据支撑、哪些仍只是公司单方声称,以及私下尽调最可能在哪些地方改变投资结论。[CV020, CV021, CV022, CV023, CV024, CV025]
| 情景 | 隐含立场 | 必须成立的前提 | 指示性估值区间(USD B) |
|---|---|---|---|
| 悲观 | 高度谨慎 | 老股交易较低估值反映现实;定价压力和整合拖累显现 | 5.0-6.0 |
| 基准 | 持续跟踪 | 平台强,但披露折价仍在 | 6.5-7.5 |
| 乐观 | 战略溢价成立 | dbt 协同和企业扩张支撑持久溢价 | 8.0-9.0 |
情景区间是分析师范围,不是市场报价或管理层指引。
[CV020, CV021, CV022, CV023, CV025]8.5 图表
免责声明
本报告是基于公开证据的尽调快照,不构成投资建议。重要的财务、法律、技术和合同事实仍未公开;做出任何投资决定前, 应直接向管理层和一手文件核验。
证据索引
| 编号 | 陈述 | 可信度 | 来源 |
|---|---|---|---|
| CO001 | Fivetran says it was founded in 2012. | 中 | SO001 |
| CO002 | Fivetran publicly credits Raj Bhatnagar, George Fraser, Taylor Brown, and Jen Streicher as founders in the current company narrative. | 中 | SO001, SO012 |
| CO003 | The about page says the company went through Y Combinator in spring 2013. | 中 | SO001 |
| CO004 | Fivetran remains publicly headquartered in Oakland, California. | 高 | SO001, SO017 |
| CO005 | Fivetran says it now operates across ten international offices. | 中 | SO001, SO003 |
| CO006 | The company describes itself as an automated data movement platform rather than a narrow single-connector ETL tool. | 高 | SO002, SO004 |
| CO007 | Fivetran and dbt Labs completed their merger on 2026-06-01. | 高 | SO011, SO013 |
| CO008 | George Fraser stayed on as CEO after the dbt Labs merger while Tristan Handy became President. | 中 | SO011 |
| CO009 | Fivetran now markets the combined company as data infrastructure for trusted AI agents. | 中 | SO011, SO013 |
| CO010 | Fivetran documentation advertises 700-plus data integration connectors with setup guides. | 高 | SO028, SO005 |
| CO011 | The homepage currently says the platform supports 900-plus sources and destinations. | 中 | SO002 |
| CO012 | The clean way to reconcile current platform breadth is that 700-plus refers to documented connectors while 900-plus reflects the wider combined source-and-destination count. | 中 | SO002, SO028, SO005 |
| CO013 | Fivetran monetizes primarily on Monthly Active Rows and positions pricing as usage-based. | 高 | SO006, SO026 |
| CO014 | Pricing pages show Free, Standard, Enterprise, and Business Critical plan tiers. | 高 | SO006, SO026 |
| CO015 | Enterprise and Business Critical plans add higher-frequency syncs, deployment choice, and stronger security controls. | 高 | SO026, SO007 |
| CO016 | Fivetran supports hybrid deployment for customers that need data to stay in their environment. | 高 | SO007, SO004 |
| CO017 | The security surface includes SOC 1, SOC 2, GDPR, HIPAA BAA, ISO 27001, PCI DSS Level 1, and HITRUST references. | 高 | SO007, SO031, SO025 |
| CO018 | The platform supports AWS PrivateLink, Azure Private Link, Google Private Service Connect, and customer-managed keys. | 中 | SO007 |
| CO019 | Fivetran announced a $100M Series C in 2020 at a $1.2B valuation. | 中 | SO009 |
| CO020 | Fivetran announced a $565M Series D in 2021 tied to the HVR acquisition. | 中 | SO010 |
| CO021 | The 2021 Series D press release said total funding had reached $730M. | 中 | SO010 |
| CO022 | The 2021 Series D press release said the round valued Fivetran at $5.6B. | 中 | SO010 |
| CO023 | Caplight shows a 2026 post-money valuation signal around $8.4B. | 中 | SO014 |
| CO024 | PM Insights reports a May 2026 Series D-1 extension of roughly $257.4M at an $8.42B valuation. | 中 | SO015 |
| CO025 | Stock Analysis / Hiive instead shows a May 2026 Series D extension with last confirmed valuation of $5.87B and a lower current implied value. | 中 | SO016 |
| CO026 | Independent secondary-market trackers do not fully agree on Fivetran’s exact 2026 valuation level, so the current mark should be treated as indicative rather than settled. | 中 | SO014, SO015, SO016, SO017 |
| CO027 | Tracxn’s profile shows a materially larger employee estimate near 1,797, which is directionally higher than the user-provided 1,000-plus shorthand. | 中 | SO017 |
| CO028 | Fivetran said it had more than 5,000 customers by 2022. | 中 | SO001 |
| CO029 | The merger press release frames the combined Fivetran-plus-dbt ecosystem as serving more than 100,000 data teams. | 中 | SO011 |
| CO030 | Fivetran says the platform delivers 99.97% uptime. | 中 | SO004 |
| CO031 | The homepage says Fivetran syncs more than 2T rows per month. | 中 | SO002 |
| CO032 | The homepage says the platform syncs more than 9.1PB of data per month. | 中 | SO002 |
| CO033 | The homepage says Fivetran handles more than 33.5M schema changes per month. | 中 | SO002 |
| CO034 | The homepage says the platform runs more than 156.5M pipeline syncs per month. | 中 | SO002 |
| CO035 | Official and partner-domain pages confirm working routes through AWS, Snowflake, and Databricks. | 高 | SO030, SO019, SO029, SO020, SO027, SO021 |
| CO036 | Independent surfaces such as Gartner Peer Insights, FeaturedCustomers, GitHub, and partner listings show that the company has meaningful market visibility beyond its own website. | 中 | SO023, SO024, SO022, SO019 |
| CM001 | Precedence Research says the data integration market totals roughly $19.21B in 2026 and can grow past $51.8B by 2035. | 中 | SM001 |
| CM002 | Research and Markets projects the data integration market at roughly $33.24B by 2030 with a low-teens CAGR starting from the mid-2020s. | 中 | SM002 |
| CM003 | Integrate.io’s ETL market statistics place 2026 ETL spend in the high single-digit billions with strong double-digit growth. | 中 | SM004 |
| CM004 | Peliqan’s 2026 industry statistics also show a large ETL and data-integration category with ongoing double-digit expansion. | 中 | SM005 |
| CM005 | The analyst market-size figures vary materially because some definitions cover broad data integration while others isolate ETL or data-pipeline tooling. | 中 | SM001, SM002, SM004, SM005 |
| CM006 | Enterprise AI programs increase demand for governed, fresh, warehouse-ready data rather than raw API hookups alone. | 中 | SM025, SM006, SM020, SM021 |
| CM007 | Multicloud and cross-application sprawl make connector automation strategically relevant instead of a niche convenience feature. | 中 | SM022, SM020, SM021, SM017 |
| CM008 | Large enterprises are the core present-day spend base for data integration platforms because they run the most sources, compliance reviews, and analytic workloads. | 中 | SM005, SM003, SM018 |
| CM009 | SMB and mid-market segments grow quickly, but lower-cost and self-serve tools capture more of that spend than premium enterprise-managed platforms. | 中 | SM009, SM014, SM019 |
| CM010 | Regulated verticals such as financial services and healthcare remain important buyers because they need compliance and reliability alongside central analytics. | 中 | SM024, SM023, SM030 |
| CM011 | Typical buyers include data engineering, analytics engineering, platform, security, and IT leadership rather than line-of-business citizen developers alone. | 中 | SM006, SM007, SM011, SM018 |
| CM012 | Budget ownership usually sits with CIO, CDO, platform, or data-infrastructure functions even when analysts and business teams consume the outputs. | 中 | SM007, SM017, SM015 |
| CM013 | The strongest category pull comes from companies standardizing on Snowflake, Databricks, or similar cloud data platforms that need fast ingestion from SaaS and operational systems. | 中 | SM020, SM021, SM006 |
| CM014 | Managed ELT is most valuable where internal scripting would create ongoing schema-drift, monitoring, and connector-maintenance burden. | 中 | SM006, SM031, SM008 |
| CM015 | Open-source and self-hosted options such as Airbyte put clear price pressure on the lower and mid-market ends of the category. | 中 | SM008, SM009 |
| CM016 | Broader platforms such as Boomi, Informatica, Qlik Talend, and SnapLogic can win when procurement wants a single vendor for API, app, and data integration together. | 中 | SM017, SM018, SM015, SM016, SM032 |
| CM017 | dbt sits adjacent to Fivetran because it specializes in transformation and developer workflow rather than upstream connector extraction. | 中 | SM011, SM026 |
| CM018 | Reverse ETL and operational activation expand the data-movement budget but are still adjacent to the core ingestion category. | 中 | SM025, SM006, SM013 |
| CM019 | Growing demand for fresher analytics and AI use cases raises the value of more frequent syncs and lower-maintenance pipelines. | 中 | SM028, SM006 |
| CM020 | GDPR, HIPAA, and similar rules make governed movement and deployment choice a structural category tailwind. | 中 | SM023, SM024, SM030 |
| CM021 | Predictable total cost of ownership matters because buyers compare managed platforms against internal engineering time and unreliable scripts, not only license price. | 中 | SM007, SM014, SM010 |
| CM022 | Market definitions overlap with iPaaS, data fabric, workflow automation, and lakehouse tooling, so TAM figures should not be mechanically added together. | 中 | SM001, SM002, SM017, SM015 |
| CM023 | Cloud and warehouse partner channels are important because they reduce buyer friction and help vendors show platform legitimacy. | 中 | SM022, SM020, SM021 |
| CM024 | Fivetran’s practical serviceable market is narrower than the whole integration TAM because some buyers need broader application orchestration or cheaper self-hosted tools. | 中 | SM017, SM008, SM016 |
| CM025 | Despite definitional noise, every retained market source points to continued category growth rather than stagnation. | 中 | SM001, SM002, SM004, SM005 |
| CM026 | Source-system sprawl across SaaS apps, databases, files, and event systems keeps connector breadth economically valuable. | 中 | SM031, SM025 |
| CM027 | Schema changes are an operational cost center in the market, which is why automation remains a differentiated buyer pain point. | 中 | SM025, SM006 |
| CM028 | Deployment flexibility matters because some buyers need hybrid connectivity, network isolation, or stricter support boundaries. | 中 | SM030, SM028 |
| CM029 | The market is big enough for many vendors, but overlapping feature sets and transparent competitor pricing pages show pricing compression risk is real. | 中 | SM009, SM010, SM014, SM012, SM016 |
| CM030 | The 2026 AI-agent narrative expands the story from basic ELT toward more strategic data-infrastructure spend. | 中 | SM026, SM025, SM021 |
| CM031 | Reliability, trust, and governance are as important as raw connector count for enterprise buyers. | 中 | SM030, SM027, SM029 |
| CM032 | Once a company standardizes ingestion into a warehouse-and-dbt stack, switching vendors becomes operationally meaningful even if connectors are theoretically replaceable. | 中 | SM020, SM021, SM026 |
| CM033 | Citizen-developer workflow tools are adjacent but do not fully replace warehouse-grade ingestion for governed analytics teams. | 中 | SM017, SM013, SM019 |
| CM034 | Public materials do not provide a clean Fivetran-specific SAM or SOM, so the market chapter can size category opportunity but not exact company capture. | 中 | SM001, SM002, SM025 |
| CM035 | The 2026 macro evidence remains supportive because AI, multicloud, and data-governance demands all keep integration budgets strategic. | 中 | SM001, SM023, SM024, SM026 |
| CP001 | Fivetran’s core category is managed ELT and automated data movement into modern destinations. | 高 | SP001, SP002 |
| CP002 | Airbyte positions itself as open-source data integration and a context layer for AI agents. | 中 | SP004 |
| CP003 | Airbyte’s pricing surface emphasizes free/open-source entry and team/custom packaging that can appeal to self-hosted buyers. | 中 | SP005 |
| CP004 | Matillion competes with a transparent pricing page aimed at cloud data integration buyers. | 中 | SP006 |
| CP005 | dbt primarily owns transformation and analytics engineering workflow rather than upstream connector extraction. | 中 | SP008, SP009 |
| CP006 | Stitch now sits under the broader Qlik portfolio, which changes its positioning from independent startup to portfolio tool. | 中 | SP018, SP012 |
| CP007 | Qlik Talend markets a broader data-fabric and agentic data engineering story than Fivetran’s core ingestion pitch. | 中 | SP019, SP012 |
| CP008 | SnapLogic packages a broader integration and AI platform rather than a pure managed-ELT point solution. | 中 | SP013 |
| CP009 | Boomi also competes as a broader enterprise platform and data-activation company. | 中 | SP015 |
| CP010 | Informatica’s cloud data integration offering targets complex enterprise integration and governance needs. | 中 | SP016 |
| CP011 | Hevo markets directly into the ELT / pipeline category and highlights simpler, more predictable packaging. | 中 | SP010, SP011 |
| CP012 | Fivetran’s clearest strength versus DIY and open-source rivals is zero-maintenance managed connector operation with schema awareness. | 中 | SP001, SP002 |
| CP013 | Connector breadth remains a competitive strength because the company supports hundreds of documented integrations and a wider endpoint count on the homepage. | 中 | SP002, SP033 |
| CP014 | Enterprise trust controls such as hybrid deployment, private networking, and customer-managed keys help Fivetran compete above simpler tools. | 中 | SP034, SP032 |
| CP015 | Alignment with Snowflake, Databricks, and AWS remains a meaningful competitive advantage in warehouse-centric deals. | 高 | SP021, SP022, SP023, SP024, SP025 |
| CP016 | Public reviews and competitor commentary repeatedly frame Fivetran’s usage-based pricing as a competitive weakness. | 中 | SP029, SP030, SP003 |
| CP017 | Open-source and self-hosted rivals matter most where buyers prioritize cost control and deployment sovereignty over turnkey management. | 中 | SP004, SP005, SP029 |
| CP018 | Boomi, Informatica, Qlik Talend, and SnapLogic matter most when procurement prefers a single integration vendor across data and applications. | 中 | SP015, SP016, SP019, SP013 |
| CP019 | Internal build remains a real competitor for limited source counts or highly customized pipelines, especially where engineering talent is cheap relative to platform spend. | 中 | SP001, SP029 |
| CP020 | Fivetran’s Connector SDK and community connectors help reduce long-tail gaps versus open platforms. | 中 | SP026, SP027 |
| CP021 | The dbt merger makes the competitive story broader by linking ingestion with transformation and AI-ready data workflows. | 中 | SP008, SP031 |
| CP022 | Developer mindshare is structurally stronger for open-source entrants than for purely managed SaaS vendors. | 中 | SP004, SP027 |
| CP023 | Airbyte and Hevo are more likely to win cost-sensitive or self-serve mid-market deals. | 中 | SP005, SP011 |
| CP024 | Boomi, Informatica, and Qlik Talend are stronger where the buyer is modernizing a messy legacy integration estate rather than just a cloud analytics stack. | 中 | SP015, SP016, SP019 |
| CP025 | Matillion remains relevant where customers want integrated transformation productivity alongside data movement. | 中 | SP006 |
| CP026 | Stitch remains category-relevant historically, but its current public surface looks less central than Fivetran or Airbyte in 2026 category leadership. | 中 | SP018, SP012 |
| CP027 | Connector sync alone is vulnerable to commoditization if warehouses, open-source tools, or broader platforms deliver acceptable reliability at lower cost. | 中 | SP004, SP010, SP015 |
| CP028 | Competition often reduces to a trade-off between managed trust and operational ease on one side and lower cost or broader scope on the other. | 中 | SP003, SP005, SP015, SP011 |
| CP029 | Partner-domain pages give Fivetran stronger public proof of ecosystem distribution than many direct rivals expose on a single surface. | 高 | SP021, SP022, SP023, SP024, SP025 |
| CP030 | Fivetran is best differentiated in warehouse-centric enterprise ingestion, not general workflow automation. | 中 | SP001, SP021, SP022 |
| CP031 | Fivetran’s self-hosting story is weaker than Airbyte’s pure self-hosted identity even though hybrid deployment mitigates some regulated needs. | 中 | SP004, SP034 |
| CP032 | Competitor pages with more explicit packages and third-party critiques of MAR costs underscore a price-predictability gap in Fivetran’s sales story. | 中 | SP011, SP006, SP030, SP029 |
| CP033 | To keep premium pricing, Fivetran must continue proving better reliability, governance, and lower maintenance burden than cheaper alternatives. | 中 | SP001, SP002, SP003 |
| CP034 | Public materials do not disclose actual win rates by competitor or segment. | 中 | SP004, SP010, SP015 |
| CP035 | The retained public record still places Fivetran among the category leaders rather than a niche follower. | 中 | SP002, SP021, SP035 |
| CI001 | Fivetran prices primarily on Monthly Active Rows, making the model usage-based rather than seat-based. | 高 | SI001, SI002 |
| CI002 | Public plan tiers are Free, Standard, Enterprise, and Business Critical. | 高 | SI001, SI002 |
| CI003 | The Free plan acts as a product-led acquisition path with restricted scale and legal limits. | 中 | SI003, SI001 |
| CI004 | Enterprise and Business Critical tiers support higher ACV deals through sync frequency, deployment choice, and security controls. | 中 | SI002, SI004 |
| CI005 | Pricing pages promote annual commitments and ELAs as ways to increase predictability. | 中 | SI001 |
| CI006 | Because billing is tied to data activity, revenue can expand with customer usage growth but customer cost surprise risk rises too. | 中 | SI001, SI014, SI015 |
| CI007 | Multiple independent and competitor-adjacent reviews criticize Fivetran for high or hard-to-predict MAR-based costs. | 中 | SI014, SI015, SI016, SI017 |
| CI008 | Airbyte, Hevo, Matillion, and dbt expose alternative pricing models that can look simpler or easier to forecast. | 中 | SI018, SI021, SI019, SI020 |
| CI009 | Fivetran officially announced a $100M Series C in 2020 at a $1.2B valuation. | 中 | SI005 |
| CI010 | Fivetran officially announced a $565M Series D in 2021 at a $5.6B valuation. | 中 | SI006 |
| CI011 | The 2021 financing press release said cumulative capital raised reached $730M. | 中 | SI006 |
| CI012 | Independent trackers suggest total capital may now be higher than the last official $730M number. | 中 | SI009, SI010 |
| CI013 | Among independent secondary-market trackers, Caplight's 2026 signal places Fivetran's post-money mark at approximately $8.4B, the highest of three competing tracker estimates reviewed in this report. | 中 | SI007, SI006 |
| CI014 | PM Insights reports a May 2026 D-1 extension of about $257.4M at an $8.42B valuation. | 中 | SI008 |
| CI015 | Stock Analysis / Hiive reports a lower last confirmed May 2026 valuation mark of $5.87B and a still-lower current implied price. | 中 | SI009 |
| CI016 | Current tracker disagreement makes the 2026 financing mark directionally positive but financially noisy. | 中 | SI007, SI008, SI009 |
| CI017 | The reviewed public record does not provide a reliable official ARR or revenue run-rate figure. | 中 | SI001, SI006, SI007 |
| CI018 | No retained public source provides gross margin, operating margin, or burn-rate disclosure sufficient for a serious SaaS model. | 中 | SI007, SI009, SI010 |
| CI019 | No retained public source gives verified net revenue retention or gross revenue retention. | 中 | SI007, SI027 |
| CI020 | Publicly visible debt or filing detail is limited, despite tracker references to later financing events and credit investors. | 中 | SI011, SI012, SI013 |
| CI021 | AWS and cloud partner routes imply procurement and billing can flow through partner channels as well as direct sales. | 中 | SI022, SI023, SI024, SI025 |
| CI022 | Security-heavy packaging likely supports larger regulated enterprise ACVs than basic connector access alone. | 中 | SI002, SI004 |
| CI023 | Customer proof highlights concrete ROI claims such as HubSpot saving $100,000 with Fivetran. | 中 | SI029 |
| CI024 | Customer proof highlights concrete efficiency claims such as National Australia Bank cutting costs around 50% and raising ML accuracy. | 中 | SI030 |
| CI025 | The product surface claims the managed data lake service can cut ingestion costs by up to 95% versus self-managed landing. | 中 | SI028 |
| CI026 | If core customers keep centralizing more sources, Fivetran’s usage-based model has natural expansion leverage. | 中 | SI001, SI028 |
| CI027 | If customers aggressively optimize rows, consolidate tooling, or switch to cheaper rivals, usage-based revenue can flatten quickly. | 中 | SI001, SI014, SI018 |
| CI028 | Public cost critics focus on surprise bills, schema change volume, and rapidly rising MAR rather than on outright product failure. | 中 | SI014, SI015, SI016 |
| CI029 | ELAs and annual contracts are clear mitigation tools for customers worried about unpredictable monthly usage. | 中 | SI001 |
| CI030 | Pricing pages bundle a baseline amount of transformation runs, which shows the company is already monetizing beyond raw connector sync alone. | 中 | SI001 |
| CI031 | Business Critical features such as customer-managed keys and private networking likely monetize through higher enterprise package pricing. | 中 | SI002, SI004 |
| CI032 | The official 2021 Series D plus 2026 tracker marks imply continued private-market access even without audited public financials. | 中 | SI006, SI007, SI008 |
| CI033 | The absence of disclosed revenue, margin, burn, and retention means the financial case is still fundamentally opaque despite credible market momentum. | 中 | SI007, SI009, SI006 |
| CI034 | The safest hard public capital figure is still at least $730M, with some tracker sources implying more. | 高 | SI006, SI009, SI010 |
| CI035 | High tracker marks suggest confidence but do not by themselves prove unit-economics quality. | 中 | SI007, SI008, SI009 |
| CI036 | Without audited revenue denominators, any revenue-multiple discussion remains highly assumption-sensitive. | 中 | SI007, SI009 |
| CE001 | Fivetran’s core product is a managed platform that moves data from many sources into centralized destinations with limited customer maintenance. | 高 | SE002, SE001 |
| CE002 | Documentation advertises 700-plus connectors with setup guides. | 高 | SE005, SE003 |
| CE003 | The homepage advertises 900-plus sources and destinations. | 中 | SE001 |
| CE004 | The safest interpretation is that documented connectors are a subset of a broader endpoint taxonomy including destinations. | 中 | SE001, SE005 |
| CE005 | The platform explicitly markets schema-migration-aware automation and low-maintenance sync management. | 中 | SE002, SE001 |
| CE006 | Fivetran positions itself as destination-native and warehouse-centric rather than as a separate analytics database. | 中 | SE002, SE011, SE012 |
| CE007 | Hybrid deployment is a first-class part of the product story. | 高 | SE006, SE002 |
| CE008 | AWS PrivateLink, Azure Private Link, and Google Private Service Connect are all explicitly supported. | 中 | SE006 |
| CE009 | Customer-managed keys are part of the Business Critical security posture. | 中 | SE006, SE031 |
| CE010 | Official security surfaces list SOC 1, SOC 2, GDPR, HIPAA BAA, ISO 27001, PCI DSS Level 1, and HITRUST-related proof. | 高 | SE006, SE007 |
| CE011 | Security pages also emphasize region and support controls such as US-only support options and GovCloud positioning. | 中 | SE006 |
| CE012 | Fivetran presents data residency, region choice, and privacy controls as product features. | 中 | SE006, SE007 |
| CE013 | The company claims more than 2T rows synced per month, more than 9.1PB moved, and more than 156.5M syncs. | 中 | SE001 |
| CE014 | Fivetran claims 99.97% uptime and high-throughput sync performance on product pages. | 中 | SE002 |
| CE015 | The product now includes managed data lake landing / open table format capabilities alongside warehouse delivery. | 中 | SE002 |
| CE016 | The platform includes transformation and activation adjacency rather than raw sync alone. | 中 | SE030, SE002 |
| CE017 | The dbt merger broadens the product narrative toward governed transformation and trusted AI-agent workflows. | 中 | SE020, SE021 |
| CE018 | Fivetran has an explicit AWS product and partner story. | 高 | SE008, SE013 |
| CE019 | Fivetran has an explicit Google Cloud product and partner story. | 中 | SE009 |
| CE020 | Fivetran has an explicit Azure product and partner story. | 中 | SE010 |
| CE021 | Fivetran has an explicit Snowflake product and partner story. | 高 | SE011, SE014 |
| CE022 | Fivetran has an explicit Databricks product and partner story. | 高 | SE012, SE015 |
| CE023 | Fivetran publishes technical docs for building custom connectors in Python via the Connector SDK. | 高 | SE022, SE023 |
| CE024 | The company maintains GitHub repositories for the Connector SDK, a community connector catalog, and a Terraform provider. | 中 | SE025, SE026, SE027, SE024 |
| CE025 | The Connector SDK is distributed on PyPI, which supports a real developer-install surface. | 中 | SE028 |
| CE026 | The Terraform provider is evidence that infrastructure-as-code and platform automation matter in the product strategy. | 中 | SE027 |
| CE027 | Developer-search surfaces such as HN search show there is some ongoing external technical interest in the product and ecosystem. | 中 | SE029 |
| CE028 | The SDK, community connectors, and partner pages collectively show an ecosystem strategy rather than a fully closed product boundary. | 中 | SE022, SE026, SE011, SE012 |
| CE029 | Like all connector platforms, Fivetran remains exposed to third-party API changes, permissions breaks, and schema drift from source systems. | 中 | SE003, SE002 |
| CE030 | The main visible product moat is operational execution: keeping many connectors working reliably, securely, and with low customer maintenance. | 中 | SE002, SE003, SE006 |
| CE031 | Many performance and scale claims are company-reported rather than independently benchmarked. | 中 | SE001, SE002 |
| CE032 | The trust posture, deployment options, and compliance coverage support calling the platform mature for regulated enterprise use. | 高 | SE006, SE007, SE008 |
| CE033 | Warehouse and lakehouse partners are integral to the product value proposition rather than optional resale channels. | 中 | SE011, SE012, SE008 |
| CE034 | Fivetran’s commercial packaging indicates the company wants to own more of the activation and transformation workflow over time. | 中 | SE030, SE021 |
| CE035 | The AI-agent positioning is plausible because trusted data movement plus dbt transformation is a real workflow bridge, even if product revenue contribution is undisclosed. | 中 | SE020, SE021, SE002 |
| CU001 | Fivetran maintains a large public customer-story surface across many industries. | 中 | SU001, SU012 |
| CU002 | Pfizer is a named customer case that ties Fivetran to clinical-trial and healthcare data workflows. | 中 | SU003 |
| CU003 | National Australia Bank is a named customer case that ties Fivetran to financial-services analytics modernization. | 中 | SU004 |
| CU004 | Coke One North America is a named case with a public 35,000-user scale reference tied to SAP data access. | 中 | SU005 |
| CU005 | HubSpot publicly claims a $100,000 savings outcome tied to Fivetran. | 中 | SU002 |
| CU006 | LVMH is a named luxury-enterprise customer proof point. | 中 | SU007 |
| CU007 | Saks is a named retail and AI-enablement proof point. | 中 | SU006 |
| CU008 | Cemex is a named industrial customer with public scale language around 1,800-plus facilities. | 中 | SU008 |
| CU009 | Activision is a named gaming customer with marketing-workflow scale proof. | 中 | SU009 |
| CU010 | Adragos is a named manufacturing / life-sciences-adjacent proof point tied to faster insight and expansion. | 中 | SU010 |
| CU011 | Fountain is a named startup / SaaS proof point showing data-culture adoption. | 中 | SU011 |
| CU012 | The public customer set spans healthcare, banking, CPG, luxury, retail, gaming, manufacturing, and SaaS. | 中 | SU003, SU004, SU005, SU007, SU006, SU008, SU009, SU011 |
| CU013 | Healthcare and BFSI references show the product is acceptable to regulated buyers. | 中 | SU003, SU004, SU022 |
| CU014 | Some public cases show very large internal-user footprints rather than niche analyst teams. | 中 | SU005, SU008 |
| CU015 | Several public cases emphasize real-time insight and AI-related value rather than batch reporting alone. | 中 | SU003, SU004, SU006, SU002 |
| CU016 | Some customer cases include specific efficiency or cost outcomes rather than only brand logos. | 中 | SU002, SU004, SU009 |
| CU017 | FeaturedCustomers lists a large body of Fivetran case studies and customer stories from third parties. | 中 | SU012 |
| CU018 | Gartner Peer Insights provides an independent review surface for Fivetran in 2026. | 中 | SU013 |
| CU019 | Snowflake, Databricks, and AWS partner surfaces reinforce that customer deployments happen inside mainstream cloud-data ecosystems. | 高 | SU017, SU018, SU019, SU020, SU021, SU022 |
| CU020 | The typical public customer story starts with source consolidation, proves one analytics or operational workflow, then expands across teams. | 中 | SU001, SU011, SU005, SU004 |
| CU021 | The best named accounts look like production deployments, not lab experiments. | 高 | SU003, SU004, SU008, SU005 |
| CU022 | Because most proof comes from company-selected case studies, the public record is likely biased toward successful deployments. | 中 | SU001, SU002, SU003 |
| CU023 | The public record does not disclose customer concentration, ARR cohorts, or renewal mix. | 中 | SU001, SU013 |
| CU024 | There is no public NRR or GRR by customer segment in the retained evidence. | 中 | SU013, SU012 |
| CU025 | Repeated reference to major enterprise logos over time is a weak but directionally positive proxy for retention durability. | 中 | SU001, SU012 |
| CU026 | Community and review surfaces show some adverse customer commentary on cost and support, even though most named references are positive. | 中 | SU014, SU015, SU024, SU025 |
| CU027 | The customer references span North America, Europe, and APAC enterprises. | 中 | SU004, SU007, SU008, SU005 |
| CU028 | Customer proof aligns tightly with Snowflake / Databricks / cloud data platform use cases. | 中 | SU016, SU017, SU018 |
| CU029 | Public proof is stronger for enterprise and upper-midmarket buyers than for tiny self-serve users. | 中 | SU001, SU012 |
| CU030 | Because cases emphasize operational excellence, analytics, and AI, expansion likely occurs across functions rather than in a single dashboard team. | 中 | SU003, SU004, SU006, SU005 |
| CU031 | The customer proof surface supports calling Fivetran a mission-critical data pipeline component for many buyers. | 高 | SU003, SU005, SU008, SU004 |
| CU032 | FeaturedCustomers lists roughly 210 Fivetran case studies, success stories, or customer stories. | 中 | SU012 |
| CU033 | The Coke One case ties Fivetran to SAP-centric data consumption inside a very large enterprise workflow. | 中 | SU005 |
| CU034 | The LVMH and Saks cases extend customer proof beyond core analytics into luxury retail operations and AI-ready workflows. | 中 | SU007, SU006 |
| CU035 | Independent proof is meaningful but still thinner than the curated official case-study library, which is why reference checks remain necessary. | 中 | SU013, SU012, SU014 |
| CU036 | Overall, the public customer proof is a genuine strength even though it is not a substitute for cohort economics. | 中 | SU001, SU012, SU013 |
| CR001 | Usage-based MAR pricing is a repeated public risk theme because customers and competitors frame costs as hard to predict. | 中 | SR012, SR013, SR014, SR015 |
| CR002 | Fivetran depends heavily on cloud and warehouse partners for deployment fit, ecosystem reach, and customer value realization. | 高 | SR029, SR030, SR031, SR032, SR033, SR026, SR027, SR028 |
| CR003 | Connector businesses are exposed to source-API changes, schema drift, and permission changes that can break pipelines or increase maintenance cost. | 中 | SR001, SR002 |
| CR004 | Because Fivetran moves sensitive enterprise data, privacy and data-handling risk are structural to the business. | 高 | SR007, SR022, SR021 |
| CR005 | GDPR and HIPAA create real execution burden even when a vendor has strong controls. | 高 | SR022, SR021, SR001 |
| CR006 | Service levels, privacy terms, and usage rules create contractual exposure if performance or data-handling promises are missed. | 中 | SR008, SR007, SR009 |
| CR007 | Fivetran maintains a public status surface, which confirms uptime transparency is at least part of the operating model. | 中 | SR003, SR004 |
| CR008 | The fetched status history surface provides limited incident detail in readable form, so public reliability transparency remains incomplete. | 中 | SR004 |
| CR009 | Hybrid deployment, private networking, customer-managed keys, and certification coverage are meaningful risk mitigants. | 高 | SR001, SR002, SR010 |
| CR010 | The 2026 HITRUST announcement adds external trust evidence relevant to healthcare and other regulated buyers. | 中 | SR010 |
| CR011 | The retained public evidence did not surface a major current unresolved breach headline, but absence of evidence is not evidence of absence. | 中 | SR003, SR001, SR002 |
| CR012 | Current private-market valuation is risky to underwrite because public trackers disagree and operating disclosure is thin. | 中 | SR036, SR037, SR035 |
| CR013 | The dbt Labs merger creates integration, product-prioritization, and go-to-market execution risk. | 中 | SR011 |
| CR014 | Public adverse commentary also suggests support and cost-governance friction risk in some accounts. | 中 | SR019, SR020, SR015, SR013 |
| CR015 | Because Fivetran often sits in production analytics and operations workflows, outages can have high downstream business impact. | 中 | SR003, SR016, SR011 |
| CR016 | SEC and Form D search surfaces do not themselves provide a clean, investor-grade current financing package for Fivetran. | 中 | SR023, SR024, SR025 |
| CR017 | Unknown customer concentration and renewal quality are material residual risks because they can amplify pricing or outage issues. | 中 | SR016, SR008 |
| CR018 | Free-plan legal boundaries imply some product-led acquisition risk around abuse, conversion quality, and support overhead. | 中 | SR009 |
| CR019 | Channel routes through hyperscalers can aid sales but also increase dependency on partner policy and economics. | 中 | SR029, SR031, SR030, SR026 |
| CR020 | Strong certifications mitigate downside but do not remove the need for flawless execution in sensitive workloads. | 中 | SR001, SR002, SR022, SR021 |
| CR021 | Pricing dissatisfaction is one of the few public risks that could directly harm retention, expansion, or willingness to standardize. | 中 | SR012, SR013, SR015 |
| CR022 | A wide partner footprint creates resilience but also multiplies integration and support complexity. | 中 | SR029, SR030, SR031, SR032, SR033 |
| CR023 | Cross-border data movement, least-privilege access, and customer approval processes remain ongoing governance burdens. | 中 | SR007, SR001, SR002 |
| CR024 | The reviewed record clearly includes company legal pages plus independent regulatory materials sufficient to frame legal and regulatory risk categories. | 高 | SR006, SR007, SR008, SR009, SR022, SR021, SR023 |
| CR025 | Independent review surfaces are not outright negative, but they do not eliminate concerns about cost governance or support friction. | 中 | SR016, SR019, SR015 |
| CR026 | The public record does not provide a clean quantified incident frequency, breach rate, or SLA-credit history. | 中 | SR003, SR004, SR008 |
| CR027 | Most visible risks are execution, pricing, and underwriting risks rather than near-term existential survival risks. | 中 | SR001, SR011, SR016 |
| CR028 | The most plausible valuation breakers are pricing compression, failed merger monetization, or weaker-than-assumed retention. | 中 | SR013, SR011, SR016 |
| CR029 | Partner dependence, privacy obligations, and API fragility are structural risks baked into the business model. | 中 | SR029, SR007, SR022 |
| CR030 | The strongest visible mitigant is the combination of enterprise trust controls and real customer mission-critical adoption. | 高 | SR001, SR002, SR016 |
| CR031 | The largest risk problem for investors is that many downside cases are real but still weakly quantified in public. | 中 | SR004, SR016, SR024 |
| CR032 | The trust center publicly tracks external vulnerabilities and states whether Fivetran is impacted, which is useful but also highlights the steady security-monitoring burden. | 中 | SR002 |
| CR033 | The trust center states Fivetran was not impacted by several 2026 disclosed vulnerabilities including Apache Polaris issues and Linux Copy.Fail. | 中 | SR002 |
| CR034 | The trust center says Fivetran investigated the Salesloft Drift incident, rotated tokens, and found no evidence of misuse. | 中 | SR002 |
| CR035 | Security FAQs say employee access to customer data requires customer approval, which is a strong mitigant but also an operational support dependency. | 中 | SR001 |
| CR036 | Cloud-provider and region-selection flexibility is valuable but also increases configuration and support complexity across deployments. | 中 | SR001 |
| CR037 | The G2 review page was access-blocked in this run, which itself illustrates that independent reputation triangulation is not frictionless. | 中 | SR017 |
| CR038 | The LinkedIn company page was blocked in this run, which limits easy independent triangulation of current workforce scale. | 中 | SR018 |
| CR039 | The legal hub encourages subscription to policy updates, signaling that customer obligations and terms can change over time. | 中 | SR006 |
| CR040 | The existence of an SLA creates exposure to service credits or disputes, but the public record does not reveal how often credits are actually paid. | 中 | SR008, SR004 |
| CR041 | Marketplace and partner policy changes could alter customer acquisition economics even if core product demand stays healthy. | 中 | SR026, SR029, SR031, SR030 |
| CV001 | Fivetran’s official valuation path includes a $1.2B Series C mark in 2020. | 中 | SV007 |
| CV002 | Fivetran’s official valuation path includes a $5.6B Series D mark in 2021. | 中 | SV008 |
| CV003 | Caplight's secondary-market data implies Fivetran's equity value has appreciated well beyond the 2021 $5.6B anchor, with the Caplight signal converging around $8.4B as the highest independent estimate for the 2026 valuation assessment. | 中 | SV001, SV002 |
| CV004 | PM Insights reports a May 2026 D-1 extension of about $257.4M at an $8.42B valuation. | 中 | SV002 |
| CV005 | Stock Analysis / Hiive shows a lower last confirmed 2026 valuation mark of $5.87B and a still-lower implied price. | 中 | SV003 |
| CV006 | Tracxn still surfaces the older $5.6B valuation and $730M total-raised framing, underscoring imperfect tracker synchronization. | 中 | SV004, SV005 |
| CV007 | The 2026 current valuation is directionally above the 2021 official mark but not precisely settled by public evidence. | 中 | SV001, SV002, SV003, SV004 |
| CV008 | The broader data-integration market still supports a growth premium because retained analyst sources all show category expansion. | 中 | SV012, SV013, SV014 |
| CV009 | Customer proof, review surfaces, and trust posture support paying a premium to smaller or less enterprise-ready ELT vendors. | 高 | SV028, SV029, SV035 |
| CV010 | The dbt merger supports a strategic-premium narrative because it broadens the value chain from ingestion into governed transformation and AI workflows. | 中 | SV009, SV031 |
| CV011 | The biggest valuation discount factor is the absence of public revenue, margin, and retention denominators. | 高 | SV001, SV003, SV010 |
| CV012 | Official financing history and later secondary interest imply late-stage private-market maturity rather than financing stress. | 中 | SV008, SV001, SV002 |
| CV013 | Pricing backlash and lower-cost alternatives imply multiple compression risk if growth or retention disappoints. | 中 | SV010, SV023, SV022 |
| CV014 | Broader platform competitors show that buyers pay for governance and scope, which can justify some premium for Fivetran’s enterprise posture. | 中 | SV017, SV019, SV021 |
| CV015 | Stitch / Qlik-style portfolio competition shows how quickly once-hot data tools can be absorbed into broader suites, which is a warning against overpaying. | 中 | SV020, SV021 |
| CV016 | Partner breadth across clouds and data platforms adds strategic value because it lowers adoption friction and broadens distribution. | 中 | SV032, SV026, SV027 |
| CV017 | Careers, trust, and ecosystem surfaces imply a company operating at meaningful scale, even though exact current headcount is undisclosed. | 中 | SV033, SV035 |
| CV018 | Public customer surfaces suggest a high-quality enterprise customer base, which tends to support better renewal durability than commodity tooling. | 中 | SV028, SV029 |
| CV019 | Public filing search surfaces still do not settle the 2026 financing package cleanly. | 中 | SV036, SV038, SV006 |
| CV020 | The bull case is that Fivetran becomes the trusted data-movement layer inside a broader dbt-led workflow stack and deserves a premium mark near the high tracker range. | 中 | SV009, SV035, SV029 |
| CV021 | The base case is that Fivetran is a strong enterprise platform but should trade with a disclosure discount until private operating metrics are shared. | 中 | SV001, SV028, SV010 |
| CV022 | The bear case is that pricing pressure, merger integration risk, and lower secondary marks imply that the 8.42B qualification event overstates realizable equity value. | 中 | SV003, SV037, SV009 |
| CV023 | On current public evidence, the 8.42B mark looks stretched rather than obviously attractive. | 中 | SV002, SV003, SV010 |
| CV024 | Confidence in any point estimate should be only medium to low because public evidence is incomplete and conflicting. | 中 | SV001, SV003, SV006 |
| CV025 | The most defensible current stance is to track the company rather than chase the mark without private materials. | 中 | SV002, SV003, SV035 |
| CV026 | At minimum, official disclosed capital raised is $730M, with trackers implying more since then. | 高 | SV008, SV004, SV003 |
| CV027 | The continued existence of secondary-market trackers implies ongoing investor and employee-liquidity interest. | 中 | SV001, SV003 |
| CV028 | The scale narrative implies some IPO optionality, but the public record does not yet provide IPO-grade disclosure. | 中 | SV030, SV035, SV034 |
| CV029 | Governance and cap-table opacity deserve an explicit valuation discount alongside financial opacity. | 中 | SV006, SV005 |
| CV030 | Without disclosed revenue, valuation is extremely sensitive to whatever revenue multiple an investor privately assumes. | 中 | SV001, SV012 |
| CV031 | A premium to simpler ELT tools is plausible because Fivetran’s product and customer proof are stronger. | 中 | SV028, SV029, SV035 |
| CV032 | That premium should still be limited because the business remains exposed to category pricing compression and platform overlap. | 中 | SV010, SV023, SV017 |
| CV033 | Public valuation trackers update on different schedules and methodologies, which is why identical company facts still produce different current marks. | 中 | SV003, SV004, SV006 |
| CV034 | Grand View Research pages were blocked in this run, limiting clean triangulation from another common market-data provider. | 中 | SV015, SV016 |
| CV035 | Marketplace and cloud-distribution surfaces increase strategic value because they can shorten procurement and improve enterprise reach. | 中 | SV027, SV032, SV026 |
| CV036 | Secondary-market trackers imply a real liquidity surface for employees and investors, which is normal for a mature late-stage asset. | 中 | SV001, SV003, SV006 |
| CV037 | Broader data-platform vendors and clouds could view Fivetran as strategically relevant because it already sits inside many enterprise data estates. | 中 | SV017, SV019, SV032 |
| CV038 | The existence of broader suite vendors implies a ceiling on how much premium a single-category ingestion asset can sustain. | 中 | SV017, SV021, SV024 |
| CV039 | Competitor pricing and packaging pages are often more transparent than Fivetran’s full realized-cost picture, which weakens valuation confidence. | 中 | SV018, SV023, SV010 |
| CV040 | A company with this level of trust, partner, and hiring surface likely commands some organizational-scale premium even before precise revenue is known. | 中 | SV033, SV035, SV032 |
| CV041 | Tracker activity shows interest, but it does not prove deep, broad secondary liquidity at the headline price. | 中 | SV001, SV003 |