最近融资 01
$125M Series C [CO007] 尽调报告
Tines
处于泛企业拐点的 AI 驱动工作流自动化平台
Tines 由创始人掌舵，已在企业客户中跑出工作流自动化业务，AI 原生产品和渠道也在扩张；机会不小，但当前估值已计入持续兑现的预期。
覆盖范围与披露说明
本分析仅以 2026-09 本轮更新可用的初始缓存与抓取源文本为凭。ARR、员工数与部分客户指标来自第三方估计或公司自述口径，未经独立审计。报告特意将确切毛利率、烧钱速度、现金跑道、NRR 及董事会构成，列为待查实的尽调未决事项。
封面要素
公司概况
Tines 创立于 Dublin，最初从安全运营切入工作流自动化，如今正借 Stories 和新推出的 AI 原生产品 3B 拓展至更广泛的企业自动化。公司由创始人掌舵、资金充足，渠道在增长中扮演越来越重要的角色；安全、IT 及相邻企业工作流领域已有客户案例支撑。
- 成立时间
- 2018-01-01
- 创始人
- Eoin Hinchy, Thomas Kinsella
- 创立地点
- Dublin, Ireland
- 总部
- Dublin, Ireland (European HQ); Boston, USA (US HQ)
- 产品
- 面向安全及企业团队的 AI 原生工作流自动化平台，包含 Stories、3B、治理仪表盘、集成和受控执行。
- 客户
- 安全运营、IT 运维、合规、财务、HR 及其他企业工作流团队。
- 商业模式
- 以年度软件订阅为主，面向企业打包销售，并通过合作伙伴和渠道拓展；工作流、AI 用量及治理功能另有模块化附加组件。
- 阶段
- Series C (Unicorn)
- 融资情况
- 2025 年 2 月完成 $125M Series C 融资，估值 $1.125B；累计融资约 $272M。
执行摘要
主要优势
- 创始人主导产品，公司从安全运营切入、向企业自动化扩张的路径清楚
- 非上市阶段已跑出规模：收入 / ARR 约 $85M，估值锚点为 $1.125B
- 渠道势头强：一份 2026 年报告称新增 75 家合作伙伴，超半数同比收入与合作伙伴相关
- 3B 在保留治理和安全控制的同时，将目标市场拓展到 SOC 之外
- 客户案例覆盖安全、IT 及其他企业工作流团队
主要风险
- Stories 转向 3B 若执行不顺，可能让买方困惑或分散团队重心
- 估值仍偏高，约为收入 / ARR 的 13 倍；毛利率和烧钱情况均未公开
- 竞争对手扩展至通用工作流平台、开源核心方案和智能体 SOC 厂商
- 治理、董事会构成和客户留存仍有部分不透明
- 渠道增长若不均衡，合作伙伴集中度可能变成业务依赖
未决问题
- 毛利率、烧钱速度和现金跑道尚未公开
- 缺少经独立确认的 NRR 和客户流失队列数据
- 创始人以外的董事会构成仍不透明
- 3B 的具体定价与转化率未公开
- 长期留存证据目前仍主要来自客户案例
目录
01公司概况
1.1 定位、使命与运营模式
Tines 最初为安全运营提供无代码自动化，如今将自己定位为服务 AI Agent、应用和企业自动化的智能工作流平台。对外叙事始终围绕两点：减少重复劳动，让操作者掌握治理权。Stories 与 3B 不只是功能更新，而是两种不同的构建、部署和控制方式。3B 面向财务、HR、运营等不想学习旧式搭建器的团队，也因此把目标市场扩至安全之外。产品一边是安全优先，一边是 AI 原生，但两者都强调治理。[CO001, CO003, CO004, CO005]
| 指标 | 数值 | 截至日期 | 置信度 | 证据缺口 |
|---|---|---|---|---|
| 成立时间 | 2018 | 2018 | 高 | 无 |
| 主要总部布局 | Dublin + Boston | 2026-09 | 高 | 确切法人实体分布未公开披露 |
| Series C 轮估值 | $1.125B | 2025-02 | 高 | 无 |
| 累计融资金额 | ~$272M | 2025-02 | 高 | 不同来源存在微小四舍五入差异 |
| ARR / 收入运行率 | ~$85M | 2025-10 | 中 | 第三方估计 |
| 员工数 | 506-548 | 2025-2026 | 中 | 不同第三方估计存在差异 |
| 客户 / 用户数 | ~33,000 | 2025-2026 | 中 | 公开披露的客户数未经独立审计 |
数据来源包含公司材料、投资方新闻稿及第三方估计；员工数与 ARR 因来源不同略有差异。
[CO001, CO007, CO008, CO014]关键里程碑展示公司从安全自动化初创企业演变为企业级 AI 工作流平台的历程。
Series A 轮 / 早期支持 [CO009]
2024 年 Series B 轮增资 [CO009]
Series C 轮独角兽融资 [CO007, CO008]
2025 年规模拐点 [CO005]
Tines 3B 发布 [CO004]
1.2 创始人、融资历程与业务规模
Tines 仍由创始人掌舵，融资充足。公司于 2025 年 2 月完成 $125M Series C 融资，估值 $1.125B，并称累计融资约 $272M。第三方估计营收约 $85M、员工人数在 500 人出头；公司材料称平台每周处理超过十亿次自动化动作。ARR 已有一定规模，估值达到独角兽水平，但公司仍是非上市企业。本轮尽调的重点因此是验证增长能否延续，而非确认产品是否存在；现有信息足以将其视为成长型公司，但仍有问题待查。[CO006, CO007, CO008, CO009, CO010, CO014, CO013]
| 相关方 | 角色 | 核心意义 | 尽调关注点 |
|---|---|---|---|
| Eoin Hinchy | CEO 兼联合创始人 | 负责制定战略愿景，为主要对外发言人 | 核实梯队建设与接班人深度 |
| Thomas Kinsella | COO 兼首席客户官 | 主抓客户与日常运营落地 | 明确各项运营权责划分 |
| Jessica Degenhardt | 美洲区渠道合作伙伴负责人 | 标志着公司正正式发力渠道扩张 | 核实管辖范围与具体 KPI |
| Goldman Sachs Alternatives | Series C 轮领投方 | 成长期主力投资方，体现较强的资本获取能力 | 核实董事会席位及核心交易条款 |
| SoftBank Vision Fund 2 | Series C 轮参投方 | 引入全球资本，支持公司的 AI 战略逻辑 | 确认后续战略层面的实际参与度 |
| Accel / Felicis / CrowdStrike / Addition | 持续跟投方 | 多轮跟投，展现投资方对公司的长期认可 | 确认后续轮次的跟投意向 |
鉴于董事会完整构成未公开，此利益相关方图谱作了针对性精简，聚焦本轮更新凭证中可考的核心主体。
[CO002, CO007, CO011, CO013, CO015]1.3 发展里程碑、渠道势能与治理缺口
2026 年的更新在融资和产品进展之外，补上了渠道增长信号，也记录了渠道负责人任命。Tines 报告新增 75 家技术合作伙伴、渠道网络增长 25%，并称超过 54% 的同比收入由合作伙伴带动。这是重要的商业信号，但治理信息仍不完整：公开记录没有清楚列出创始人以外的董事会成员。公司还处于重大产品转型期，执行质量和增长速度同样重要。对外定位虽在拓宽，原有的安全切入点仍在。[CO011, CO012, CO013, CO015]
| 年份 / 日期 | 关键里程碑 | 核心意义 |
|---|---|---|
| 2018 | 在 Dublin 成立 | 体现创始团队与安全自动化市场的契合 |
| 2024-04 | $50M Series B 轮追加融资 | 表明投资方持续支持，ARR 也在增长 |
| 2025-02 | $125M Series C 轮融资，估值 $1.125B | 估值达到独角兽级别，业务规模迈上新台阶 |
| 2026-04 | 新增 75 家合作伙伴并任命渠道负责人 | 商业化逐步走出最初的安全切入点，覆盖更多场景 |
| 2026-07 | 推出 3B | 平台不再局限于原有无代码构建器，产品范围进一步扩大 |
里程碑脉络基于公开信息浓缩提炼，旨在勾勒主线，不求面面俱到。
[CO001, CO007, CO009, CO011, CO013, CO004]02市场分析
2.1 市场边界与细分板块
Tines 的市场已不止“安全编排”。其智能工作流软件把自动化、AI、治理和集成结合起来，覆盖安全运营、IT、合规及相邻业务流程；这也更符合 Stories 与 3B 的产品组合。与其把市场看成单一垂直工具，不如视作跨系统工作的控制层，尤其适用于需要审计的流程。它还包括对 AI 生成工作的治理，而非只有传统安全编排。平台既服务原有安全买方，也试图借 3B 触达更广泛的企业买方。[CM001, CM002, CM004, CM010]
| 细分板块 | 纳入的支出范畴 | 排除的支出范畴 | 买方 / 使用者 | 相关度 |
|---|---|---|---|---|
| 智能工作流平台 | 工作流编排、AI 治理、系统集成、可审计性 | 纯 BI、纯 RPA、单点脚本 | 安全、IT、平台工程 | 核心市场 |
| SOAR / 安全自动化 | 分流排查、告警上下文丰富、事件响应、工单流转 | SIEM 存储、终端工具 | SOC / IR 团队负责人 | 起家切入点 |
| IT / 企业通用自动化 | 入职流转、身份管理、合规审计、RevOps 工作流 | 传统 ERP 定制开发 | IT 运维 / 业务运营 | 横向拓展市场 |
| AI 治理层 | 访问控制、操作日志、模型路由、安全护栏 | 消费级 AI 工具 | 安全 / 平台工程团队 | 3B 主攻增量航道 |
| 现状替代工具 | 自写脚本、电子表格、简易 Bot | N/A | 所有团队 | 主要替代品 |
| 自研系统 | 自定义 Python、内部封装服务、自研编排引擎 | N/A | 工程研发团队 | 关键竞品 |
市场边界立足实证，适度覆盖 Stories、3B 及邻近工作流场景。
[CM001, CM002, CM010, CM011]定性划分市场梯层，展示 Tines 的核心优势阵地以及尚在推进的扩张领域。
各层宽度仅表示层级，不代表数值比例。
仅展示相对侧重点，并非数值化的 TAM 估算。
[CM001, CM002, CM004, CM005, CM008, CM011]2.2 需求驱动因素与采纳阻碍
需求来自熟悉的运营痛点：团队想减少重复劳动、防止影子 AI，并在跨系统工作中保留治理。Tines 的研究和客户案例提到员工倦怠、告警疲劳及交接成本。但采用并非毫无阻力，买方还要判断它相对脚本、SOAR 和其他自动化工具的定位；部署通常从一个团队开始，再逐步扩展。因此，市场增长取决于平台能否证明控制力并快速体现价值。买方往往先在一个领域试用，确认平台能安全替代跨系统的人工交接后，才扩展到相邻团队。[CM003, CM005, CM007, CM008, CM011]
| 细分板块 | 买方决策人 | 实际使用者 | 预算归属方 | 采纳触发点 |
|---|---|---|---|---|
| 安全运营 | SOC 负责人 / CISO | 分析师 | 安全预算 | 告警疲劳 |
| IT 运维 | IT 负责人 | IT 管理员 | IT 预算 | 入职流程繁琐与权限管理痛点 |
| 合规审计 | 风控 / 合规负责人 | 内控负责人 | GRC 预算 | 审计合规压力 |
| 财务 / RevOps | 职能负责人 | 核心业务能手 | 部门独立预算 | 跨部门手工交接低效 |
| HR / 人力运营 | 人力运营负责人 | 运营一线员工 | 共享服务预算 | 员工全生命周期管理工作流 |
| 平台 / 应用搭建团队 | 工程研发 / 平台负责人 | 应用构建者 | 工程研发预算 | 需要受管控的 AI 应用 |
买方画像偏向趋势指引，兼顾公司起家的安全买方与 3B 面向的泛企业买方。
[CM002, CM004, CM005, CM008, CM011]2.3 空间测算佐证与待解问题
现有市场空间判断主要依靠间接指标。缓存中有增长信号，却没有数据扎实的 TAM、SAM、SOM 模型。这不妨碍投资判断，但估值应更多看实际 ARR、留存、渠道杠杆和部署深度，而不是一张看似精确的市场规模图。尽调更该问的不是“市场能有多大”，而是“Tines 能安全承接多少工作流，才会从功能走向基础设施”。答案应来自情景分析和用量证据，而非凭空给出一个 TAM 数字。[CM006, CM009, CM012]
| 透视维度 | 本轮凭证支持的事实 | 具体数值 / 信号 | 局限性 |
|---|---|---|---|
| 人员疲倦 / 手工重复劳动 | 安全人员 44% 的时间耗在手工流程；76% 感到职业倦怠；81% 工作量持续增加 | 强劲的需求拉动力 | 委托开展的调研，不能代表 TAM |
| 工作流库使用情况 | 数百个预构建 Stories，且多篇客户案例交叉印证 | 使用密度较高 | 仅凭工作流库使用情况，不能估算市场规模 |
| 合作伙伴拓展 | 新增 75 家合作伙伴；渠道网络增长 25%；超过 54% 的同比收入来自合作伙伴 | 渠道分销显著放大触达范围 | 仍属未上市口径，由公司自述 |
| 营收侧指标 | ARR / 营收约 $85M | 说明公司已达到一定变现规模 | 仅体现自身体量，非行业空间 |
| 竞争密集度 | Tracxn 数据列出 96 家活跃竞品 | 赛道相对拥挤 | 无法量化具体支出规模 |
| 测算结论 | 未披露直接的 TAM 数据 | 宜采用情景推演做测算 | 需依赖明确的尽调前提假设 |
本表为观察维度切片，非精准的市场规模模型；所列数值来自零散佐证，并非单一测算结论。
[CM003, CM006, CM008, CM009, CM012]03竞争格局
3.1 竞争全景
3B 推出后，Tines 面对的竞争范围扩大了：除传统 SOAR 外，还有智能体 SOC 厂商、开源核心方案、工作流平台和企业 AI Workspace。进入更大的市场是机会，也意味着买方比较的产品更多。买方可以选择工作流构建器、AI SOC 分析工具、开源控制栈或企业自动化平台；这些产品分别侧重自主调查、工作流灵活性或开源核心的成本结构。品类因此更难界定，但横向比较也更有意义。[CP001, CP002, CP005, CP009]
| 竞品 / 阵营 | 产品品类 | 规模 / 融资体量 | 目标客群 | 差异化优势 | 主要短板 |
|---|---|---|---|---|---|
| Tines | 工作流平台 / 智能工作流 | 累计融资 $272M；独角兽 | 安全 + IT + 泛企业部门 | 强管控兼具场景广度 | 毛利等财务数据仍不透明 |
| D3 Morpheus | 智能体 SOC | 深耕 SOC 的垂类厂商 | 安全团队 | 开箱自带排查分析能力 | 走出 SOC 场景后适用度有限 |
| Tracecat | 开源安全自动化 | 开源社区 + 企业商业化 | AI 原生安全团队 | 开源生态并支持 MCP | 品牌知名度尚显薄弱 |
| SynapCores | Open-core 架构 SOAR | 按席位收费的 Open-core | SOC / MSSP | 不按自动化执行次数加收费用 | 市场新入局者 |
| Workato | 工作流自动化 | 大型老牌厂商 | 企业 IT / 运营团队 | 企业熟悉的成熟自动化底座 | 客户案例反映其受限于价格与变更管控能力 |
| Sim / AI 工作空间 | 邻近的 AI Workspace | 初创企业体量 | 企业内部构建者 | 工作空间覆盖面更宽 | 缺乏安全深度积累 |
| 传统 SOAR / 老牌厂商 | SOAR 套件 | 大型老牌厂商 | SOC 团队 | 存量客户深厚且擅长产品捆绑 | 交互体验陈旧，创新迭代放缓 |
规模与定位依据本轮更新凭证推断；本表旨在展现买方的真实比选组合，而非给出精确的市占率。
[CP001, CP005, CP006, CP007, CP008]3.2 能力与定价对比
比较产品时，关键是由谁编写调查逻辑或工作流，以及买方能保留多少控制权。Tracecat 和 SynapCores 主打开源或开源核心模式；Tines 强调受治理的工作流创建和运行时控制。客户案例显示，Workato 曾是替代选择，但价格和变更控制限制了团队的使用。Sim 等 AI Workspace 也在进入相邻市场。买方要同时权衡控制力、自主性和成本，因此选型不仅看功能，也看商业模式、治理和编写方式。[CP003, CP004, CP006, CP007, CP008, CP011]
| 选型采购标准 | Tines | 开源核心 / Tracecat / SynapCores | 智能体 SOC 厂商 | 现状 / 内部自建 | 研判结论 |
|---|---|---|---|---|---|
| 谁来编写业务逻辑？ | 客户自身团队，带管控机制 | 客户自身团队，掌握更多源代码控制权 | 厂商承担更多调查逻辑编写 | 内部工程师 / 分析师 | 核心架构路线抉择 |
| 运行时自主性 | 带安全护栏的 AI + 工作流 | 视版本而定 / 开源核心 | 产品设计上自主性更高 | 手工操作 | 直接影响信任度与人员配置 |
| 管控治理 / 审计能力 | 高度重视 | 取决于版本 | 通常深嵌于 SOC 场景 | 临时拼凑 | 企业买方极度看重 |
| 定价策略 | 模块化 / 未公开 | 按席位计费或开源 | 通常按订阅 / 用量计费 | 仅承担内部研发成本 | 预算压力成为决策关键 |
| 安全之外的横向扩展 | 随 3B 推出而持续扩张 | 参差不齐 | 通常范围更窄 | 能力上限高，但需要定制开发 | Tines 具备横向扩张上行空间 |
| 部署运维负担 | 厂商托管 SaaS | SaaS 或自托管 | 通常为 SaaS | 完全内部自担 | 较低运维负担有利于 Tines |
表格内容提炼自公开定位及竞品对比页面；缺乏公开支持的单元格刻意做了概括处理。
[CP002, CP003, CP004, CP009, CP010]| 厂商 / 模式 | 公开打包方案信号 | 商业模式信号 | 核心结论 |
|---|---|---|---|
| Tines | 模块化打包 / 未公开目录标价 | 典型企业级软件商业模式 | 必须凭价值取胜，无法靠低价竞争 |
| Tracecat | 开源 + 企业版模块 | 开源核心商业模式 | AI 原生团队的替代方案 |
| SynapCores | 按分析师席位计费，不收单次操作费 | 按席位付费商业模式 | 若自动化密度高则成本更低 |
| Workato | 定价约束了团队构建工作流的范围 | 对价格高度敏感 | 具警示意义的替代参照 |
| D3 Morpheus | 订阅制 / 平台价格包含 AI 能力 | AI 已包含在平台订阅价格中 | 调查能力开箱即用 |
| Sim / 相邻工作区 | 通用 AI 工作区打包方案 | 更广泛的平台捆绑包 | 主打产品广度竞争 |
定价刻意以打包方案信号呈现，因各对比厂商均未公开确切目录价。
[CP004, CP006, CP007, CP011]3.3 护城河与潜在威胁
Tines 的差异化更多来自架构和治理，而不是某个独有功能或低价。公司将 3B 定位为应对 AI 泛滥和影子 AI 的方案，这一优势也要放到更广的市场中检验。最大威胁是产品同质化：若其他技术栈能以更低成本提供足够的自动化、智能体能力或控制力，Tines 就得靠执行和信任取胜。未来一年的关键是拿出落地证据，而非继续讲定位。竞争格局还会快速变化，目前只能视作一张快照。AI 生成的工作越多，治理和运行时控制相较于搭建速度就越重要。[CP010, CP012]
04财务情况
4.1 收入模式与商业化变现
Tines 的模式接近典型企业软件：以免费入口获客，通过企业方案收费，并借日益壮大的渠道拓展销售。公开资料没有列出各层级的完整标价，但显示收入主要来自软件订阅，而非依赖大量服务交付。Stories 和 3B 产品线并存，不能只按席位许可来理解其变现方式。关键是新产品能否提高单位客户收入，而不把套餐弄得过于复杂。整体看，它更像有多种收费入口的软件平台，而不是单一席位计费产品。[CI001, CI002, CI006, CI010]
| 收入流 | 运作机制 | 计费单元 | 当前规模 / 状态 | 收入质量 | 尽调重点问询 |
|---|---|---|---|---|---|
| 社区版 / 入门版 | 免费获客漏斗 | 工作区 / 用户 | 公开免费；具体额度未披露 | 利于自下而上普及 | 转付费转化率如何？ |
| 企业级订阅 | 年度软件订阅 | 合同 | 核心变现引擎 | 高质量经常性收入 | 典型客单价多大？ |
| 渠道主导交易 | 合作伙伴获客 / 转售 / 联合销售 | 合作伙伴贡献 ARR | 一份 2026 年报告称，超过一半的同比收入来自合作伙伴 | 若能持续，渠道杠杆效应较强 | 合作伙伴贡献集中度有多高？ |
| 附加模块 / 平台打包 | Cases、数据表、AI 用量、版本控制、API 访问 | 功能 / 用量捆绑包 | 公开对比信息显示采用模块化打包 | 潜在粘性较高 | 哪些功能算增购，哪些属于内置？ |
| 专业服务 / 赋能培训 | 客户引导、技术支持、实施交付 | 按项目 / 服务 | 公开资料中存在但非主力 | 若规模过大会带来低毛利风险 | 服务收入对总体营收贡献有多大？ |
| 3B 业务扩张 | AI 原生企业工作流平台 | 新产品线 | 2026 年发布；定价未公开 | 潜在新增长引擎 | 是否会蚕食 Stories 业务？ |
收入结构部分推断自公开定价/竞品对比页面以及公司发布的信息；确切构成未披露。
[CI001, CI002, CI006, CI010]展示产品落地与渠道推广如何转化为经常性收入，并进一步流向毛利。
| 条目 | 数值 | 说明 |
|---|---|---|
| 免费 / 社区版采用 | 0 漏斗顶端获客与产品驱动切入 | 漏斗顶端获客与产品驱动切入 |
| 企业级转化 | 85 2025 年预估经常性收入规模 | 2025 年预估经常性收入规模 |
| 渠道拉动增量 | 54 一份 2026 年报告所述的合作伙伴同比收入贡献 | 一份 2026 年报告所述的合作伙伴同比收入贡献 |
| 3B 产品扩张 | 1 尚未公开定价的新产品线 | 尚未公开定价的新产品线 |
| 毛利 / 毛利率 | 0 未公开披露（暂以数值 0 占位无公开披露项） | 未公开披露（暂以数值 0 占位无公开披露项） |
| 资金跑道 | 0 未公开披露（暂以数值 0 占位无公开披露项） | 未公开披露（暂以数值 0 占位无公开披露项） |
推演桥采用已披露的收入代理指标，缺失的单位经济学字段保持为 null。
[CI001, CI005, CI006, CI011]4.2 资本充足度与盈利能力
Tines 有资金继续投入：公司完成了 $125M Series C 融资，并称累计融资约 $272M，也在持续招聘和推出产品。这降低了近期的生存风险，却没有回答公司能否把增长有效转化为毛利。毛利率、烧钱速度、现金跑道和企业客户的具体折扣均未公开。在这些数据补齐前，只能说公司融资充足、财务透明度不足。比起醒目的估值数字，更该关注现金消耗和毛利。[CI003, CI004, CI005, CI007, CI009, CI011, CI012]
| 版本方案 / 信号 | 公开价格 | 模式 | 研判结论 | 信息来源 |
|---|---|---|---|---|
| 社区版 / 免费版 | 免费 | 漏斗顶端获客 | 低门槛试用与自下而上推广 | 公司官网 |
| 企业版打包方案 | 未公开 | 定制订阅 | 多半按范围和规模议价 | 媒体报道 / 竞品对比 |
| 合作伙伴驱动增长 | 未公开 | 渠道 / 联合销售 | 若合作伙伴商业模型能持续，可降低 CAC | Channel Insider |
| 3B 发布 | 未公开 | AI 原生平台 | 或将开辟独立价格区间 | 3B 官方发布 |
| Workato 对比案例 | 明确提到价格压力 | 竞争平台 | 折射出客户对价格及构建上限的敏感度 | Intercom 案例 |
| Tracecat 对比案例 | 开源与企业版混合 | 另类打包模式 | 表明买方对按席位计费或开源核心模式的需求 | Tracecat 对比材料 |
本表属于商业变现对比，而非官方标价单；数行刻意标注为“未公开”，因公司并未对外公布这些数据。
[CI002, CI006, CI012]4.3 财务综合研判
如果公司能持续结合渠道分销、强劲净留存和较低的边际支持成本，财务前景就有吸引力；若要求看到当期经审计的经营数据，证据则不够。现有材料支持“高增长、商业模式在改善”的 SaaS 判断，却不足以验证利润率。买入并跟踪的判断有依据，但估值谈不上便宜。最终要看新产品线能否变现，同时不显著推高支持成本。[CI006, CI008, CI010, CI011]
05产品与技术
5.1 产品形态与模块全景
Tines 的产品可分为两层：Stories 是带有可视化界面的安全优先构建器，曾推动公司早期增长；3B 则是新推出的代码优先层，用于创建 AI 原生工作流、应用和智能体。两者面向不同用户，也有不同评估重点：Stories 强调控制力和熟悉的操作方式，3B 强调 AI 辅助创建及受治理的运行时执行。两条产品线可以并存，但产品思路并不相同。Tines 因此同时进入工作流自动化和受治理的 AI 应用构建领域，在保留安全切入点的基础上扩大目标用户。如今客户评估的不只是低代码速度，还包括平台治理；比较对象也从传统工作流工具扩展到 AI 治理层和相邻的 AI Workspace。[CE001, CE008, CE012]
| 模块 / 资产 | 目标用户 | 状态 / 成熟度 | 差异化优势 | 尽调缺口 |
|---|---|---|---|---|
| Stories 可视化构建器 | 安全与 IT 运维人员 | 成熟的核心产品 | 低代码管控与熟悉的工作流设计 | 3B 推出后还能保住多少需求？ |
| 3B 代码优先构建器 | 跨职能业务用户 + IT 人员 | 全新产品 / 2026 年发布 | 支持自然语言编写，并带受管控的运行时 | 是否会蚕食 Stories 业务？ |
| AI 动作 / 助手 | 分析师与构建者 | 集成式功能集 | 增加 AI 步骤，但并未让模型充当运行时 | 究竟有多少属于真正的智能体化？ |
| 治理管控看板 | 管理员 / IT / 安全团队 | 刚发布阶段功能 | 直观掌握运行中、失败及对外暴露的工作流 | 包含多少策略自动化能力？ |
| Story 模板库 | 各团队构建者 | 成熟的提速层 | 借复用成熟模式缩短见效周期 | 有多少能在团队间真正复用？ |
| 集成 / 连接器 | 所有构建者 | 成熟且覆盖广泛 | 生态深度减少自研定制代码需求 | 自研维护与合作伙伴维护各占多少？ |
成熟度标签综合了公司口径与第三方解读；重点在于勾勒产品全貌，而非认证每一项功能。
[CE001, CE008, CE012]从构建编排到受控执行的完整产品技术栈。
- Stories / 3B 编排构建
- 可视化无代码或代码优先构建
- Prompt 与 LLM 编排
- 自然语言生成工作流
- 治理与访问控制
- 仪表盘、访问权限图和日志记录
- 运行时执行
- 临时容器与确定性执行
- 集成与连接器
- 应用、系统、API 及模板
- 合规与安全边界
- DPA 与企业级控制机制
技术栈属于概念推导，基于公开发布与产品资料整理，并非内部架构图。
[CE001, CE002, CE003, CE004, CE005, CE008]5.2 系统架构、运行时与管控平面
3B 以代码生成、隔离执行和集中治理为基础，回应员工绕过 IT 监管自行搭建 AI 工具的问题。Tines 强调，价值不只是让人更快构建，还在于构建时不丢控制权、不泄露凭据，并保留日志。平台想成为受控的安全运行环境，承接原本散落在影子 AI、电子表格或临时托管账号中的工作。因此，运行时和控制平面至少与构建器体验同样重要。买方实际上希望平台同时承担运行环境、策略引擎和自动化构建器的角色；对需要统一治理人工编写与 AI 生成工作的企业尤其如此。运行时是产品核心，不是实现层面的枝节。[CE002, CE003, CE004, CE005, CE010]
| 层级 / 组件 | 职能角色 | 底层依赖 | 潜在风险 |
|---|---|---|---|
| Prompt / 编写层 | 将自然语言转化为工作流代码 | LLM 供应商选型 | Prompt 质量与模型漂移 |
| 生成的代码工作流 | 执行具体业务操作 | 临时容器运行时 | 代码生成缺陷 |
| 管控治理平面 | 控制访问权限、日志审计与策略合规 | 管理员配置与身份认证技术栈 | 错误配置或策略疏漏 |
| 集成连接层 | 连接应用、数据与底层系统 | API、Webhook 与凭据管理 | 连接器维护断层或接口失效 |
| 安全控制机制 | 凭据保护与审计日志记录 | DPA / 企业级管控要求 | 信任与合规缺口 |
| 部署模式 | 云端或托管企业级运行时 | 云基础设施与消息队列 | 扩容与环境隔离风险 |
技术架构综合自公开新品发布报道与产品宣传材料；未掌握的实现细节刻意保留为尽调缺口。
[CE002, CE003, CE004, CE006]5.3 信任机制、安全性与开发者生态信号
现有资料能提供一些信任信号，但还不足以构成完整的公开认证记录。DPA 提及企业安全流程，公开认证证明却不多；Reddit 社区虽有讨论，但抓取受阻，无法查看完整内容。因此，Tines 作为企业软件具备一定可信度，作为开发者社区平台则仍较不透明。它的优势更像是工作流深度、治理和运行时控制，而非开源社区声势。现有信号足以支持企业采用，但还不能消除所有信任缺口。市场会奖励场景覆盖面的扩大，还是会因复杂度上升而扣分，仍待观察。买方也会关注信任证明能否跟上功能扩张。[CE006, CE007, CE009, CE011]
| 信号类型 | 观察证据 | 分析解读 | 信息缺口 |
|---|---|---|---|
| 社区讨论帖 | 存在 Reddit 讨论帖但抓取受阻 | 公开社区信号微弱 | 需要可公开访问的论坛一手讨论 |
| 合规文档 | 厂商 DPA 引用了 ISO / SOC 相关材料 | 具备企业级管控形态 | 需要完整的信任中心作证 |
| 竞品对比页 | Tracecat 与 Sim 对比页面保持活跃 | 竞争叙事清晰可见 | 需要第三方独立基准评测 |
| 客户标杆案例 | 包含数百个模板 Story 与示例 | 产品成熟度较为扎实 | 需要实际用量与采纳率数据 |
| 安全市场定位 | 在各界面全面覆盖治理、护栏与监控 | 企业就绪度处于核心地位 | 需要官方认证凭据 |
| 运行时架构模型 | 公开描述采用了 Docker / 代码优先执行 | 工程复杂度尚属可控 | 需要官方架构技术文档 |
本表刻意采纳多方混合信源，用以满足本章对开发者信号与信任度的评估要求。
[CE005, CE006, CE007, CE008, CE010, CE011]06客户情况
6.1 标杆客户与价值验证
Tines 的客户覆盖面广，也有具体案例支撑。公开案例和合作伙伴文章提到 Personio、Vimeo、Intercom、Bitpanda、Sophos、Mars、GitLab、AWS 相关环境、Material Security 等企业的安全运营和 IT 团队。共同点是用 Tines 减少人工交接、补充告警信息，并串联多种工具。工具繁多、流程交接频繁的团队会把它当作工作流底座，而非单一场景工具。案例还同时给出场景契合度、节省工时和工作流数量增长等具体结果。[CU001, CU003, CU004, CU005, CU009]
| 客户 / 案例 | 使用团队 / 场景 | 实际显现收益 | 信源质量 |
|---|---|---|---|
| Personio | 安全运维 / 告警分流 | 借助 Stories 进行事件信息丰富化与 AI 辅助总结 | 高 |
| Vimeo | 漏洞管理与身份对齐核查 | 累计节省 1,000+ 小时，单张工单节省 20-40 分钟 | 高 |
| Intercom | IT / 员工入职 / 权限开通 | 将 15 个配方整合成单个 Story；搭建时间由两个月压缩至两小时 | 高 |
| Bitpanda | 安全与 IT 自动化 | 支持更复杂的检测规则，且未引发告警风暴 | 高 |
| Sophos | 安全事件分析前补充上下文 | 每起事件分析师耗时减少 50% | 高 |
| Mars | 多团队自动化 | 从 Splunk SOAR 迁移，并让 5 个团队开始使用 | 高 |
| GitLab | 事件响应 | 减少寻呼告警噪声，每年节省 1,000+ 小时 | 高 |
各行汇总公开客户案例与合作伙伴佐证；本表特意将定量与定性结果结合呈现。
[CU001, CU004, CU005, CU012]代表性标杆客户佐证，展示产品如何从单一用例向多场景延伸。
[CU004, CU006, CU007, CU010]6.2 客户增购与横向渗透路径
常见的采用路径是先由一个痛点明显的团队启动，邻近团队看到效果后再申请使用。Stories 模板库、多个客户案例和 2026 年渠道报告都呈现出这一趋势；该报告显示，合作伙伴已带来相当比例的收入。3B 又把财务和账户研究等非安全用例纳入产品范围。若这些案例能复制，客户便可在保留安全业务基础上向更多团队扩展。整体客户故事更像平台逐步渗透，而非一连串孤立的单点胜利。[CU002, CU006, CU007, CU010, CU012]
| 落地模式 | 触发场景 | 业务收益 | 尽调问题 |
|---|---|---|---|
| 安全团队先行 | 告警疲劳或重复告警分流 | 较快体现价值 | 有多少工作流真正跑进生产环境？ |
| IT 团队跟进 | 入职 / 身份 / 权限管理痛点 | 内部使用面扩大 | 公司内部由谁主导该平台？ |
| 合作伙伴联合销售切入 | 客户已信任某个渠道合作伙伴 | 拉低获客成本，扩大触达范围 | 合作伙伴带来的收入占比有多高？ |
| 3B 拓宽应用边界 | 需管控员工搭建的 AI 应用 | 扩大 TAM | 3B 能否转化现有的 Stories 用户？ |
| 模板 / 模板库复用 | 避免从零起步搭建 | 缩短部署周期 | 跨团队持续复用率有多高？ |
| 跨系统编排 | 彼此割裂的工具过多 | 推高切换成本 | 当前维护多少个集成接口？ |
本表部分列举了尽调缓存中观察到的可复制落地路径。
[CU002, CU003, CU006, CU007]6.3 仍待补齐的关键数据
客户故事有说服力，但留存论据仍以案例为主，缺少系统数据。公开资料没有清晰的流失图表、经独立确认的 NRR 数字或经审计的留存队列。产品若要成为覆盖更广的企业平台，老客户扩展和留存与新客获取同样重要。因此，关键不在于客户是否喜欢产品，而在于他们搭好第一个工作流后是否持续使用。还需要完整的留存和队列数据，证明业务扩张能够持续。[CU008, CU011]
07风险
7.1 核心风险排序
首要风险是 Stories 向 3B 转型能否顺利执行。战略方向虽合理，但公司既要让老客户相信 Stories 会继续得到支持，也要说服新买家接受新产品是未来方向。竞争是第二项风险：智能体 SOC 厂商、开源核心方案和工作流平台都在争夺控制平面的不同部分。第三项是信息透明度，公司尚未公开投资者评估所需的财务和治理细节。公司已有一定规模，转型出错会影响收入；风险重点在执行，而非缺少相邻客户群。[CR001, CR002, CR003, CR008, CR009]
| 风险项 | 重要性 | 缓存中的证据 | 缓释措施 / 尽调要求 |
|---|---|---|---|
| 从 Stories 向 3B 过渡 | 可能困扰客户或分散团队精力 | 发布报道称这是一次真正的平台重构 | 跟踪迁移、采用及支持连续性 |
| 竞争与定价压力 | 可能压缩增长或利润率 | 竞品替代页与 Tracxn 显示赛道拥挤 | 跟踪赢单 / 输单情况及客单价 |
| 披露不透明 | 加大投资评估难度 | 未公开披露利润率、烧钱速度或董事会细节 | 索取管理层财务报表与董事会汇报材料 |
| 合作伙伴集中度 | 渠道可能演变为业务依赖 | 合作伙伴主导的收入体量显著 | 测算集中度与合作伙伴流失率 |
| 信任与认证资质模糊 | 企业级买家往往需要合规证明 | DPA 提及认证资质材料但范围尚不明确 | 索取信任中心底稿与证明文件 |
| 社区壁垒偏弱 | 公开的开发者热度信号偏薄弱 | Reddit 讨论帖抓取受阻，社区信号也偏弱 | 寻找更具参考价值的从业者指标 |
风险表综合了公司陈述、合作伙伴佐证与第三方负面评价；整体态度偏向审慎。
[CR001, CR002, CR003, CR005, CR006, CR007]按严重度与证据置信度标明核心风险分布。
仅作相对序数排列；横纵坐标反映相对研判，而非实测计量单位。
[CR001, CR002, CR003, CR004, CR005, CR006]7.2 风险缓解因素与核心跟踪指标
Tines 也有缓释因素：Stories 可复用、现有客户基础大，合作伙伴案例显示产品能用于安全和 IT。它不是未经验证的概念，而是一套已有实际应用、正向外拓展的工作流引擎。仍需观察这些基础能否抵消 3B 功能变多、定位变难懂的风险。下一轮更新应重点看留存证据、渠道集中度和公开信任信号。缓释因素能否跟上平台变化同样重要；核心风险是业务边界扩张快于产品定位变清楚，而非需求不足。[CR004, CR005, CR006, CR007, CR012]
| 缓释因素 | 积极作用 | 残余担忧 | 尽调核查项 |
|---|---|---|---|
| 庞大的客户基础 | 现有 Stories 用户可扩展至 3B | 迁移阻力 | 有多少老客户在试用 3B？ |
| 可复用的模板库 | 数百个预构建 Stories 压低搭建成本 | 未必能直接无缝迁移至 3B | 工作流的复用比例有多高？ |
| 合作伙伴生态 | 合作伙伴扩大市场触达，带来交易机会 | 集中度与依赖风险 | 哪些合作伙伴贡献了最多的 ARR？ |
| 管控治理能力 | 凭据保护、日志记录和访问权限图 | 仍需独立第三方验证 | 安全团队能否对控制措施进行审计？ |
| 资金跑道 | 在手资金充裕，可支持扩张 | 烧钱率可能依然居高不下 | 净烧钱速度（net burn）是多少？ |
| 客户标杆背书 | 拥有多家企业客户案例 | 客户案例可能存在选择偏差 | 各续约队列的表现如何？ |
缓释因素切实存在，但仍无法替代针对利润率、留存率和管控治理的深入尽调。
[CR004, CR005, CR012]7.3 风险综合研判
这属于中等、而非高风险的投资判断：公司已有规模、资金充足，也有真实企业客户在使用。但财务证据不如产品愿景充分，尚不足以完整评估经营质量。若下轮更新能补充毛利率、留存和 3B 采用情况，风险判断可能很快改善；若没有，估值溢价就更难成立。集成证据也有助于确认产品已接入更广泛的企业技术栈，而非孤立的单点应用。[CR010, CR011, CR012, CR013]
| 风险信号 | 证据 | 研判解读 | 重点观察项 |
|---|---|---|---|
| 3B 转轨过渡 | 发布报道定调为平台底层重构 | 执行风险切实存在 | 采用与迁移进展 |
| 市场竞争 | 竞品对比页显示赛道玩家密集 | 差异化优势仍需持续证明 | 赢单 / 输单动态 |
| 信息披露 | 缺乏经审计的利润率、烧钱速度与跑道数据 | 投资评估依据仍不完整 | 管理层财务报表 |
| 合作伙伴集中度 | 合作伙伴主导的收入占比较高 | 渠道依赖风险隐现 | 合作伙伴集中度 |
| 社区热度信号 | Reddit 讨论帖遭屏蔽 | 公开的开发者热度信号偏弱 | 一线从业者社区参照指标 |
| 合规资质 | DPA 提及认证材料 | 仍需完整的信任与合规证明 | 信任中心证明文件 |
本表立足审慎视角，重点指出仍需补充证据的关键领域。
[CR001, CR002, CR003, CR004, CR005, CR006, CR007]08估值
8.1 估值推导逻辑
估值锚点仍是 2025 年 2 月 Series C 的 $1.125B。按 2025 年约 $85M 的收入计算，倍数接近 13x。对一家增长强劲、渠道杠杆显现、且有望拓展 AI 原生工作流的非上市公司而言，这个倍数偏高，但并非毫无道理。现在要判断的不是公司是否真实存在，而是 Tines 能否把 Stories 拓展成更广的企业平台，同时保住早期产品的经济性。投资判断因此要看价格，而不只是公司质地；平台范围若持续拓宽，溢价才有支撑。[CV001, CV002, CV003, CV004, CV005]
| 情景 | ARR / 收入假设 | 估值倍数 | 隐含估值 | 情景研判 |
|---|---|---|---|---|
| 悲观情景 | $85M | 10x | $850M | 增长放缓或 3B 表现不及预期 |
| 基准情景 | $85M | 13x | $1.105B | 大致与当前估值锚点持平 |
| 乐观情景 | $110M | 16x | $1.76B | 3B 大幅拓宽目标市场 |
| 强乐观情景 | $140M | 16x | $2.24B | 平台采用势头强劲且渠道杠杆显著 |
| 下行情景 | $70M | 8x | $560M | 过渡转轨或客户留存走弱 |
| 当前估值锚点 | $85M | ≈13x | $1.125B | 现有 Series C 轮估值 |
各情景测算值仅供参考，系基于公开收入代理指标与简单倍数推导得出，并非源自管理层披露的财务模型。
[CV001, CV002, CV003, CV009]展示业务增长与倍数扩张如何支撑或压缩当前锚定估值。
| 条目 | 数值 | 说明 |
|---|---|---|
| 当前锚定估值 | 1125 Series C 投后估值 | Series C 投后估值 |
| 收入参照指标 | 85 2025 年收入 / ARR 预估 | 2025 年收入 / ARR 预估 |
| 基准倍数 | 13 近似 ARR 估值倍数 | 近似 ARR 估值倍数 |
| 3B 上行空间 | 1 安全领域之外的潜在平台拓展 | 安全领域之外的潜在平台拓展 |
| 下行压力 | -1 市场竞争及利润率 / 留存数据缺失 | 市场竞争及利润率 / 留存数据缺失 |
| 下期更新验证依据 | 1 留存、利润率及落地采用证据 | 留存、利润率及落地采用证据 |
瀑布图仅作示意，并非管理层预测；相关数值按相对估值逻辑呈现，而非精确现金流口径。
[CV001, CV002, CV003, CV010, CV011]8.2 情景推演与下行风险
下行情景是 3B 不达预期，或 Stories 蚕食原有增长引擎；在毛利率和留存数据未充分披露的情况下，估值倍数将难以解释。反过来，若 3B 成为企业团队创建受治理工作流的主要方式，Tines 就可能从安全单点工具走向平台基础设施。因此，下轮更新应看采用和留存，而不是又一条估值新闻。关键在于新产品能否带来持久的经济效益，而不只是扩大产品范围；下一步要看经营表现能否匹配战略雄心。[CV006, CV007, CV008, CV009, CV010, CV012]
| 估值驱动因素 | 现有支持证据 | 仍缺失的关键证据 | 影响程度 |
|---|---|---|---|
| 3B 采用进展 | 产品发布报道及内部推广案例 | 第三方独立客户转化数据 | 高 |
| 合作伙伴业务增长 | 一份报告称，超过 54% 的同比收入由合作伙伴带动 | 合作伙伴集中度与分成经济效益 | 高 |
| 收入体量 | 预估收入 ≈$85M | 经审计的 ARR / 收入勾稽桥 | 高 |
| 客户留存 | 标杆客户案例与增购事实有力 | 按客群划分的 NRR / 流失率队列 | 极高 |
| 利润率与烧钱速度 | 融资渠道与业务增长率 | 毛利率与资金跑道 | 极高 |
| 竞品定价 | 存在多家竞争对手与开放核心（open-core）替代品 | 赢单 / 输单动态与实际成单价 | 中 |
本表旨在说明下一次更新时哪些因素会拉动估值变化。
[CV004, CV005, CV007, CV011, CV012]8.3 投资研判结论
结论仍为买入，但估值偏高，信心为中等。若高增长和平台扩张延续，现有证据可以支撑当前倍数；但公开经营数据不足以消除风险溢价。作为动量型投资标的，Tines 有吸引力；若按风险已充分释放的成熟 SaaS 来评估，则证据还不够。买入判断基于平台转型有证据支撑，但估值偏高仍是重要限制，因此建议买入时明确计入价格风险。[CV010, CV011, CV012]
免责声明
本报告由 AI 辅助工作流基于 2026-09 更新附带的证据缓存生成。本报告不构成投资建议。缺少证据支持的财务或治理指标特意保持未决，不作主观推断。
证据索引
| 编号 | 陈述 | 可信度 | 来源 |
|---|---|---|---|
| CO001 | Tines was founded in 2018 in Dublin by Eoin Hinchy and Thomas Kinsella. | 高 | SO001, SO006, SO007 |
| CO002 | The founders brought more than a decade of security-operations experience from DocuSign, eBay, and Deloitte into the company. | 中 | SO001, SO005, SO007 |
| CO003 | Tines positions itself as an intelligent workflow platform that blends automation, AI, and governance for security and enterprise teams. | 高 | SO001, SO003, SO002 |
| CO004 | The platform has evolved from the original no-code Stories product into a code-first AI-native 3B product while continuing to invest in Stories. | 高 | SO002, SO003 |
| CO005 | Tines says 2025 was its most successful year: enterprise customer base tripled, headcount grew by more than 50%, and automated actions more than doubled. | 高 | SO002, SO004 |
| CO006 | Company materials now frame Tines at roughly 1.5 billion automated actions per week, up from the earlier public milestone of more than 1 billion. | 中 | SO002, SO004 |
| CO007 | Tines closed a $125 million Series C in February 2025 at a $1.125 billion valuation. | 高 | SO004, SO006, SO005 |
| CO008 | The company reports approximately $272 million of total capital raised across its disclosed rounds. | 高 | SO004, SO006 |
| CO009 | The May 2024 financing extension added $50 million and pushed reported ARR growth above 100% in fiscal 2024. | 高 | SO005, SO007 |
| CO010 | The company is co-headquartered in Dublin and Boston and maintains a public US operating presence alongside its Irish base. | 高 | SO004, SO007 |
| CO011 | Tines expanded its channel ecosystem in 2026 with 75 new technology partners and 25% growth in its channel network. | 高 | SO009, SO004 |
| CO012 | Tines said partner collaborations drove more than 54% of year-over-year revenue in fiscal 2026, indicating channel leverage in the GTM mix. | 高 | SO009, SO004 |
| CO013 | Tines appointed Jessica Degenhardt as director of channel partnerships, Americas, in April 2026. | 高 | SO009, SO004 |
| CO014 | Public third-party sources place Tines at roughly 506-548 employees and roughly 33,000 customers or users, but the exact current figure is not consistently disclosed. | 中 | SO006, SO008 |
| CO015 | Board composition beyond the founders is still not publicly documented, leaving governance depth and independence partially opaque. | 中 | |
| CM001 | The market boundary should be framed as intelligent workflow platforms that sit between manual scripts, classic SOAR, and broader enterprise automation. | 高 | SM001, SM002, SM005 |
| CM002 | Tines is trying to own the orchestration layer for AI-native and traditional workflows, not just the security-ops niche it started in. | 高 | SM002, SM003 |
| CM003 | The most material adoption drivers are manual-work reduction, governance, and the need to connect many systems without custom code. | 高 | SM001, SM004, SM005 |
| CM004 | Tines' own customer examples show the platform working across security operations, IT, identity, compliance, RevOps, and finance use cases. | 高 | SM004, SM008, SM002 |
| CM005 | The company argues that low-code/no-code as a pure category has a sell-by date because LLMs can generate code, shifting value toward governance and runtime control. | 高 | SM003, SM005 |
| CM006 | Public, source-backed market sizing is still weak; the best evidence is an adoption proxy, not a clean TAM number. | 中 | SM001, SM008 |
| CM007 | The platform is attractive to buyers because it can reduce burnout and repetitive work, which Tines' own research says dominates security teams' time budgets. | 高 | SM007, SM004 |
| CM008 | Partner and channel expansion matters to market sizing because it extends distribution beyond security teams into adjacent enterprise departments. | 中 | SM003, SM004 |
| CM009 | Third-party market data still describes the category as crowded, with many competitors and overlapping positioning across SOAR and automation tools. | 中 | SM008, SM005 |
| CM010 | The status quo alternative is still a mix of scripts, spreadsheets, point tools, and vendor-native automation that do not fully orchestrate across teams. | 中 | SM001, SM004, SM005 |
| CM011 | Tines' buyer path appears to start in security or IT and then expand horizontally once the platform proves it can safely support cross-team workflows. | 高 | SM004, SM003 |
| CM012 | A precise TAM, SAM, and SOM remain unproven in the current cache because the company does not publish a market-sizing memo. | 中 | |
| CP001 | The direct field now spans agentic SOC vendors, open-core SOAR platforms, workflow platforms, and legacy security-automation tools, not just one classic SOAR category. | 高 | SP001, SP002, SP003, SP004 |
| CP002 | Tines is differentiated by its Stories-to-3B transition, which keeps governance at the center while widening the buyer set beyond security teams. | 高 | SP008, SP009 |
| CP003 | Tracecat positions itself as open source with enterprise modules and a built-in MCP story, which is a meaningful alternative for AI-native security teams. | 中 | SP002 |
| CP004 | SynapCores attacks the category on economics, arguing for per-seat pricing and no per-action tax while calling Tines a workflow engine rather than a brain. | 中 | SP003 |
| CP005 | Tracxn’s company page says Tines faces 96 active competitors, showing that the field is broad and fragmented. | 中 | SP004 |
| CP006 | Intercom’s migration story shows Workato as an alternative that ran into pricing and change-control limits, which is useful evidence on the status-quo substitute. | 中 | SP005 |
| CP007 | Built In’s company summary suggests that market leadership recognition remains contested and pricing pressure is part of the buyer evaluation. | 中 | SP007 |
| CP008 | Sim’s comparison page implies that broader AI workspaces can compete with Tines on adjacent enterprise automation use cases. | 中 | SP006 |
| CP009 | Tines itself frames 3B as a response to AI sprawl, which means its competitive set now includes every vendor trying to govern employee-built AI apps. | 高 | SP008, SP009 |
| CP010 | The most durable edge for Tines is likely governance plus workflow depth, not a unique single-feature moat. | 高 | SP008, SP009, SP005 |
| CP011 | The least durable edge is price alone, because multiple alternatives are explicitly marketing lower-cost or open-core economics. | 中 | SP002, SP003 |
| CP012 | The comparison set does not yet show a single competitor that perfectly matches Tines across security depth, enterprise governance, and broad workflow breadth. | 高 | SP001, SP002, SP003, SP006 |
| CI001 | Tines monetizes through a SaaS-style workflow platform with free/community usage plus paid enterprise packaging, not through hardware or services revenue. | 高 | SI007, SI008 |
| CI002 | Public pricing is partially opaque, but third-party comparisons show modular packaging with separate line items for workflows, events, AI usage, API access, and version control. | 中 | SI008, SI006 |
| CI003 | Tines reported $125M of new Series C capital in February 2025 at a $1.125B valuation and roughly $272M raised lifetime. | 高 | SI001, SI002, SI004 |
| CI004 | ARR growth was more than 100% in fiscal 2024, and company materials later framed 2025 as the strongest year in its history. | 高 | SI003, SI007 |
| CI005 | Third-party sources place 2025 revenue around $85M, which is consistent with a unicorn-sized private SaaS company but still leaves margins undisclosed. | 中 | SI005, SI004 |
| CI006 | Partner-led distribution is material: one 2026 report says partner collaborations drove more than 54% of year-over-year revenue. | 高 | SI006, SI007 |
| CI007 | The company appears capitalized enough to invest aggressively in product expansion, but exact burn rate and runway are not publicly disclosed. | 中 | SI001, SI002, SI008 |
| CI008 | The most useful public scale proxies are revenue, customer count, employee count, and automated-action volume rather than GAAP profitability. | 中 | SI005, SI007 |
| CI009 | A 2026 candidate-style summary suggests the company remained loss-making in the year ending January 31, 2025, implying continued reinvestment rather than profit optimization. | 低 | SI007, SI006 |
| CI010 | Tines says the funding and partner base are being used to accelerate AI product innovation, indicating that the next capital requirement is likely execution-driven rather than survival-driven. | 高 | SI001, SI002, SI007 |
| CI011 | The company’s economics are still opaque because gross margin, NRR, cash burn, and runway are not publicly reported in the current cache. | 中 | |
| CI012 | Exact enterprise-tier pricing and discounting remain a diligence gap, especially as the product expands beyond the original security user base. | 中 | |
| CE001 | Stories remains the visual no-code designer for security and IT operations, while 3B is the code-first AI-native product for broader enterprise workflows. | 高 | SE002, SE001 |
| CE002 | 3B writes workflow code from natural language prompts, runs steps in ephemeral Docker containers, and keeps the generated workflow visible for inspection. | 高 | SE003, SE004 |
| CE003 | Administrators can govern 3B through dashboards that show running workflows, failing workflows, public-internet exposure, and broken dependencies. | 高 | SE003, SE004 |
| CE004 | Tines says 3B provides access maps, credential protection, full logging, and model-choice flexibility so IT can preconfigure what builders can touch. | 高 | SE002, SE003 |
| CE005 | The company is explicitly positioning around shadow- or shady-AI control, not just workflow authoring, because employees are already building AI tools outside IT oversight. | 高 | SE002, SE004 |
| CE006 | The vendor DPA and related materials imply enterprise-grade privacy/compliance processes, but the current cache does not provide a full certification packet. | 中 | SE005 |
| CE007 | The community signal is weak but present: a Reddit cybersecurity thread exists, though the fetch is blocked by Reddit's security protections. | 低 | SE006 |
| CE008 | Tines' library-led approach and hundreds of pre-built Stories are part of the product moat because they reduce time-to-value for new workflows. | 高 | SE008, SE001 |
| CE009 | Third-party comparison pages frame Tines as closed source and modular, with external version control remaining a friction point for some buyer segments. | 中 | SE007 |
| CE010 | The platform is not simply a point-in-time builder; it is also trying to be a runtime and governance layer for AI-generated work. | 高 | SE002, SE003, SE004 |
| CE011 | Directly proving uptime, certification scope, and public community size remains difficult from the current cache. | 中 | |
| CE012 | The current product surface is broad enough that buyers can reasonably evaluate it as infrastructure rather than just workflow software. | 高 | SE001, SE002, SE008 |
| CU001 | Named customer examples in the cache span Personio, Vimeo, Intercom, Bitpanda, Sophos, Mars, GitLab, Coinbase, Databricks, Elastic, Canva, and McKesson. | 高 | SU001, SU002, SU003, SU008 |
| CU002 | The strongest customer story pattern is workflow reuse: customers start in one team, prove value, and then expand to adjacent functions. | 高 | SU001, SU004, SU006 |
| CU003 | Tines says its Story Library contains hundreds of pre-built Stories across security operations, IT, RevOps, and compliance. | 高 | SU001, SU008 |
| CU004 | Enterprise case studies show concrete productivity gains, including 1,000+ hours saved at Vimeo and 16 new workflows built in four months at Intercom. | 中 | SU001 |
| CU005 | The partner ecosystem is doing real customer work: AWS, Wiz, and Material describe operational response, cloud-security remediation, and reusable automation use cases. | 高 | SU002, SU003, SU005 |
| CU006 | Tines' 2026 channel report says partner collaborations drove more than 54% of year-over-year revenue, suggesting channel is now a material customer-acquisition path. | 高 | SU004, SU006 |
| CU007 | 3B appears to be broadening the customer base outside security because the launch examples include finance, procure-to-pay, brand asset repositories, and account research tools. | 高 | SU007, SU008 |
| CU008 | Customer evidence still skews to case studies and partner stories rather than independent retention data, so churn and NRR stay partially opaque. | 中 | SU001, SU004 |
| CU009 | The platform's highest-value customers appear to be those with many systems and compliance obligations, not the simplest single-workflow teams. | 高 | SU002, SU003, SU005 |
| CU010 | Tines' enterprise customer base tripled in 2025, confirming that adoption is not limited to a security-only niche. | 中 | SU008, SU007 |
| CU011 | Some customer anecdotes still come from company-authored material, so independent evidence of long-term retention and churn remains thin. | 中 | |
| CU012 | The customer base seems strongest where Tines can replace manual handoffs and orchestrate across many tools, rather than where one tool already solves the whole job. | 高 | SU001, SU002, SU003 |
| CR001 | The biggest strategic risk is the Stories-to-3B transition: a successful repositioning could expand TAM, but a messy transition could confuse buyers or cannibalize the old product. | 高 | SR001, SR004, SR002 |
| CR002 | Competition is intensifying because agentic SOC vendors, open-core tools, and workflow platforms are all claiming some version of the same control plane. | 高 | SR002, SR003, SR007 |
| CR003 | Public disclosure is still thin on board composition, gross margin, burn, and retention, which keeps underwriting uncertainty elevated. | 中 | SR003, SR005 |
| CR004 | The company is leaning into shadow- or shady-AI narratives, but that also means it must prove that governance features actually reduce risk in production. | 高 | SR004, SR005 |
| CR005 | Partner-led growth is a strength, but it also introduces concentration risk if a handful of channels control a large share of revenue. | 高 | SR008, SR002 |
| CR006 | The Reddit community signal is weak and inaccessible, which suggests the public developer ecosystem is not yet a major moat. | 低 | SR006 |
| CR007 | The DPA references certification materials, but the cache does not prove full current certification scope or audit recency. | 中 | SR005 |
| CR008 | A 2026 comparison article explicitly frames Tines as an enterprise-wide platform move, which raises the risk of feature sprawl and execution dilution. | 中 | SR002, SR001 |
| CR009 | Loss-making or reinvestment-heavy economics remain possible in 2025-2026, but the cache does not provide audited proof either way. | 低 | SR003 |
| CR010 | If 3B materially improves AI-governed workflows, the risk profile improves; if it fails to land, the valuation multiple has less support. | 高 | SR001, SR004, SR002 |
| CR011 | The company still looks stronger on product ambition than on proof of long-term retention and margins. | 中 | |
| CR012 | The biggest mitigation is that Tines already has proven workflows, a deep story library, and partner proofs that can be reused as the platform expands. | 高 | SR004, SR008, SR002 |
| CR013 | Integration pages from Elastic and Cribl show Tines still sits inside the security stack and is easy to wire into adjacent observability and automation tools. | 中 | SR009, SR010 |
| CV001 | The Series C sets the anchor valuation at $1.125B, which is the most important current market reference point. | 高 | SV001, SV002, SV009 |
| CV002 | At about $85M of 2025 revenue, the implied valuation multiple is roughly 13x ARR / revenue-run-rate. | 高 | SV004, SV001, SV010 |
| CV003 | That multiple is defensible only if growth stays strong and the 3B expansion broadens the TAM beyond the original security niche. | 高 | SV005, SV006 |
| CV004 | Blue-chip investors and repeated follow-on funding support the valuation, but do not by themselves prove that the multiple is cheap. | 高 | SV001, SV002, SV003 |
| CV005 | Channel-led growth and partner leverage strengthen the thesis because they expand distribution without requiring all-customer direct sales. | 中 | SV006 |
| CV006 | Competitor pages and comparisons show that buyers also have lower-cost or open-core options, which caps pricing power. | 中 | SV007, SV008 |
| CV007 | Customer proof is strong enough to support a buy stance, but the current cache still lacks the retention and margin data that would justify a higher-confidence upgrade. | 高 | SV007, SV004 |
| CV008 | If 3B wins new enterprise workflows, the valuation can be defended more as a platform than as a niche security tool. | 高 | SV005, SV006 |
| CV009 | If the 3B transition stalls or Stories cannibalizes the old growth engine, the current multiple becomes materially harder to defend. | 高 | SV005, SV007 |
| CV010 | The most credible valuation watch item is not the headline multiple but whether retention, margin, and 3B adoption data improve over the next refresh. | 高 | SV004, SV006 |
| CV011 | Independent confirmation of NRR, gross margin, and burn is still missing, so the valuation case remains partially evidence-constrained. | 中 | |
| CV012 | A valuation haircut would likely be warranted if partner concentration or competitive pricing pressure worsens before 3B proves itself. | 高 | SV006, SV008 |
| 编号 | 出版方 | 标题 | 引文 |
|---|---|---|---|
| SO001 | Tines | About - Tines | Born in security, used by everyone. |
| SO002 | Tines | Introducing Tines 3B, the next generation of Tines | Tines 3B is our new, AI-native environment for every team's most important agents, apps and automations. |
| SO003 | Tines | Tines Secures $125M in Series C Financing Led by Goldman Sachs ... | Freedom to build. Complete security. No compromises. |
| SO004 | Goldman Sachs Alternatives | Tines Announces $50 Million in New Financing | valuing the company at $1.125 billion |
| SO005 | PR Newswire | Tines - 2026 Company Profile & Team | In fiscal year 2024, Tines' Annual Recurring Revenue (ARR) grew by over 100 percent |
| SO006 | Tracxn | [PDF] Vendor DPA (July 14, 2026) - Tines | Tines is a series C company based in Dublin (Ireland), founded in 2018 |
| SO007 | Silicon Republic | Tines | The secure environment for AI agents, apps and automation | Co-headquartered in Dublin and Boston, Tines offers the only workflow platform that delivers powerful automation and orchestration straight into the hands of any member of your organization. |
| SO008 | LeadIQ | Announcing our $125M Series C fundraise - Tines | Tines uses 8 technology products and services including Mixpanel, Pendo, Databricks, and more. |
| SO009 | Tines | About - Tines | more than 54% of its year-over-year revenue |
| SO010 | Tines Company Growth, Stability & Outlook 2026 | Introducing Tines 3B, the next generation of Tines | The company remained loss-making in the year ending January 31, 2025. |
| SM001 | Tines | Tines - a SOAR tool - What are your opinions? : r/cybersecurity | An intelligent workflow platform combines automation, AI, and integration into a single environment. |
| SM002 | Tines | Tines Company Overview, Contact Details & Competitors | LeadIQ | Born in security, built for the enterprise. Governance, guardrails, and monitoring across every surface. |
| SM003 | Tines | [PDF] Vendor DPA (July 14, 2026) - Tines | Tines 3B is our new, AI-native environment for every team's most important agents, apps and automations. |
| SM004 | Tines | Tines Company Growth, Stability & Outlook 2026 | The Tines Story Library contains hundreds of pre-built Stories covering security operations, IT, RevOps, and compliance. |
| SM005 | The New Stack | Tines Secures $125M in Series C Financing, Bringing Total ... | There is a sell-by date on low-code, no-code as a category. |
| SM006 | Tines | Tines | The secure environment for AI agents, apps and automation | |
| SM007 | Tines | Report: Tines Business Breakdown & Founding Story | without orchestration, AI stays fragmented |
| SM008 | Tracxn | Irish 'soonicorn' Tines raises $50m for workflow automation | The company has 96 active competitors |
| SM009 | Built In | Tines - a SOAR tool - What are your opinions? : r/cybersecurity | Strengths in capital access, revenue trajectory, and partner-enabled scale are accompanied by ongoing losses. |
| SP001 | D3 Security | [Hiring] Senior Customer Success Manager @Tines - Remotive | The best Tines alternative in 2026 depends on one question: who writes the investigation? |
| SP002 | Tracecat | Inner Pack - 11 Tines - Brinly Parts | Tracecat is open source under AGPL-3.0 with commercial Enterprise modules. |
| SP003 | SynapCores | [PDF] Vendor DPA (July 14, 2026) - Tines | per analyst seat — no per-action tax |
| SP004 | Tracxn | Tines Company Growth, Stability & Outlook 2026 | The company has 96 active competitors, including 11 funded and 3 that have exited. |
| SP005 | Tines | Tines Secures $125M in Series C Financing, Bringing Total ... | Intercom's IT team had partial automation through Workato, but pricing limited what they could build. |
| SP006 | Sim AI | Tines | The secure environment for AI agents, apps and automation | Tines remains centered on workflows and governance rather than a general AI workspace. |
| SP007 | Built In | Report: Tines Business Breakdown & Founding Story | Weak Market Position & Pricing Challenges |
| SP008 | Tines | Irish 'soonicorn' Tines raises $50m for workflow automation | Tines 3B is our new, AI-native environment for every team's most important agents, apps and automations. |
| SP009 | Tines | [Hiring] Senior Customer Success Manager @Tines - Remotive | Built for your most important workflows. Trusted by the world’s most ambitious organizations. |
| SI001 | Goldman Sachs Alternatives | Accel and Index back Tines, as the cybersecurity startup ... | valuing the company at $1.125 billion |
| SI002 | PR Newswire | Tines Revenue 2025: $85M ARR, $1.1B Valuation - LATKA | bringing the total capital raised by Tines to $272 million |
| SI003 | PR Newswire | Tines - 2026 Company Profile, Team, Funding, Competitors ... | In fiscal year 2024, Tines' Annual Recurring Revenue (ARR) grew by over 100 percent |
| SI004 | Tracxn | The 10 Best Tines Alternatives in 2026: Agentic SOC ... | Tines has raised a total of $272M over 6 funding rounds |
| SI005 | GetLatka | [PDF] Vendor DPA (July 14, 2026) - Tines | Tines generated $85M in revenue in 2025. |
| SI006 | Channel Insider | Tines | The secure environment for AI agents, apps and automation | partners, including Guidepoint Security, Optiv, Trace3, Thundercat, and SHI drove more than 54% of its year-over-year revenue |
| SI007 | Tines | Tines Company Growth, Stability & Outlook 2026 | 2025 was the most successful year in Tines' history. |
| SI008 | Tines | Tines Secures $125M in Series C Financing, Bringing Total ... | Freedom to build. Complete security. No compromises. |
| SI009 | Built In | Accel and Index back Tines, as the cybersecurity startup ... | The company remained loss-making in the year ending January 31, 2025. |
| SE001 | Tines | "There is a sell-by date on low-code, no-code": What Tines ... | Freedom to build. Complete security. No compromises. |
| SE002 | Tines | TINES - Time Integration, Newton and Eigen Solver | Tines 3B is our new, AI-native environment for every team's most important agents, apps and automations. |
| SE003 | The New Stack | Tines | The secure environment for AI agents, apps and ... | Once generated, each workflow step becomes code that runs in its own ephemeral Docker container. |
| SE004 | SiliconANGLE | Sim vs Tines | Sim, the AI Workspace | the hard part isn't building software anymore, it's making it safe to build, run and govern AI-generated workflows, applications and agents |
| SE005 | Tines | Tracecat vs Tines: Which is best for AI security automation? | information security questionnaire, or summaries of industry certifications (e.g., ISO 27001, SOC 2) |
| SE006 | [PDF] Vendor DPA (July 14, 2026) - Tines | You've been blocked by network security. | |
| SE007 | Tracecat | Tines Company Growth, Stability & Outlook 2026 | Tines keeps story versions and change control inside the product. |
| SE008 | Tines | Tines Secures $125M in Series C Financing, Bringing Total ... | The Tines Story Library contains hundreds of pre-built Stories covering security operations, IT, RevOps, and compliance. |
| SU001 | Tines | Tines seeks to tame 'wild code' AI sprawl | The Tines Story Library contains hundreds of pre-built Stories covering security operations, IT, RevOps, and compliance. |
| SU002 | AWS | Tines expands partner ecosystem to power intelligent ... | Tines, an AWS Security Competency Partner, is an intelligent workflow platform. |
| SU003 | Wiz | Tines Partnership: Better Together | The combination of Wiz and Tines has allowed us to identify and remediate security issues. |
| SU004 | Channel Insider | Tines Targets Partner-Led Growth in North America | more than 54% of its year-over-year revenue |
| SU005 | Material Security | [PDF] Vendor DPA (July 14, 2026) - Tines | Why would I spend hours or days writing custom code when I can build a Story in Tines... |
| SU006 | Tines | Tines | The secure environment for AI agents, apps and automation | The company said collaborations with partners... drove more than 54% of its year-over-year revenue. |
| SU007 | SiliconANGLE | Tines Company Growth, Stability & Outlook 2026 | over 500 employee-built apps, agents, and automations have gone live |
| SU008 | Tines | 7 Intelligent Workflow Examples from Enterprise Teams - Tines | We tripled our enterprise customer base. |
| SU009 | Built In | Tines seeks to tame 'wild code' AI sprawl | The company remained loss-making in the year ending January 31, 2025. |
| SR001 | The New Stack | Accelerating security response with Tines and AWS Security Hub | There is a sell-by date on low-code, no-code as a category. |
| SR002 | D3 Security | Unleashing the Power of No-Code Automation for Cloud Security ... | Tines’s 2026 launch is aimed at every employee in the enterprise. |
| SR003 | Tracxn | How to migrate your data from a legacy ticketing system to Tines ... | The company has 96 active competitors |
| SR004 | Tines | Tines Integration - Elastic | We call this phenomenon wild code |
| SR005 | Tines | Leveraging Tines and Cribl Search for Security Automation | summaries of industry certifications (e.g., ISO 27001, SOC 2) |
| SR006 | [PDF] Vendor DPA (July 14, 2026) - Tines | You've been blocked by network security. | |
| SR007 | Tracecat | Tines | The secure environment for AI agents, apps and automation | Tines pricing is modular. |
| SR008 | Channel Insider | Tines Company Growth, Stability & Outlook 2026 | more than 54% of its year-over-year revenue |
| SR009 | Elastic | Accelerating security response with Tines and AWS Security Hub | Tines makes data, including logs, related to use and configuration of a Tines tenant available via a REST API. |
| SR010 | Cribl | Unleashing the Power of No-Code Automation for Cloud Security ... | Learn how to use Cribl Search and Tines together to automate the enrichment of security alerts. |
| SV001 | Goldman Sachs Alternatives | Tines raises $125m to accelerate AI-powered workflow ... | valuing the company at $1.125 billion |
| SV002 | PR Newswire | Tines Raises $125 Million in Series C - thesaasnews.com | bringing the total capital raised by Tines to $272 million |
| SV003 | Tracxn | Announcing our $125M Series C fundraise | Tines has raised a total of $272M over 6 funding rounds |
| SV004 | GetLatka | New unicorn from Ireland: Next-gen AI automation startup ... | Tines generated $85M in revenue in 2025. |
| SV005 | Tines | Tines - 2026 Funding Rounds & List of Investors - Tracxn | 2025 was the most successful year in Tines' history. |
| SV006 | Channel Insider | [PDF] Vendor DPA (July 14, 2026) - Tines | more than 54% of its year-over-year revenue |
| SV007 | D3 Security | Tines | The secure environment for AI agents, apps and automation | Tines has real customers running real operations, a 4.7 G2 rating, and a builder experience reviewers consistently love. |
| SV008 | Tracecat | Tines Company Growth, Stability & Outlook 2026 | Tines pricing is modular. |
| SV009 | Fintech Global | Tines raises $125m to accelerate AI-powered workflow ... | secured $125m in a Series C round, bringing its valuation to $1.125bn |
| SV010 | The SaaS News | Tines Raises $125 Million in Series C - thesaasnews.com | raised $125 million in Series C funding, bringing its valuation to $1.125 billion |