初创公司尽调
尽调报告 cybersecurity SPAC 2026-07-30

EigenQ

EigenQ:抗量子安全基础设施

EigenQ 卡位量子安全基础设施这个有吸引力的切口,但宣布的约 $3B SPAC 估值仍跑在公开证据前面,更适合继续研究,而不是高确信买入。

封面要素

企业价值 01
~$3B [CO003]
预计交割后股票代码 02
EIGQ [CO007]
SPAC 信托现金 03
~$215M pre-redemption [CO005]
战略合作 04
HPE / AMD / WNC / TD SYNNEX [CO024]
客户重点 05
Government / defense / critical infrastructure / enterprise [CO014]
技术范围 06
PQC, trusted infrastructure, communications, sensing, computing [CO008]
建议 07
research-more [CO031]
风险评级 08
high [CO036]

公司概况

EigenQ 是一家总部在 Texas 的量子技术公司,近期商业化故事围绕以硬件为根的后量子安全基础设施,而不是投机性的纯计算需求。公司正借与 Silicon Valley Acquisition Corp. 待完成的 SPAC 合并,为商业化、制造扩产和全球扩张融资,公告的备考企业价值约为 $3.0 billion。公开证据显示,政策顺风和合作伙伴栈都有可信度,但收入质量和客户密度仍像未披露指标的私营公司。

官网
eigenq.com
创始人
Dr. Jesse Van Griensven Thé
创立地点
Austin, TX
总部
Austin, TX
产品
以硬件为根的抗量子信任基础设施,覆盖 QMA 熵模块、qTPM 身份、qTEE 可信执行、PQC+ 密码学,以及量子安全、通信、感知、AI 和计算等更广支柱。
客户
政府、国防、关键基础设施和企业买家,需要长期数据保护、可信身份和量子安全迁移路径。
商业模式
面向政府和企业商业化,路径包括直销、OEM 与服务器集成,以及由 HPE、AMD、WNC、TD SYNNEX 和 Intel 生态部署动作牵引的合作伙伴渠道分发。
阶段
SPAC (pre-close)
融资情况
与 SVAQ 的 SPAC 交易待完成,备考企业价值约 $3.0B,赎回和费用前信托现金约 $215M;未公开独立收入或完整股权结构表。
[CO001, CO003, CO005, CO008, CO009, CO014, CO017, CO024]

执行摘要

主要优势

  • NIST PQC 标准和国家安全迁移压力带来真实政策顺风,支撑品类需求。
  • HPE、AMD、WNC 和 TD SYNNEX 给 EigenQ 搭起商业化脚手架,强于许多披露不足的深科技同业。
  • 产品叙事更贴近当下网络安全预算,而不是纯粹押注长期容错计算。
  • 待完成的 Nasdaq 上市给公司留下规模化融资路径,前提是披露改善、需求能转化。

主要风险

  • 公开来源仍未披露支撑宣布估值所需的收入、毛利率、留存或客户数指标。
  • SPAC 赎回、稀释和交割机制可能让可用增长资金显著低于名义信托金额。
  • 相对于商业化叙事的规模,具名客户证明仍偏少。
  • 公开量子和 PQC 可比公司波动很大,也已经显示即便上市,前沿技术商业化仍可能拉得很长。
  • 合作伙伴组合有战略价值,但公开证据尚未证明联盟能转成可重复订单。

未决问题

  • 最终 S-4 中的经审计收入、订单、毛利率和客户集中度披露。
  • 资金来源与用途、PIPE 或侧融资条款、认股权证压力和赎回敏感性。
  • 合作伙伴经济性,包括 OEM / 渠道抽成、资质验证成本和质保负担。
  • 需要更多具名客户、合同金额、部署数量和续约证据,超出目前稀疏的证明点。

目录

Chapter 01

01公司概览

1.1 身份、阶段与核心供给

EigenQ 将自己定位为应用型量子技术公司,近期商业化重点放在后量子网络安全,而不是投机性的容错计算。公司称,其平台把量子生成熵、以硬件为根的身份和执行控制,以及后量子密码软件层组合起来,可接入现有基础设施,无需整体重构。2026 年 6 月 17 日,公司宣布与 Silicon Valley Acquisition Corp. 签署最终业务合并协议,公开公司叙事由此锚定。该交易给予 EigenQ 约 $3.0 billion 的企业价值,提到 SPAC 信托在赎回和费用前持有 $215 million 现金,并计划在 2026 年 Q4 交割,前提是 SEC 生效、股东批准并满足交易所上市条件。在公开定位中,EigenQ 卖的不是单一盒子,而是一套信任基础设施栈,服务必须适应 NIST 后量子标准和 CNSA 2.0 迁移压力的政府、国防、关键基础设施和企业环境。[CO001, CO002, CO003, CO004, CO005, CO006]

EigenQ 快照 KPI 表
指标数值 / 状态日期信心来源 / 缺口
总部美国 Texas(合并公告为 Austin;部分产品公告中出现 Columbia, MD)2026-06 至 2026-07公开材料最一致地使用 Texas/Austin,但部分伙伴新闻稿在运营层面列出 Columbia, Maryland
阶段待完成 SPAC / 上市前公开挂牌流程2026-07SEC 文件和 SPAC 网站
SPAC 伙伴Silicon Valley Acquisition Corp.(Nasdaq: SVAQ,SPAC 伙伴)2026-06SEC 文件和 Nasdaq
备考企业价值~$3.0B2026-06SEC 文件和 PRNewswire 新闻稿
股权对价公式$2.93B / $10.00 换股比率基准2026-06业务合并协议摘要
SVAQ 信托账户~$215M,赎回和费用前2026-06合并公告来源
交割后预期股票代码EIGQ2026-06SEC 文件和 2026 年 7 月 425 文件
目标交割时间2026 年 Q4,取决于批准2026-06SEC 文件和 PRNewswire 新闻稿
核心产品硬件根植的后量子信任基础设施,包含熵、身份、可信执行和 PQC 模块2026-07官方网站产品栈
具名平台 / 渠道伙伴HPE、AMD、WNC、TD SYNNEX、Intel 生态对齐2025-07 至 2026-07公司和伙伴公告
收入 / ARR / 客户 / 员工数所审阅来源未公开披露2026-07待上市之际仍是重大缺口
披露画像私营且未披露,待 SPAC 交割2026-07公司尚未报告公众公司运营 KPI

公开来源支撑估值、信托现金、挂牌路径和产品框架,但核心运营指标仍未披露。各来源对总部表述不一;Texas/Austin 是规范的顶层身份。

[CO001, CO002, CO003, CO004, CO005, CO006]
FO002: 公司快照逻辑

EigenQ 将监管压力和 OEM / 渠道关系接到以硬件为根的信任栈,目标买家是受监管基础设施。

[CO008, CO011, CO024, CO028, CO029, CO030]
FO003: 快照 KPI 与披露缺口

公开信息在交易框架和合作伙伴叙事上充足,但运营指标薄弱。

[CO003, CO005, CO006, CO024, CO031, CO032]

1.2 领导层、治理与职能覆盖

随着 EigenQ 推进合并,公开的领导层披露有所改善,但仍比一家已上市运营公司通常提供的披露包薄。公司网站列出 Dr. José R. Rosas-Bustos 为 CEO、Dr. Jesse Van Griensven Thé 为董事长;2026 年 7 月合并期沟通又加入 Mark Pecen 担任副董事长,并将 Alexander Truskovsky 提升到新设的 CISO 岗位。网站还列出临时/代理 CFO、首席增长官、首席产品高管,以及聚焦收入和合作的商务负责人,合在一起显示公司在投入产品化和商业化,而不是停留在纯研究驱动。即便如此,公开材料还没有给出常规的董事会委员会图谱、董事独立性分析、经审计的治理控制,或清晰对齐的股权结构表。尽调时可以把这套领导班子视为具备商业化可信度,但在注册声明和代理材料完整披露监督结构前,治理成熟度仍应按进行中处理。[CO016, CO017, CO018, CO019, CO020, CO021]

领导层与创始人表
人员职务背景 / 职能覆盖创始人-市场匹配或相关性关键人物依赖
Dr. José R. Rosas-BustosCEO曾任 CTO;现负责战略、商业化和量子韧性信任基础设施定位把技术架构与商业化叙事接起来高;可见 CEO 兼合并期发言人
Jesse Van Griensven Thé 博士董事长 / 创始人角色学术界和量子技术人物;公开董事长和早期战略推动者锚定量子可信度和长期平台愿景高;位于创始人身份和投资者叙事中心
Mark Pecen副董事长ETSI 量子安全标准老兵,曾任 EigenQ 董事会顾问增加标准、通信和欧洲生态可信度中高;对外部可信度和 IP 战略重要
Alexander Truskovsky首席信息安全官曾任密码学副总裁;2026 年 7 月晋升释放产品安全和合规领导力正规化信号中;对企业和受监管买方信任重要
Rika Nakazawa首席增长官曾在 NVIDIA/Sony/Accenture 任高管,聚焦全球增长和主权市场扩张强化全球市场进入和战略伙伴覆盖中;偏扩张导向,不是技术单点故障
William Berghoff临时 / 代理 CFO长期业务参与者和临时财务负责人在合并期提供财务连续性中;职务披露为临时 / 代理,因此永久财务领导仍待确定

公开领导层披露主要来自公司网站和 2026 年 7 月新闻稿。董事会委员会、独立性和最终公众公司治理结构仍未披露。

[CO016, CO017, CO018, CO019, CO020, CO021]

1.3 资本、合作伙伴生态与披露边界

EigenQ 最强的公开证据点是资本框架和生态对齐,而不是运营指标。资本层面,合并文件和配套公告持续引用约 $3.0 billion 的备考企业价值、SVAQ 信托账户在赎回前约 $215 million 的现金;业务合并协议则锁定 $2.93 billion 的股权对价公式。生态对齐层面,EigenQ 反复把商业化与 HPE、AMD、WNC、TD SYNNEX 和 Intel 相关部署路径绑定:WNC 对应硬件制造扩产,HPE 对应服务器集成,TD SYNNEX 对应渠道和公共部门分销,Intel/AMD 对应已安装服务器资产的改造或部署适配。缺失的信息同样重要:现有来源没有披露收入、ARR、员工人数、客户数量、毛利率、留存或完整的 SPAC 前融资历史。因此,尽管公共交易待完成,公司披露画像仍像指标未披露的私营公司;估值判断更多押注战略叙事,而不是已披露运营证据。[CO003, CO004, CO005, CO024, CO025, CO026]

利益相关方或投资者地图
利益相关方角色控制权或经济重要性证据状态尽调问题
Silicon Valley Acquisition Corp.合并交易对手 / 上市壳提供挂牌路径和信托现金,但所得款取决于赎回和批准SEC 和 SPAC 材料记录充分审阅赎回敏感性、PIPE/兜底条款和交割条件
SVAQ 公众股东赎回敏感资本池可实质性削减交割时可用现金通过信托账户和合并风险措辞间接记录建模最低现金和摊薄情境
WNC制造与硬件规模化伙伴可能把原型转化为批量生产,并保障供应链执行有伙伴公告支撑验证生产状态、认证周期和商业单位经济性
HPE服务器集成和企业可信度伙伴对证明 OEM 改造和公共部门部署相关性重要有公司公告和 HPE 文件支撑确认实际设计导入、转售路径和认证范围
AMD / TD SYNNEXEPYC 环境的平台和分销路径对触达公共部门、国防和企业买方的实际渠道重要有公司公告和媒体转载伙伴公告支撑核验合作是否已转化为出货项目,还是只停留在就绪度评估
Intel存量基础设施现代化路径支撑无需全面替换即可改造现有 Xeon 机群的叙事有 2026 年 7 月公告和行业报道支撑核验兼容性是参考架构、试点,还是产生收入的部署

这是一张利益相关方地图,而不是股权结构表,因为已审阅公开来源没有披露可靠的交割前股东名册或历史私募融资名单。

[CO005, CO024, CO025, CO026, CO027, CO033]

1.4 里程碑、依赖与近期风险

EigenQ 已经在合作、管理团队搭建和拟上市路径上拼出一串可见里程碑,同一批来源也暴露了公司最核心的尽调风险。6 月 23 日的 8-K 说明,合并取决于 SEC 生效、股东批准和上市批准,最晚截止日为 2027 年 2 月 14 日。该文件和新闻稿都提示赎回、定价压力、供应链暴露、客户采用时点、OEM 集成时点,以及一般前瞻性不确定性。这些并非只有模板意义的风险:它们直接映射到 EigenQ 的商业模式。公司需要借第三方平台生态和渠道伙伴,把标准推动力转化为可部署的硬件根基础设施。结论是,EigenQ 可能踩中了强主题时点,也有可信的技术定位,但近期价值兑现仍取决于交易能否交割、能否向公共部门和企业买家证明渠道实际销售,以及上市流程推进后能否把合作公告转成可衡量收入和客户证据。[CO006, CO025, CO026, CO027, CO034, CO035]

里程碑表
日期事件类型金额 / 状态参与方含义
2024-08-13NIST 发布 EigenQ 市场叙事引用的首批最终版 PQC 标准监管FIPS 203/204/205 已定稿NIST为产品-市场时点创造标准背景
2025-07-15EigenQ 和 WNC 在 HPE Discover 2025 宣布战略合作合作已宣布合作EigenQ、WNC、HPE 生态在 SPAC 公告前释放制造和 OEM 集成雄心
2026-06-10Rika Nakazawa 获任首席增长官治理高管任命EigenQ建设全球扩张和主权市场进入能力
2026-06-15EigenQ 宣布与 TD SYNNEX 在 AMD EPYC 环境上合作合作已宣布合作EigenQ、TD SYNNEX、AMD搭建进入公共部门和企业基础设施的渠道与平台路径
2026-06-17宣布与 SVAQ 达成最终业务合并融资~$3.0B EV,赎回前 ~$215M 信托EigenQ、SVAQ创造公开挂牌和规模化资本路径
2026-06-238-K 摘要披露业务合并协议监管披露交割条件和最晚截止日SVAQ、EigenQ厘清批准、挂牌和风险依赖
2026-07-06宣布 Intel Xeon 就绪能力产品宣布现有现场平台对齐EigenQ、Intel 生态强化改造和存量基础设施叙事
2026-07-28Mark Pecen 获任副董事长;Alexander Truskovsky 晋升 CISO治理宣布领导层调整EigenQ显示上市前高管团队正规化
2026-Q4 目标业务合并目标交割窗口融资预期交割窗口EigenQ、SVAQ、股东、SEC仍取决于批准和生效
2027-02-14业务合并协议中的最晚截止日不利终止兜底日期EigenQ、SVAQ如果批准或条件延误,时间表风险会凸显

里程碑仅反映公开披露。公司成立日期和 2025 年前融资历史,在已审阅来源中没有可支撑披露。

[CO002, CO003, CO005, CO006, CO018, CO019]
FO001: EigenQ 公开里程碑时间线

公开里程碑显示,EigenQ 正从合作伙伴牵引的商业化证明,走向 2026 年仍带条件的公开市场交易。

[CO002, CO003, CO018, CO019, CO020, CO025]

1.5 展项

Chapter 02

02市场分析

2.1 市场边界与 EigenQ 应计入的范围

EigenQ 的正确市场框架不是“全部量子技术”,甚至不是整个网络安全栈。最接近的商业边界,是受监管数字基础设施的后量子密码迁移:替换或增强 RSA/ECC 时代信任功能的软件和硬件,以及部署所需的集成和迁移服务。公开市场报告通常会纳入软件、硬件安全模块或加速器、咨询或部署服务,但是否把相邻的量子安全网络、迁移项目和更广的密码硬件算进去,各家口径不同。具体到 EigenQ,商业上真正相关的细分更窄:政府、国防、关键基础设施和企业服务器环境中,OEM 集成、硬件根、基础设施导向的 PQC 采用。因此,现状竞争不只是另一家量子创业公司;还有既有 HSM 供应商、云安全栈、内部自建项目,以及因为替换周期昂贵复杂而拖延迁移的组织。[CM001, CM002, CM003, CM004, CM013, CM014]

市场定义表
细分 / 类别纳入支出排除支出 / 邻近项买方或付款方为何对 EigenQ 重要
PQC 软件和密码库算法库、证书或密钥管理软件、加密敏捷性工具没有 PQC 功能的一般安全软件CISO、平台安全、应用负责人多数市场研究中的核心软件层,也是 EigenQ 栈的一部分
硬件根植 PQC 模块熵硬件、加速器、安全芯片、类似 HSM 或邻近 TPM 的模块没有 PQC 功能的通用服务器硬件OEM 产品团队、基础设施架构师、采购最契合 EigenQ 差异化硬件根植叙事
迁移与集成服务评估、盘点、部署、互操作、托管迁移无关咨询支出CIO 办公室、联邦项目经理、系统集成商服务通常放大 TAM,也可能卡住软硬件采用
受监管通信和身份基础设施安全通信、认证、密钥生命周期、证明、信任根与 PQC 无关的消费消息或广义 IT 支出政府、国防、关键基础设施、企业安全最适合作为 EigenQ 目标用例的代理
量子安全网络 / QKD 邻近产品以量子安全定位营销的网络或通信产品纯研究网络项目和无关电信资本开支国家安全、电信、主权网络项目相关邻近市场,但不是 EigenQ 最干净的商业分母
排除:全量子计算 / AI / 传感支出None安全迁移之外的量子计算机、传感或主权 AI 预算R&D、科研或计算买方重要,因为 EigenQ 的 SPAC 叙事横跨比即时收入市场更宽的量子领域

市场报告差异最大之处在于是否计入硬件、迁移服务和量子安全网络邻近项。该表收窄 EigenQ 商业相关边界。

[CM001, CM002, CM013, CM014, CM030, CM032]
FM001: 市场规模视角

EigenQ 的可服务市场只是更大 PQC 增长故事的一部分:从全部量子转型支出,收窄到受监管基础设施和 OEM 集成的信任模块。

[CM001, CM002, CM014, CM030]

2.2 规模测算口径与估计分歧

所有已审阅的公开市场来源都指向同一方向——多年快速扩张——但没有一个给出唯一权威分母。Axis Intelligence 综合了较宽口径:纳入硬件、服务和迁移项目后,2025 年约 $1.3 billion 到 $1.6 billion,2026 年约 $2.2 billion 到 $2.8 billion。The Business Research Company 给出更窄的 2026 年市场值 $0.78 billion 和 2030 年展望 $2.23 billion;360ResearchReports 与 Business Research Insights 又发布了不同的 2026 和 2035 曲线。分歧本身有信息量,而不是噪音:市场仍年轻,定义仍流动,分析师边界选择会实质改变标题数字。尽调上,最有助于决策的结论不是一个 TAM 数字,而是一个区间。EigenQ 可以可信地指向强结构性增长,但不能指向一个已形成共识、足以自动验证 $3 billion 企业价值的市场规模。[CM005, CM006, CM007, CM008, CM009, CM010]

TAM / SAM / SOM 或规模测算视角表
发布方年份地域数值CAGR / 预测期方法论信号信心局限
Axis Intelligence Research2026全球$2.2B-$2.8B(2026);$1.3B-$1.6B(2025)底层预测区间为 37%-46%跨来源综合,纳入硬件、软件、服务和政策背景二级综合,不是一手市场样本
The Business Research Company2026全球$0.78B(2026);$2.23B(2030)到 2030 年 30.5%覆盖终端用户垂直领域的解决方案和服务范围窄于更宽口径预测
360ResearchReports2026全球$1.106B(2026);到 2035 年 $18.19B36.49%广义市场仪表盘,包含应用组合和区域份额方法披露较薄,部分运营指标看起来偏模型驱动
Business Research Insights2026全球$0.68B(2026);到 2035 年 $1.47B9.04%叙事型市场概览,包含应用和区域分割预测显著低于同行;历史框架看起来偏通用
CISA 买方指引2026美国联邦采购非收入视角:品类级采购指引政策时点,不是市场 CAGR定义采购品类,买方应优先选择支持 PQC 的产品不是市场规模来源
NIST / White House / NCCoE 来源2024-2026美国监管基线非收入视角:迁移强制要求与互操作性工作截止期限与采用路径视角解释为什么即使支出共识尚未明朗,采用也会发生不是直接的 TAM 来源

有用的结论是一段区间,而不是单一 TAM。政策来源说明需求为何紧迫;分析师报告则显示,定义口径如何改变收入分母。

[CM005, CM006, CM007, CM008, CM009, CM010]
FM002: 市场估算区间

已发布的市场曲线对分母分歧很大,但一致指向强劲增长。

数值沿用各来源发布的计价单位和范围选择,没有归一到同一种方法。

[CM005, CM006, CM007, CM008, CM009, CM011]

2.3 买家、预算所有者与采用路径

把市场拆成买方系统,而不是只按行业看,证据最连贯。在受监管环境中,用户可能是安全或密码团队,预算所有者可能是 CISO、CIO、平台安全负责人或联邦项目办公室,部署路径往往走 OEM、渠道或集成商生态,而不是直接购买 SaaS。政府和国防买家关心保障期限、采购类别和认证路径;关键基础设施运营方关心资产寿命长和改造可行性;金融、医疗和电信买家则要保护长期记录,同时不扰动生产流量。EigenQ 的公开信息最贴合高保障计算、安全身份、加密通信和硬件根服务器环境,这些买方需求更接近基础设施现代化,而不是可选安全工具。实践中,采购摩擦也意味着平台伙伴塑造节奏的力度常常不亚于终端客户紧迫性。因此,采用通常走分阶段流程——盘点、评估、试点、混合部署、资质确认,再到规模化铺开——而不是一个季度内完成软件替换。[CM003, CM012, CM013, CM014, CM015, CM016]

细分市场 / 买方图谱
细分市场买方使用方付款方 / 预算负责人工作流采用触发因素
联邦民用高价值系统机构网络安全和企业架构团队安全工程师和 PKI 团队联邦 CIO/CISO 或项目办公室密码资产清点、试点、采购、分阶段替换白宫和 CISA 指引,加上长期保存数据风险
国家安全 / 国防环境任务系统集成商和国防 IT 负责人密码、网络和平台安全团队项目执行办公室和国防采购资质要求高、由安全保证驱动的部署对齐 CNSA 2.0,以及涉密数据长期保密需求
关键基础设施运营方基础设施安全和 OT/IT 融合团队网络、身份和运营安全人员CISO、COO 或资产所有方围绕长生命周期资产做改造规划需要保护长期运行系统,又不能整体拆换
企业服务器和云资产平台安全和基础设施团队IAM、网络和计算管理员CIO/CISO 和架构预算负责人大规模铺开前先做混合试点先收集后解密担忧,以及供应商生态成熟度
OEM 和服务器平台提供商产品经理和硬件架构师嵌入式安全和固件团队产品 P&L 负责人将模块集成进下一版产品和改造套件受监管客户带来的渠道拉动
金融、医疗和电信垂直行业行业安全和合规负责人应用、身份和网络运维人员业务线和安全预算服务占比较高、叠加合规要求的迁移记录长期保存需求和监管压力

买方和付款方往往不是同一方。EigenQ 最有吸引力的路径,是借助渠道或 OEM 集成,让一个产品触达大量受监管部署。

[CM003, CM012, CM013, CM014, CM015, CM016]
FM003: 买家 / 细分市场图

最相关买家同时具备长期数据暴露、复杂基础设施和采购流程。

[CM013, CM014, CM015, CM019, CM024, CM026]

2.4 增长驱动、采用约束与时点

最强的需求驱动真实且清晰:NIST 已在 2024 年 8 月敲定首批 PQC 标准,CISA 现在为具备 PQC 能力的产品类别发布买方指南,White House 和联邦生态抬高了迁移议程,CNSA 2.0 也让国家安全时间线始终在场。这些力量给能够提供实用迁移路径的供应商带来少见的自上而下拉力。但约束同样关键。Cloudflare 把转型描述为实质上的两次迁移,警告不要出现「加密拖延」,并显示证书迁移仍落后于密钥协商采用。NIST 的迁移工作强调互操作性和实施复杂度,多份市场摘要也把技能短缺、性能开销和集成成本列为核心阻力。结果是,市场有真实紧迫感,却要慢慢改企业底层管线。只有当 EigenQ 能借 OEM 集成和渠道触达降低迁移摩擦时,环境才会利好公司;否则,制造需求的同一套复杂性也会推迟订单,把试点拉成长达数年的项目。[CM004, CM017, CM018, CM020, CM021, CM023]

增长驱动因素与约束表
驱动因素 / 约束方向时间点影响尽调问题
NIST 已最终确定 FIPS 203/204/205驱动现在建立技术基线,降低标准化不确定性EigenQ 技术栈哪些部分能清晰对应最终标准?
白宫 / 联邦迁移压力驱动2026-2030加快联邦机构和承包商规划EigenQ 管线中真正来自联邦的占比多少,企业外溢又占多少?
CISA 买方指引与 GSA 峰会活动驱动2026+表明采购正在从抽象研究走向常态化EigenQ 是否已进入实际采购、试点或 RFI 流程?
先收集后解密风险驱动当前提前释放保密周期长行业的需求哪些目标垂直行业短期预算权限最清晰?
实施成本与基础设施复杂度约束当前放慢大规模部署,拉长销售周期哪种部署模式最能降低整体拆换成本?
技能短缺与密码敏捷性缺口约束当前催生服务和集成伙伴需求EigenQ 方案中有多少必须包含赋能或伙伴主导服务?
性能 / 兼容性开销约束试点到生产在延迟敏感或遗留环境中可能拖住采用EigenQ 在真实生产平台上有哪些基准测试数据?
市场分母尚不成熟,采购路径长约束当前至中期让估值叙事比收入转化更容易管线中有多少是设计导入、试点或已签订单,又有多少只是主题兴趣?

驱动因素足以形成自上而下的需求,但约束意味着商业机会会在不同买方和多个预算周期里不均衡释放。

[CM004, CM017, CM018, CM020, CM021, CM023]
FM004: 采用漏斗或价值链图

PQC 采用通常是分阶段迁移项目,不是即时产品替换。

[CM004, CM016, CM020, CM025, CM027]

2.5 展项

Chapter 03

03竞争对手

3.1 竞争格局与同业类别

EigenQ 面对的不是一个干净的单一同业集合,因为后量子市场仍围绕不同买方任务组装。SandboxAQ 和 QuSecure 主要在大型企业和政府的密码资产盘点、修复和迁移编排上竞争。ISARA 和 evolutionQ 更接近密码敏捷性和迁移赋能专家;PQShield、SEALSQ 和 Crypto4A 则强调嵌入式、硬件或硅根实现。行业摘要还显示,Thales、IBM、AWS、DigiCert、Entrust 等大型既有厂商和系统集成商已经在嵌入或咨询 PQC,这意味着 EigenQ 同时面对聚焦型创业公司,以及大得多的平台打包出来的功能集。买家的实际问题因此不是“哪家公司做得完全一样?”,而是“谁能以最低运营风险,最快迁移我的基础设施盘点、密码控制和可信硬件?”在这个问题上,EigenQ 最接近的对手,是兼具硬件或基础设施可信度与迁移叙事的供应商;最大的战略压力,则来自已经掌握安全运营或采购关系的公司。[CP001, CP002, CP003, CP004, CP005, CP006]

竞争对手概况表
竞争对手类别规模或融资信号目标细分市场差异化局限
SandboxAQ迁移平台 / 量子安全平台融资超过 $1B,行业报道提到 $1.4B+国防、金融、电信、大型企业、联邦清点、修复、联邦紧迫性、资金充足更宽的 AI + 量子产品组合,可能让其 PQC 切入点比 EigenQ 更不偏硬件
PQShield嵌入式 PQC IP 和硅片行业报道提到 B 轮和 91 人规模半导体、嵌入式、政府迁移项目软件库,加上硬件加速器和芯片级集成更像组件供应商,而不是完整迁移平台
QuSecure密码敏捷性和修复平台获 WEF 认可的私营平台;伙伴主导 GTM电信、金融、国防、企业网络实时密码资产清点,加上快速修复叙事硬件根信任叙事弱于 EigenQ
ISARA密码敏捷性工具包和资产清点经营多年的专注厂商,具备联邦分销渠道公共部门、银行、嵌入式和证书密集环境证书和清点导向强,加上混合迁移支持在物理信任硬件上差异化较弱
SEALSQ安全半导体和 PKI 平台上市公司运营披露,加上广泛 IoT 安全栈IoT、设备身份、工业、电信、安全通信硬件信任根、安全微控制器、PKI、配置发放更宽的 IoT 布局可能稀释其对数据中心服务器改造的聚焦
evolutionQ量子安全平台和咨询行业报道提到央行和电信验证案例政府、金融、电信、服务主导迁移路线图规划、混合架构、咨询和平台工具咨询占比高的打法,作为产品厂商扩张可能更慢

该画像表混合了官方产品页和独立行业报道,因为很少有私营厂商披露标准化收入或客户数量。

[CP001, CP002, CP003, CP004, CP005, CP006]
FP001: 竞争定位图

纯专注竞品按硬件强度和迁移控制影响力聚类,而不是按单一的「量子安全」概念划分。

[CP033, CP034, CP037]

3.2 能力与产品对比

最清晰的能力分野,在迁移发现供应商与硬件根实现供应商之间。SandboxAQ 的 AQtive Guard、QuSecure 的 QuProtect 和 ISARA Advance 聚焦发现、盘点、态势分析和跨既有密码资产的修复。PQShield、SEALSQ、Crypto4A 和 EigenQ 则更直接围绕软件库、嵌入式实现、硬件加速器、安全元件或设备根信任竞争。这个区别很重要,因为买家可能分阶段采购:先盘点并规划问题,再部署硬件、固件、证书或密钥管理升级。EigenQ 的优势,是把一套全栈硬件根信任架构与 OEM 集成、公共部门服务器现代化绑定起来。劣势在于,一些对手的产品故事更简单:QuSecure 卖清晰的修复平台,PQShield 向芯片和固件团队卖 IP 与加速器,SEALSQ 已经是一家上市半导体安全公司,拥有更宽的 IoT 身份栈。因此,能力之争不在于谁提到 NIST 标准,而在于每家供应商能可信占住迁移栈的哪一层。[CP011, CP012, CP013, CP014, CP015, CP016]

功能 / 能力矩阵
采购标准EigenQSandboxAQPQShieldQuSecureISARASEALSQ
密码资产清点与发现部分 / 隐含有限有限
硬件根信任或硅片安全有限有限有限
嵌入式或 OEM 集成
联邦 / 公共部门迁移表述
PKI / 证书生命周期深度
公开可见的伙伴 / 渠道杠杆

这些评级是基于公开材料的有证据序数判断,不是基准测试分数。“强”表示该能力是公开产品叙事的核心,不一定意味着商业上占主导。

[CP012, CP013, CP014, CP015, CP016, CP017]
FP002: 功能广度 / 能力图

最明显的分野在迁移控制平面厂商与嵌入式硬件 / 硅厂商之间。

[CP014, CP015, CP035]

3.3 分销、切换成本与买方权力

分销力是这个市场最被低估的竞争变量之一。EigenQ 正尝试借 HPE、WNC、TD SYNNEX、Intel 和 AMD 相关生态动作触达买家;如果这些动作转成合格平台和可复用采购渠道,威力会很大。但竞争对手也在争取杠杆式触达:ISARA 通过 Carahsoft 拿到联邦分销,SandboxAQ 强调与联邦机构和大型企业合作,QuSecure 强调伙伴牵引的企业部署,PQShield 面向半导体和政府项目,设计导入可扩展到大量设备。切换成本呈混合状态。发现和盘点平台会因为映射大型资产中的证书、密钥和密码态势而变黏;嵌入式或硬件根方案一旦被认证进芯片、板卡、固件或公共部门服务器捆绑包,也会变黏。这意味着,当硬件根信任成为设计决策,而不只是软件功能需求时,EigenQ 的机会最强。反过来,如果客户停留在软件优先迁移阶段的时间长于预期,拥有低摩擦发现和修复流程的平台供应商可能先拿走预算。[CP021, CP022, CP023, CP024, CP025, CP026]

定价 / 打包对比
厂商公开定价可见度打包模式包含能力主要未知项
EigenQ无公开定价通过 OEM 或渠道集成销售硬件和软件模块熵、身份、可信执行、PQC 层标价、部署经济性和实际渠道利润率未披露
SandboxAQ无公开定价平台和企业解决方案打包清点、风险分析、修复规划按席位、资产或企业定价未公开
PQShield无公开定价库、SDK、内核、加速器和授权嵌入式软件和硬件 PQC 组件版税、NRE 和支持服务经济性未公开
QuSecure无公开定价面向探查、报告和修复的平台模块发现、编排、策略、迁移定价如何随资产数量或环境扩展未公开
ISARA无公开定价工具包、SDK、资产清点和咨询服务证书管理、密码资产清点、混合迁移软件与服务的收入组合不清晰
SEALSQ无简单公开标价安全半导体、信任服务、PKI、配置发放微控制器、安全元件、PKI、信任服务单位经济性随设备量和设计导入规模变化

竞争对手官网披露打包方式和定位,远多于实际商业定价;因此本表聚焦变现形态和缺失信息。

[CP020, CP022, CP023, CP024, CP025, CP026]
FP003: 护城河 / 就绪度 KPI

竞争持久性不仅取决于 PQC 实施深度,也同样取决于渠道控制和迁移工作流归属。

[CP028, CP036, CP038]

3.4 护城河耐久性、既有厂商与替代风险

EigenQ 的护城河叙事建立在三个想法上:硬件根信任比纯软件叠加层更耐久,OEM 和公共部门合作加速可信度,监管迁移压力奖励能够改造长寿命基础设施的供应商。这些确实是优势,但没有一项不受挑战。PQShield、SEALSQ、Crypto4A 和 QuintessenceLabs 都在讲某种硬件或熵支撑的差异化。SandboxAQ、QuSecure、ISARA 和系统集成商如果成为迁移决策和政策报告的控制平面,未必需要同样的硬件故事。同时,云、HSM、证书和网络领域的大型既有厂商可以把 PQC 吸收到客户已经购买的产品中,削弱选择独立供应商的紧迫性。因此,最深的反向证据是商品化风险:随着 NIST 标准成熟,PQC 的某些层可能变成入场标配,价值转向分销、集成易用性和生命周期管理。只要 EigenQ 能证明硬件根信任实质改善采购、保障和运营结果,仍然可以胜出。但如果这些收益没有在客户部署中被证明,资金更足或分销更强的对手可以很快压缩差异化。[CP029, CP030, CP031, CP032, CP034, CP035]

护城河耐久性 / 竞争风险清单
护城河主张威胁严重性重要性缓释措施或尽调问题
硬件根信任PQShield、SEALSQ、Crypto4A 和其他偏硬件厂商也声称具备物理或硅片根差异化如果买方能从别处采购类似模块,单靠硬件可能并不独特验证 EigenQ 在服务器环境中是否具备更强的资质认证、性能或保障证明
OEM 和渠道杠杆合作伙伴可能更偏好中立的多厂商生态,或打包自有控制能力分销权力可能掌握在 HPE、TD SYNNEX、Intel 或 AMD 手里,而不是 EigenQ要求提供单一来源定位、附加率和设计定点耐久性的证据
监管时点顺风标准可能让功能商品化,并偏向已有装机基础的在位者PQC 变成入场门槛后,价值可能从算法转向工作流所有权跟踪 EigenQ 控制的是策略、生命周期管理,还是只有组件层
公共部门匹配度联邦和国防采购可能奖励已有合同、且拥有 Carahsoft 等转售商的厂商小厂商可能被自己不掌握的合同基础设施挤出核验采购工具、转售商准入和批准供应商状态
全栈定位客户可能先向一家厂商购买发现能力,再向另一家购买硬件迁移控制平面可能在信任硬件选型前就吃掉预算评估 EigenQ 能否在周期早期锚定发现、评估或策略工作流

该清单强调差异化面临的战略风险,而不是泛泛产品风险;用途是判断护城河耐久性,不是单纯给技术质量排序。

[CP027, CP028, CP029, CP030, CP031, CP032]

3.5 展项

Chapter 04

04财务

4.1 收入模式与变现形态

公开证据支持一个清晰的变现形态,但不足以拼出完整利润表。EigenQ 的网站、产品措辞和合作伙伴公告显示,公司业务混合了硬件根安全模块、后量子软件层、集成能力和渠道赋能的服务器部署,而不是简单的按席位计费 SaaS。WNC 合作描述了面向 EigenQ Post-Quantum Unit 硬件和 Quantum Encryption Module 软件栈的合同制造与联合设计服务;TD SYNNEX 与 AMD 合作则把商业化框定在基于 EPYC 的服务器环境后量子就绪上。这在经济上重要,因为收入可能来自硬件出货、平台集成、赋能工作,也可能来自软件或生命周期支持;但没有已审阅来源披露标价、合同规模、平均部署金额,或产品、软件和服务元素之间的收入确认方式。结论是,商业化路径真实,但收入组合不清,定价透明度弱。[CI001, CI004, CI005, CI006, CI007, CI008]

收入来源表
收入来源机制单位或触发因素当前公开状态收入质量尽调问题
硬件安全模块向服务器和边缘环境销售 PQU 卡或相关安全硬件按单元 / 按部署已描述商业化路径;未公开披露已签约收入中低要求按模块系列提供出货量、ASP 和毛利率
量子加密软件栈随硬件和平台集成授权或捆绑销售的软件按服务器、环境或合同产品范围已描述;定价和收入确认未披露中低要求提供软件附加率和经常性支持条款
OEM / 平台集成通过 HPE、AMD 和生态集成获得设计导入或认证收入按设计定点 / 项目伙伴路径可见;合同经济性未公开要求提供已签署设计定点、NRE 条款和部署时间表
渠道赋能企业部署通过 TD SYNNEX 或类似采购渠道销售按订单 / 伙伴计划渠道打法已描述;订单量和实际折扣未公开中低要求提供转售商协议经济性和预测管线
部署和迁移支持围绕 PQC 现代化提供评估、集成和赋能按项目 / 服务合作从商业化材料推断,并非单独披露要求提供服务组合、利用率以及产品销售附加率

公开证据显示的是变现形态,而不是某一期间已签约收入。

[CI004, CI005, CI006, CI007, CI010, CI011]
定价 / 变现表
产品或渠道公开定价可见度变现形态已知包含能力主要未知项
EigenQ 网站产品未公开标价清单硬件加软件平台定位扎根硬件的信任、qTPM、熵、PQC 能力未公开 ASP、支持费或最小起订量
WNC 制造合作未公开定价硬件生产加 QEM 软件栈集成PQU 硬件、QEM 软件、制造扩量未披露版税、转移价格或利润分成
与 HPE 相关的服务器改造路径未公开定价经认证基础设施套件或集成路径ProLiant 与公共部门服务器现代化叙事未见套件价格、附加率或部署数量证据
TD SYNNEX 与 AMD 合作未公开定价渠道支持的服务器就绪计划与部署评估、平台适配、渠道启用定价究竟是订阅、设备、项目制还是混合模式,公开信息未说明
政府 / 国防部署未公开定价可能走定制合同和合规驱动采购任务连续性、高保障基础设施、分阶段迁移未公开合同规模、期限或续约结构

变现看起来更偏定制化、由合作伙伴居中撮合,而不是像 SaaS 标价那样标准化。

[CI008, CI009, CI010, CI014, CI015]
FI001: 收入模型衔接图

EigenQ 公开可见的收入路径,大致从硬件和软件组件出发,经 OEM 或渠道整合,进入受监管的基础设施部署。

本图只梳理公开可见的商业化路径,不构成预测。

[CI004, CI006, CI007, CI008, CI009, CI010]

4.2 销售动作与单位经济模型代理指标

EigenQ 的 GTM 动作看起来由合作伙伴牵引、偏重企业客户;虽然核心数字缺位,仍能提供一些销售效率线索。HPE、AMD、WNC 和 TD SYNNEX 被描述为集成、制造和渠道路径,而不只是营销标识,说明公司试图借 OEM 关系和生态采购来卖,而不是依靠直接、广泛的自助采用。如果一次设计中标可以扩展到许多系统,这种方式会很高效;但已兑现经济收益也可能要与合同制造商、分销商和平台伙伴分享。公开证据指向政府、国防、关键基础设施和其他拥有长寿命系统的受监管买家;这些客户能支撑大单,也常常带来更长的资质确认周期和部署支持需求。由于没有已审阅来源披露获客成本、分销商抽成率、安装毛利、附加率、续约模式或支持负担,单位经济模型只能定性代理:战略匹配强,公开变现披露弱,转化速度不确定。[CI014, CI015, CI016, CI017, CI030, CI031]

单位经济模型表
指标公开数值或代理指标置信度重要性尽调要求
获客成本未披露;合作伙伴主导的企业销售意味着销售接触重、投入高决定渠道杠杆能否抵消漫长销售周期按直营账户和合作伙伴导入账户索取 CAC
回本周期未披露检验硬件和服务毛利能否足够快地收回获客与集成成本按产品线和部署类型索取回本周期
毛利率未披露;含硬件和制造环节,毛利率可能低于纯软件判断扩量能否带来经营杠杆的核心变量索取混合口径及产品级毛利率历史
支持与部署负担未披露;在受监管环境中可能不轻高强度支持会摊薄硬件和软件经济性按账户索取现场部署人工、保修和支持成本
渠道经济性未披露;合作伙伴分销可能要与 OEM 和分销商分走价值判断实际 ASP 和贡献毛利所必需索取分销商折扣、MDF 和合作伙伴利润率安排

上述指标都很关键:公开记录能证明商业化存在,却不给出可做标准化比较的数字。

[CI014, CI015, CI016, CI030, CI031, CI032]
FI002: 单位经济模型衔接图

公开证据显示,利润率形成更依赖伙伴分销、硬件含量和部署支持,而不是纯软件订阅。

节点只标出成本和价值驱动因素;公开资料没有经审计的金额。

[CI015, CI016, CI030, CI031, CI032, CI036]

4.3 成本结构、资本需求与融资依赖

成本结构比收入更容易推断,却难以验证。EigenQ 并不是一家轻量软件供应商:公开材料强调硬件根信任、量子熵硬件、OEM 集成、制造扩产,以及部署到服务器和关键基础设施环境。这些事实意味着物料清单成本、资质确认工作、库存或生产计划纪律、伙伴利润和支持义务,而纯软件 PQC 供应商可能避开这些成本。因此,拟议业务合并在财务上处于核心位置。公司和交易材料称,该交易给予 EigenQ 约 $3 billion 估值,并由 SVAQ 信托账户在赎回和交易费用前约 $215 million 支撑,所得资金计划用于商业化、制造扩产、合作伙伴关系和扩张。但同一批文件也警告,实际结果取决于赎回、盈利假设、交易成本、定价压力、供应链问题,以及公司维持合作伙伴利益的能力。这意味着标题资本故事有意义,但带条件,并不是到手现金确定性。[CI002, CI003, CI018, CI019, CI020, CI021]

资本充足性表
资本因素公开证据当前状态重要性尽调要求
披露口径企业价值约 $3B 备考 EV已公告给估值预期定锚,但不等于经营现金索取股权结构表、股数测算和稀释桥
信托现金支持SVAQ 信托在赎回和费用前约 $215M已公告但有条件公开点名的主要扩张资金来源索取最低现金条件和赎回敏感性
募资用途商业化、制造扩量、战略合作与扩张仅有叙事决定资金是推动收入转化,还是摊向分散的路线图扩张按工作流索取董事会批准的资金用途计划
额外融资可见度未在已审阅公开材料中看到 PIPE 金额或债务额度披露不清晰信托若被赎回侵蚀且没有兜底,可用现金可能大幅压缩索取 PIPE 承诺、债务条款和备用融资
股东行为预计 EigenQ 现有股东将基本滚存全部股权;预计不会有重大套现支持性强,但不产生现金利益一致有帮助,但替代不了经营流动性索取禁售条款和交割后股权结构表

交易的资本叙事方向上有支撑,但最终可用现金仍高度受制于尚未公开对齐的因素。

[CI001, CI002, CI003, CI018, CI019, CI020]
FI003: 财务估算区间

公开记录给出了清晰的交易锚点,但经营区间仍很宽,或根本不可得。

只有已披露锚点以数字呈现;未知经营指标以不可得边界表示。

[CI001, CI002, CI013, CI028]
FI004: 资本强度 / 现金流图

现金逻辑从有条件的信托支持延伸到商业化和制造需求,赎回与披露缺口是主要断点。

这是依赖关系图,不是现金流量表。

[CI002, CI003, CI018, CI021, CI022, CI023]

4.4 公开财务缺口与投资判断边界

从投资定价角度看,最深的问题不是战略叙事不足,而是缺少对齐后的财务披露。已审阅的 SEC 材料、公司页面、合作伙伴公告和文件索引中,没有任何公开来源提供经审计的 EigenQ 收入、ARR、毛利率、运营费用、月度烧钱、非受限现金、债务、积压订单、客户集中度、递延收入或合同负债。文件跟踪来源确认 SVAQ 一直维持公开报告节奏,2026 年 7 月文件索引也确认公告后提交了更多交易材料,但已审阅文本仍没有暴露标的公司的真实 P&L 或现金状况。公开披露中也没有 PIPE 金额,或信托现金与滚入股权之外的其他增量融资。因此,跑道、稀释风险、高赎回情景下资本是否充足、当前商业化是否增厚毛利率等关键判断,仍取决于私下尽调请求,而不是完整公开记录。[CI013, CI026, CI027, CI028, CI029, CI030]

公开财务缺口表
缺失指标缺失为何重要当前公开代理指标具体尽调路径
当前收入或 ARR无法研判收入质量,也无法比较远期倍数公开信息只有商业化表述和合作伙伴路径按产品、渠道和地区索取过去 8 个季度收入
当前现金和月度烧钱无法建模现金续航期和稀释风险已披露信托账户,未披露标的现金索取月末现金余额和 24 个月烧钱历史
按硬件、软件和服务拆分的毛利率无法判断单位经济模型或规模杠杆硬件占比较高的叙事意味着毛利结构复杂按收入流索取毛利率桥
积压订单、设计定点和订单转化无法把销售管线可信度与近期收入节奏挂钩公开合作伙伴公告描述的是路径,不是订单索取已签积压订单、预测转化和取消历史
赎回与 PIPE 敏感性披露口径的信托支持可能高估交割后流动性申报文件提到赎回和调整,但这里没有最终现金下限索取最低现金契约、PIPE 文件和下行情景流动性模型

这些缺口是承保的具体卡点,不是泛泛要求「更多数据」。

[CI013, CI022, CI027, CI028, CI029, CI036]

4.5 财务判断

相比仍在概念阶段、尚无产品的量子公司,EigenQ 的商业化框架更可信。它有公开的合作伙伴路径,一笔可能增加市场可见度的交易,官方信息也把资金用途绑定到商业化和制造,而不是只投向开放式 R&D。话虽如此,当前公开财务包仍不足以支撑常规投资尽调。多头情形是:信托账户所得资金、滚入股权和渠道伙伴合在一起,给 EigenQ 足够资本和市场通路杠杆,把监管紧迫性转成硬件与基础设施收入。空头情形是:多产品量子路线图、不确定赎回、偏硬件的成本结构,以及缺位的运营披露,让投资者无法检验业务是否真的资本高效。平衡结论是,收入质量仍未证明,利润率路径仍不透明,SPAC 加合作伙伴网络应被视为一座融资桥;在看到私下收入、积压订单和烧钱数据前,不能有把握地定价。[CI018, CI019, CI022, CI029, CI030, CI031]

4.6 展项

Chapter 05

05产品与技术

5.1 产品模块与客户任务

EigenQ 对产品的定义不像单一独立设备,更像一层信任基础设施,服务必须穿过后量子转型的基础设施。从公司网站到合作伙伴公告,反复出现的组件包括硬件根身份、量子熵生成、后量子密码软件、密码敏捷性工具,以及能嵌入服务器、网关、边缘系统和长寿命设备的部署模型。公开客户任务很具体:保护通信、建立设备身份、支持证明、现代化密钥生成和生命周期管理,并在不整体替换的情况下改造现有 Intel Xeon 或 AMD EPYC 环境。WNC 公告点名 PCIe、M.2 和 1U 安全服务器模块,补充了实体形态线索;Intel 和 AMD 公告则把技术描述成已部署基础设施的升级路径。这一点重要,因为它说明 EigenQ 卖的是嵌入买方工作流和已安装硬件资产,而不只是抽象密码原语。[CE001, CE002, CE003, CE004, CE005, CE006]

产品模块 / 资产矩阵
模块或资产主要用户状态或成熟度差异化尽调缺口
qTPM 与设备身份基础设施安全团队和 OEM 集成商已公开描述身份扎根在硬件中,而不是仅叠一层软件索取数据表、证明流程和认证证据
量子熵生成高保障系统架构师已公开描述熵被定位为 PQC 系统的基础信任输入索取熵测试结果和硬件来源细节
PQC+ 加密库平台与安全工程团队已公开描述把标准时代算法接到可部署基础设施上索取 API、性能和互操作性文档
密码敏捷工具迁移和安全运营团队已在合作伙伴材料中公开描述把转换定义为运营迁移,而不是简单更换算法索取资产清单、策略和更新工作流细节
服务器与边缘模块(PCIe、M.2、1U)OEM、集成商和公共部门部署方已描述试点和生产路径可改造进现有系统的物理形态索取 SKU 列表、可供货情况和现场部署参考

公开模块描述足以勾勒技术栈,但细节还不足以替代正式产品文档。

[CE001, CE002, CE003, CE006, CE007]
工作流 / 用例表
用户任务当前工作流压力EigenQ 方案声称可量化收益限制
保护长期加密通信遗留基础设施面临量子迁移压力在现有系统中改造接入 PQC 和熵层避免全量拆换叙事未见真实工作负载的公开性能基准
建立可信设备身份高保障场景里,仅靠软件凭证可能不够使用以 qTPM 为根的身份和证明硬件信任叙事更强未审阅到公开的独立证明测试包
为 CNSA 2.0 准备服务器资产联邦和国防买家需要可落地迁移路径Intel 与 AMD 环境就绪路径把标准压力映射到具体服务器环境未披露实际客户部署规模
扩大安全模块制造原型安全硬件必须实现可重复量产使用 WNC CM/JDM 和与 HPE 相关的验证路径比单靠内部制造更快扩量对合作伙伴执行的依赖仍高
通过可信渠道部署大型买家往往通过平台和分销生态采购TD SYNNEX 与 OEM 协同可能降低采购摩擦渠道条款和附加率未公开

本表关注客户工作流匹配度,而不是部署规模的商业证明。

[CE008, CE009, CE010, CE016, CE018]
FE001: 产品架构图

EigenQ 公开讲述的产品路径,是把信任硬件、PQC 软件和生态集成层层叠进已部署基础设施。

各层反映公开描述,不是完整工程物料清单。

[CE001, CE004, CE007, CE012, CE013]

5.2 架构与运营模型

公开架构叙事形态一致,尽管实施细节仍不完整。EigenQ 反复描述一套由 qTPM 和量子熵锚定的硬件信任根,叠加 PQC+ 密码库和可接入服务器、高保障环境的集成层。Intel 公告称,该栈可帮助现有 Xeon 基础设施保护加密通信、工作负载、身份、密钥生成和证明;AMD 与 TD SYNNEX 材料称,类似平台可以评估、对齐并迁移基于 EPYC 的环境。WNC 补上制造和形态层,显示 EigenQ 技术不只是概念,而是已经映射到实体模块和合同制造路径。架构优势在于,EigenQ 试图在基础设施层解决部署和保障。架构风险在于,公开来源还没有提供足够底层文档,无法验证生产中的吞吐、互操作边界、故障切换行为、更新机制或长期可维护性。[CE012, CE013, CE014, CE015, CE016, CE017]

技术 / 运营架构表
层级或组件作用依赖风险
量子熵为安全基础框架提供可信随机性硬件设计和验证熵质量主张需要产品级证据
qTPM / 硬件信任根锚定设备身份与证明OEM 兼容性和固件集成混合硬件资产中部署复杂度可能上升
PQC 库在可部署系统中落地 ML-KEM / ML-DSA 时代的密码体系标准对齐和软件生命周期管理互操作性和更新细节尚未完全公开
密码敏捷工具支持分阶段迁移和策略变更接入客户运营环境控制平面细节弱于营销叙事
制造与物理封装把信任组件做成可部署模块WNC 及盟友生态执行供应、认证和扩量问题可能拖慢推出

运营架构足够具体,可以理解各层作用;但要审计完整工程实现,信息仍不够。

[CE012, CE013, CE014, CE019, CE029]
FE002: 客户工作流 / 运营流程

EigenQ 的运营模型从已安装基础设施切入,借助伙伴支持的部署,把 PQC 就绪信任层插进去。

这是基于公开材料绘制的部署工作流图。

[CE008, CE010, CE012, CE017, CE037]

5.3 集成成熟度与路线图

EigenQ 的成熟度证据,在合作伙伴公告点名实际部署路径时最强;在买家会要求产品级基准时最弱。公开材料显示多条集成路径:HPE 相关 ProLiant 赋能、WNC 支撑的制造、Intel Xeon 改造支持,以及通过 TD SYNNEX 对齐 AMD EPYC。WNC 公告甚至点名试点出货和计划量产时间,Intel 与 AMD 材料则强调与已安装基础设施兼容。这些信号比笼统的“未来量子”叙事更强。领导层和投资者沟通还显示,路线图会从量子安全延伸到 AI、通信、感知和计算;野心更宽,但也可能稀释产品聚焦。实际结论是,EigenQ 更像一个改造和合作伙伴集成平台,成熟度高于一家拥有完整文档和丰富基准的独立产品公司。投资者因此应区分两件事:可见的集成牵引,以及仍未证明的现场性能深度、认证范围和软件生命周期工具。[CE017, CE018, CE020, CE021, CE022, CE023]

路线图 / 发布 / 开发阶段表
日期或阶段功能或里程碑状态含义来源
2025 合作阶段WNC 制造与 HPE 生态启用已公告表明模块和服务器套件的实体扩量路径WNC 新闻稿
2025 年 Q4 / 2026 年初量产和 HPE 认证套件公司声称时间表明产品化可能已越过原型阶段WNC 新闻稿
2026 发布阶段与 TD SYNNEX 合作推进 AMD EPYC 就绪已公告把兼容性扩到另一套服务器生态PRNewswire / TMCnet / TQI
2026 发布阶段Intel Xeon 改造就绪能力已公告强化存量基础设施改造叙事PRNewswire / HPCwire / TQI
更广的战略路线图以安全为牵引,组合延伸至 AI、通信、感知和计算公司声称扩大可选空间,但也可能拉宽执行面SEC / 网站 / 投资者材料

公开路线图更清楚地展示集成和扩张里程碑;正式带版本的软件发布反而不够清晰。

[CE017, CE020, CE021, CE022, CE023, CE024]
FE003: 关键依赖图

产品交付依赖一条链:从标准和芯片生态,延伸到制造与采购伙伴。

依赖图只突出公开可见的依赖项。

[CE006, CE015, CE018, CE030, CE031, CE033]

5.4 差异化与依赖结构

EigenQ 最清晰的差异化主张是,纯软件迁移不足以覆盖长寿命或高保障系统;公司认为买家需要可信熵、硬件根身份,以及位于密码转型底层的量子安全执行脚手架。联邦采购指南强调硬件和软件产品类别都需要采用 PQC,NIST 标准工作也把买家最终必须实施的算法正式化,这些都强化了上述定位。因此,差异化不只是“我们支持 ML-KEM 和 ML-DSA”,而是“我们把这些标准封装成可部署的基础设施组件”。不过,依赖结构并不轻。EigenQ 依赖芯片和平台生态、制造伙伴、标准对齐和采购渠道。只要其中任一环节滞后——无论因为资质摩擦、标准变化还是 OEM 重新排序——即便核心技术论点成立,公司的产品速度也会放慢。因此,伙伴杠杆既是强项,也是技术依赖。[CE028, CE029, CE030, CE031, CE032, CE033]

FE004: 产品成熟度 / 能力图

公开可见的成熟度在伙伴集成叙事上最高,在基准验证或已发布生命周期细节上较低。

[CE017, CE020, CE029, CE039, CE041]

5.5 信任、质量与合规控制

信任故事在战略上很强,但证据仍不均匀。EigenQ 反复引用 FIPS 203 和 FIPS 204 对齐、CNSA 2.0 就绪、联邦部署适配,以及经过验证的熵或 qTPM 信任根。NIST、CISA 和 NSA 材料都支撑更广的技术背景:ML-KEM、ML-DSA 和 SLH-DSA 是已批准标准;迁移预计会覆盖硬件和软件产品类别;买家正在被推向具备 PQC 能力的基础设施。仍不清楚的是 EigenQ 自身认证、测试证据或审计材料的确切范围。一些公司措辞会以产品相邻方式写到「FIPS-certified」或「NIST-certified」,但已审阅公开记录没有为每个模块提供干净的认证台账或性能测试包。换句话说,EigenQ 与标准体系高度对齐,但买家或投资者仍需要产品级文档,覆盖认证、安全更新实践、可靠性指标和合规边界。[CE035, CE036, CE037, CE038, CE039, CE040]

信任 / 质量 / 合规表
控制项或标准状态范围缺口
FIPS 203 / ML-KEM 对齐公开引用PQC 产品所处的密钥封装标准语境需要逐产品的实现和验证证据
FIPS 204 / ML-DSA 对齐公开引用PQC 产品所处的数字签名标准语境需要模块级证明和生命周期支持细节
FIPS 205 / SLH-DSA 语境有标准格局支撑与长期信任相关的哈希签名替代方案未见 EigenQ 公开的已审阅产品映射
CNSA 2.0 就绪表述在公开材料中反复出现联邦与国防迁移定位就绪主张强于已发布测试证据
已验证熵 / qTPM 信任主张在公司材料中反复出现扎根硬件的信任叙事未审阅到完整公开认证台账或可靠性仪表盘

标准对齐证据充分;但公开记录中的产品级证明材料仍不完整。

[CE035, CE036, CE037, CE038, CE039, CE041]

5.6 展项

Chapter 06

06客户

6.1 客户细分与购买中心

与其说 EigenQ 的公开客户基础是一张已披露账户名单,不如说它是一组目标客群。交易材料、网站和合作伙伴材料中,公司反复强调政府、国防、关键基础设施和高保障企业环境是初期商业化目标。实际买家看起来包括基础设施安全团队、联邦或国防采购机构、OEM 平台伙伴,以及由渠道牵引、正在为后量子就绪改造 Intel Xeon 或 AMD EPYC 资产的企业账户。用户很可能是需要证明、密码敏捷性、密钥管理和工作负载保护的安全、平台与运营团队;付款方可能是政府项目、主承包商、基础设施运营方或企业平台所有者。这种切分很重要,因为它意味着少量高价值、高摩擦账户,而不是广泛的自助客户基础。渠道触达和合规拉力也是客户故事的一部分,不只是支撑性的 GTM 细节。[CU001, CU002, CU003, CU004, CU005, CU006]

客户分层表
客群买方、用户或付款方用例规模或战略价值收入或战略含义缺口
联邦和国防项目项目办公室、主承包商、安全架构师CNSA 2.0 驱动的服务器和通信现代化战略价值高,公开数量可见度低可能带来大型合规驱动部署未公开机构、合同工具或授标清单
关键基础设施运营方基础设施所有者和安全团队保护长寿命系统和安全通信具有战略重要性的目标客群支撑紧迫性叙事和长更换周期已审阅公开记录中未见具名运营方部署
企业服务器资产平台与基础设施团队Intel Xeon 与 AMD EPYC 就绪和改造存量基础巨大可能推动公共部门之外的更广商业扩张未公开账户数量或转化指标
OEM 与集成商生态HPE、WNC、集成商、渠道伙伴将 PQC 信任层打包或嵌入系统如果设计定点转化,将产生放大效应合作伙伴渠道可能加速触达终端客户归属和经济性不清楚
任务导向通信用户航天、安全视频、高保障通信团队加密通信、身份、远程证明BlackVe 提供了最清晰的具名用例验证证明方案贴合高价值任务工作负载公开具名证据仍只有这一组

公开证据最能说明细分市场匹配度,最缺的是已披露客户数量。

[CU001, CU002, CU003, CU004, CU005, CU006]
FU001: 客户旅程图

EigenQ 公开可见的客户旅程,从监管压力和基础设施评估开始,走向改造部署和潜在扩张。

旅程图根据公开伙伴和交易材料重构,并非公司发布的 GTM 图。

[CU001, CU004, CU010, CU014, CU021, CU031]

6.2 公开采用与具名证据

已审阅公开记录中最强的具名客户证据是 BlackVe。EigenQ 面向 Intel 的公告和多个第三方镜像称,BlackVe 计划把 EigenQ 兼容 Intel 的后量子技术,用作国家安全和空间场景中安全视频系统的基础安全层。这在战略上重要,因为它比通用客户标识 或未具名试点更具体:它把一个具名合作伙伴/客户,与用例、运行环境和任务画像连在一起。BlackVe 之外,公开证据变得更薄。WNC 公告称试点数量已向部分集成商出货,且 HPE 认证服务器捆绑包有望推出,但这些是路径信号,不是具名终端客户部署。AMD 和 TD SYNNEX 材料同样显示了一条通向公共部门和企业环境的渠道路径,却没有点名谁已经购买或扩张。结论是,真实采用信号存在,但具名生产证明集仍极窄。[CU010, CU011, CU012, CU013, CU014, CU015]

客户增长 / 采用轨迹表
指标公开值日期来源置信度含义缺失分母
具名客户证据1 个明确具名公开用户(BlackVe)2026-07-06Intel 方面公告说明公司至少有一个面向任务场景的公开验证点未披露客户总数
集成商试点出货已向部分集成商发出试点数量2025-06-23WNC 新闻稿说明进展已越过概念阶段未披露集成商数量或转化率
认证套装时间表HPE 认证服务器套装目标在 2026 年初推出2025-06-23WNC 新闻稿表明公司计划为更大范围部署做好准备未见公开证据说明套装体量或客户采用
AMD 公共部门渠道就绪度披露了渠道路径,但未量化2026-06-15PRNewswire / TMCnet / TQI说明还有一条扩张路径未披露账户、订单或部署数量
目标细分市场广度政府、国防、关键基础设施、企业2026-06-17 至 2026-07-06SEC / 新闻稿 / 镜像稿契合广阔 TAM未披露按收入或部署划分的细分市场结构

公开采用证据只能看出方向,不能衡量规模。

[CU001, CU010, CU012, CU013, CU016]
具名客户验证表
客户或验证面细分市场部署或用例生产环境 / 试点结果或证据局限
BlackVe国家安全航天 / 安全通信使用 EigenQ Intel 兼容 PQC 技术的安全视频系统和航天应用早期部署或承诺使用信号带有任务场景的具名第三方引述未披露合同规模、上线生产指标或续约数据
部分集成商集成商 / OEM 生态PQU Gen2 硬件试点数量试点说明硬件已进入集成商手中终端客户未具名,部署结果未披露
HPE 认证套装路径公共部门和国防服务器环境计划推出 HPE 认证 ProLiant 套装认证 / 规模化前说明进入买方环境的具体路径不是具名终端客户,也未证明生产部署
AMD EPYC 就绪渠道公共部门和企业服务器环境通过 TD SYNNEX 评估并部署的路径渠道就绪显示可落地的采购路径没有具名买方或购买证据

本表把一个具名客户和三个具名验证面放在一起,因为公开终端客户披露很稀少。

[CU010, CU011, CU012, CU013, CU014, CU015]
FU002: 采用 / 部署漏斗

公开可见的采用路径,从目标细分市场和伙伴渠道,进入少数具名或隐含的部署验证。

本流程抽象当前客户验证集;它不是公司上报的漏斗。

[CU001, CU004, CU010, CU013, CU020, CU033]
FU003: 客户验证质量矩阵

BlackVe 的证据质量最高;没有具名终端客户的广泛伙伴主导细分市场主张,质量较低。

[CU017, CU019, CU032, CU033]

6.3 留存与耐久性可见度

今天的留存几乎全靠推断。没有已审阅来源披露客户数量、NRR、GRR、流失、续约率、合同期限或分群行为。最好的连续性代理指标都是间接的:围绕政府和关键基础设施紧迫性的重复信息,围绕 Intel、AMD、HPE、WNC 和 TD SYNNEX 搭建的合作伙伴生态,以及硬件根集成一旦被认证进已部署系统就会变黏的逻辑。但黏性不等于已测量留存。公开合作伙伴公告也带有限定:经批准且适用的渠道路径、面向已部署系统的技术适配限定,以及没有证明复购或客户满意度的前瞻性表述。当前,耐久性叙事更多建立在基础设施嵌入逻辑上,而不是已披露账户行为。因此,留存仍是论点,不是已测事实。[CU020, CU021, CU022, CU023, CU024, CU025]

留存 / 重复使用 / 满意度表
指标数值或 null细分市场置信度尽调请求
NRR所有细分市场索取分群 NRR,至少按账户类别提供扩张收入
GRR所有细分市场索取按部署类型和年份划分的留存
续约率伙伴主导和直销部署索取续约和支持合同历史
客户满意度或背书具名和未具名账户索取客户访谈,如有跟踪则索取 NPS,并索取部署结果
合同期限 / 粘性如果进入基础设施认证,可推断具备粘性,但公开材料未衡量关键任务和基础设施部署索取合同条款、支持期限和嵌入式足迹证据

公开留存证据几乎空白,因此本表聚焦尽调需索取的问题。

[CU020, CU021, CU022, CU023, CU024, CU025]
FU004: 留存 / 重复队列

留存数据缺失时,示例性耐久场景展示了不同客户验证类型下账户连续性可能如何分化。

这些百分比只是分析师用于尽调的启发式假设,并非公司披露的留存数据。

[CU021, CU022, CU023, CU027]

6.4 扩张、集中度与采购摩擦

EigenQ 的上行和风险紧密相连,因为能够打开扩张的同一批渠道也可能制造集中度。如果 Intel、AMD、HPE 或 WNC 相关路径转化,每个账户都可能具备战略价值,并可跨设备群、工作负载或项目线扩张。BlackVe 显示,一个可信任务伙伴可以支撑相邻的安全通信或空间应用。但集中度风险仍高,因为公开记录没有展示多元化的具名付费客户名单。渠道集中度也重要:TD SYNNEX 和 OEM 伙伴可能控制采购触达;联邦和国防买家又会叠加合规、资质确认和合同摩擦,即便需求紧迫也会拖慢扩张。公开来源还没有说明最强的参考案例究竟是试点、已融资部署,还是大范围生产项目。投资者因此应把伙伴牵引扩张视为可行,但规模化尚未证明。[CU028, CU029, CU030, CU031, CU032, CU033]

扩张与集中度风险表
扩张驱动因素集中度风险影响尽调路径
关键任务部署可向更多工作负载扩张公开证据集中在一个具名客户战略上行空间高,但多元化证据弱索取头部客户收入占比和按账户拆分的销售管线
OEM 和渠道路径能快速放大渠道伙伴可能控制客户入口和经济条款伙伴依赖可能压低定价权索取伙伴来源与直销收入占比
联邦紧迫性可加速采购认证和签约周期仍可能拖慢扩张收入兑现可能滞后于战略价值索取平均销售周期和采购阶段数据
扎根硬件的集成可形成粘性认证失败或部署慢于预期,可能卡住复购持久性仍缺公开证明索取部署到续约的转化历史
细分市场从国防延伸到企业公开证据尚未说明当前到底哪个细分市场在付费战略广度可能掩盖收入集中索取细分市场收入拆分和具名生产账户

让 EigenQ 有吸引力的伙伴主导扩张逻辑,也带来了客户集中和采购风险敞口。

[CU028, CU029, CU030, CU031, CU032, CU033]

6.5 客户判断

EigenQ 已有足够公开客户证据,能说明目标市场真实存在,且至少有一个具名任务导向用户 BlackVe 愿意公开谈及计划部署方向。这强于没有任何外部使用背书的纯概念阶段创业公司。但公司仍缺少足够证据广度,无法有把握地定价客户耐久性。公开材料没有客户数量桥表,没有披露扩张比率,没有独立满意度数据,也没有清晰列出跨机构、企业或关键基础设施运营方的生产部署。客户故事因此可信但集中:与 PQC 紧迫性最高的场景高度对齐,生态路径有意义,直接账户级透明度却很有限。尽调需要把渠道叙事转成账户、部署、续约和集中度数据,才能把客户质量评为真正成熟。[CU010, CU020, CU028, CU033, CU034, CU035]

6.6 展项

Chapter 07

07风险

7.1 按严重程度排序的主要风险

最实质的风险集中在四个相互牵连的依赖项上。第一,交易与融资风险仍然很高,因为 EigenQ 的公开资本故事仍取决于 SPAC 能否交割,以及信托现金能保留多少;赎回、交易费用和任何追加融资需求都可能削薄这笔现金。第二,产品交付风险不小,因为 EigenQ 的商业化叙事靠 WNC、HPE、Intel、AMD 和 TD SYNNEX 推动制造、认证和渠道执行,而不是靠一个完全内生的产品引擎。第三,客户验证风险偏高,因为相对于估值规模和市场进入主张的宽度,公开记录里具名终端客户证据很薄。第四,监管与合规风险可控但不可忽视:公司公开绑定隐私法合规、出口管制、制裁和联邦采购预期,合并协议也显示这些领域是重要陈述与保证主题。单看任何一项都不足以否定故事,但加在一起,在交割、规模化和客户转化拿出更强证据之前,残余风险仍然很高。[CR001, CR002, CR003, CR004, CR005, CR006]

FR001: 风险热力图

最高残余风险集中在融资依赖、伙伴集中和经营披露稀薄的交叉处。

[CR005, CR007, CR008, CR009]

7.2 法律、监管与运营风险敞口

法律和监管风险的重点,不是今天是否存在已知诉讼,而是公司能否满足交易结构和目标市场隐含的义务。业务合并协议和 8-K 摘要把诉讼、隐私与安全、重大合同、知识产权、环境合规、出口管制、制裁和政府批准列为重要事项。隐私政策又承诺遵守 PIPEDA、GDPR、以色列隐私法和其他国际标准;FTC 指引和联邦采购指引则抬高了任何面向安全敏感环境销售公司的运营门槛。运营层面同样如此:公开来源提到安全服务器模块、试点出货、HPE 认证组合,以及伙伴主导的制造或认证。这些是正面信号,但也意味着可靠性、供应、质量和更新控制一旦失守,会很快传导到客户信任和融资信心。简言之,EigenQ 的风险画像不是「未知科学风险」,而是「高标准商业化风险」。[CR011, CR012, CR013, CR014, CR015, CR016]

监管 / 法律风险登记表
规则或问题司法辖区或来源状态可能性严重性缓释措施剩余敞口尽调路径
业务合并交割及审批条件SEC / 股东 / 交易法待决交易文件已形成,律师已介入赎回、审批或条件仍可能阻碍交割复核 S-4 条件、最低现金和最终截止日保护
隐私法合规承诺PIPEDA / GDPR / 以色列隐私法 / 其他适用法律公司称已合规已有公开隐私政策和合同陈述未见公开审计包或事件历史供复核索取隐私控制、DPA 模板和安全审计结果
出口管制和制裁合规EAR / OFAC / 其他国际贸易法已在合并协议中覆盖陈述与保证覆盖合规事项目标市场会放大合规负担索取出口分类分析和制裁筛查控制
知识产权和侵权敞口知识产权局 / 法院 / 合同权利本次未发现公开纠纷中高合并协议覆盖 IP 和未决程序FTO 证据未公开索取专利清单、转让文件和 FTO 审查
诉讼和程序风险法院 / 监管机构已审阅来源中未发现重大公开案件中低协议陈述覆盖诉讼和法律程序未来仍可能出现合并或产品诉讼做法院和案卷检索,并复核陈述与保证的更新确认

法律态势看起来可控,但公开控制证据仍比这些市场的重要性要求更薄。

[CR001, CR011, CR012, CR013, CR014, CR015]
运营 / 质量 / 安全风险登记表
失效模式可能性严重性缓释成熟度剩余敞口未解决缺口
制造放量或模块认证延误未披露生产良率、故障率或进度达成数据
改造环境中的现场可靠性或互操作性故障中低未见公开基准或可靠性看板供复核
安全或隐私控制失效,削弱信任主张中高未见公开事件历史或控制审计包供复核
扎根硬件的模块遭遇供应链中断中高中高伙伴制造集中可能造成瓶颈
签名、密钥管理或更新中的标准落地滞后公开标准对齐证据强于详细生命周期证明

运营风险偏高,因为产品承诺靠真实部署质量兑现,不只靠算法选择。

[CR006, CR018, CR019, CR020, CR021, CR022]
FR002: 风险传导图

多项风险沿着同一条链传导:从伙伴执行和合规,进入客户验证、融资和估值信心。

[CR006, CR010, CR032, CR040]

7.3 合作伙伴、人员与商业模式风险

公司的合作伙伴生态既是牛市论点,也是依赖关系图。WNC 提供制造规模和物理模块封装,HPE 连接公共部门服务器落地,Intel 和 AMD 支撑存量基础设施改造叙事,TD SYNNEX 拓宽渠道触达。这能加快采用,但也意味着节奏、质量和经济性可能受制于有自身优先级的第三方。客户章节也显示,具名公开证据仍然很窄,因此渠道集中和信号集中,比在广泛、多元客户基础中更关键。人员风险同样重要。公司近期扩充了领导层,这有帮助,但也说明业务一边迈向公开市场准备,一边仍在整合商业化、安全领导力和生态管理。公开记录没有披露板凳深度、组织设计或客户归属;任何关键领导、伙伴或任务级客户出现滑坡,执行风险都会维持在高位。[CR021, CR022, CR023, CR024, CR025, CR026]

伙伴 / 依赖风险登记表
依赖合作方角色集中度失败情境严重性缓释措施剩余敞口
制造和实体模块放量WNCCM/JDM 与模块生产生产时间或质量滑坡拖延部署多条生态关系和早期试点证据
公共部门服务器使能HPE服务器套装和认证路径认证或优先级延误削弱客户转化联邦需求顺风和生态对齐中高
存量基础改造可信度IntelXeon 兼容性和安全计算对齐中高技术对齐低于预期,或主要停留在营销层面中高独立镜像稿和具名 BlackVe 用例
额外服务器生态入口AMD 与 TD SYNNEXEPYC 就绪和渠道路径中高渠道兴趣未转化为终端客户部署中高多条公开公告和目标市场匹配中高
SPAC 交割和市场准入SVAQ信托现金和上市路径赎回或交割失败会削弱流动性和可信度滚存股权和公开交易流程

每项依赖都具有战略性,因为 EigenQ 的获客路径明确由生态中介承接。

[CR002, CR003, CR004, CR023, CR024, CR025]
人员 / 执行风险登记表
角色或职能依赖或缺口可能性严重性缓释措施尽调路径
高管领导层扩大产品组合的同时,还要承受公开市场审视并放大组织近期补强领导层,并有董事会支持索取组织架构图、决策权和继任计划
商业执行需要把伙伴路径转成付费部署目标市场确有紧迫性,也有伙伴入口索取销售管线阶段、输赢单数据和部署转化
安全与合规运营主张横跨隐私、联邦就绪度和信任硬件公开隐私政策和 CISO 任命有所加分索取控制权责、审计节奏和事件响应计划
跨伙伴项目管理多个硬件、服务器和渠道伙伴抬高协调负担中高中高围绕 PQC 迁移的共同使命要求提供联合路线图治理和 SLA 结构
产品焦点路线图从安全延伸到 AI、传感、通信和计算中高安全仍是最初商业化重心要求按产品支柱和近期优先级披露资本配置

人员风险主要在焦点和协同,不是公开可见的管理真空。

[CR028, CR029, CR030, CR036, CR038]
FR003: 依赖图

EigenQ 的商业化栈依赖少数伙伴;每个伙伴控制进入市场路径中的不同环节。

[CR024, CR025, CR026, CR027, CR035]

7.4 缓释成熟度与否决条件

风险缓释成熟度参差不齐。确实有缓释因素:联邦标准正在厘清市场,合并协议看起来覆盖较全,隐私义务至少已被公开承认,多家平台伙伴也为进入买方环境提供不止一条路径。但最深层风险只被部分缓释,因为很多必要证据仍在私域。公开材料没有把赎回敏感性、积压订单、出货转化、可靠性指标、认证范围或客户续约串起来。因此投资者需要把否决条件绑定到可衡量事件,而不是一般性乐观。交易未能按时交割、伙伴路径没有转化为真实部署、认证或制造出现明显延误、监管或隐私不合规,或任何迹象显示公开主张实质性跑在可部署产品证据前面,都应迅速改变投资判断。因此,尽调负担是主动监测,不是被动期待。[CR031, CR032, CR033, CR034, CR035, CR036]

缓释措施与否决标准表
风险可监测触发项阈值或事件行动含义
交易失败交割时间线看不到在 2026 年 Q4 完成交割的有效路径,或最低现金支持恶化立即重估融资桥和估值
合作伙伴路径转化不足部署证据合作伙伴公告持续出现,但没有新增具名生产级部署在证据出现前,将 GTM 说法视为夸大
制造或认证进度滑坡项目时间服务器套装、模块可用性或认证日期无解释地大幅后移下调对商业化扩张速度的信心
合规失败监管或隐私事件出现重大隐私、出口管制或法律合规问题上调法律和商业风险评级
客户集中证明广度客户故事仍围绕一两个证明场景,没有多元化付费账户保持高剩余风险假设和更严格的估值纪律
产品证明缺口基准和认证证据没有可信的公开或尽调专用证据证明可靠性、认证范围或互操作性不要用溢价倍数给生产成熟度定价

这些否决标准是应当改变投资测算的可监测事件,不是泛泛担忧。

[CR031, CR032, CR037, CR038, CR039, CR040]

7.5 展品

Chapter 08

08估值

8.1 公告价格要求投资者相信什么

公开记录给了投资者一个异常清晰的头部估值,也留下一个异常不完整的运营模型。从 2026 年 6 月合并公告、6 月 23 日业务合并材料,到 7 月 28 日文件更新,EigenQ 一直被表述为约 $3.0B 的备考企业价值,SVAQ 信托现金在赎回和费用前约 $215M。这有助于锚定入场讨论,但回答不了核心估值问题,因为市场仍看不到收入、毛利率、客户数、留存、订单,或经审计的单位经济明细。支撑这个数字的最近依据是叙事,不是算术:联邦 PQC 迁移压力真实存在,HPE/AMD/WNC/TD SYNNEX 提供了可想象的规模化路径,公开量子可比公司也显示,只要政府需求和供应链可信度可见,投资者会为技术可选性买单。问题在于,拥有公开估值的同行至少在收入、现金或装机系统上部分可读,而 EigenQ 仍是一个尚未交割的 SPAC 标的,有商业化主张,却几乎没有披露运营证据。这个组合意味着,公告估值更适合被当作谈判点和市场信号,而不是公开记录已经证明的公允价值。[CV001, CV002, CV003, CV004, CV005, CV006]

8.2 公开可比公司支撑主题,但不支持无视价格入场

最相关的公开参照分成两组。第一组是 IonQ、D-Wave、Rigetti 等量子计算龙头。它们不是完美的商业模式匹配,但展示了市场会为技术动量、政府信用和早期收入支付什么价格。IonQ 已成为该领域收入龙头;D-Wave 和 Rigetti 规模小得多,但仍受益于战略项目胜利和公开市场可选性。第二组是 Arqit、SEALSQ 等后量子或量子安全公司,更接近 EigenQ 的安全叙事,但产品架构和资本市场历史不同。这些可比公司支持一个判断:量子和 PQC 基础设施在成熟盈利前,就能讲出十亿美元级股权故事。它们不能证明 EigenQ 立刻就应有 ~$3B 标记。相反,它们说明市场奖励证据密度:披露收入、可见政府项目、技术里程碑,或可复制的商业楔子。EigenQ 政策顺风强、伙伴包装也强,但相对同行,证据缺口仍大于估值缺口。[CV011, CV012, CV013, CV014, CV015, CV016]

投资主线 / 反向论点表
论点支撑证据重要性什么会改变判断
PQC 迁移顺风因素真实存在NIST 已敲定核心标准,CISA 正推动各产品类别采用 PQC为迁移支出托起监管需求底如果采购指引放慢或企业推迟迁移预算,紧迫性会减弱
合作伙伴栈可以加速渠道触达HPE、WNC、AMD 和 TD SYNNEX 提供集成、制造和渠道路径比单打独斗的创业公司打法更快触达企业和公共部门如果合作伙伴路径停留在营销说法、没有订单流,渠道价值就被高估
以安全定位的量子故事可能比只做计算的同业更早变现Arqit 和 SEALSQ 表明,公开市场会在硬件可选性之外认可更近端的安全叙事让 EigenQ 比纯长期计算故事更贴近当前网络安全预算如果买家把 EigenQ 视为小众硬件层而非平台,估值溢价会收窄
反向论点:收入不透明过于严重约 $3B 估值没有公开收入、ARR、毛利率或留存指标相配无法把价格与运营产出做归一化比较经审计的 S-4 披露可能大幅缓解这一担忧
反向论点:上市同业已经显示商业化慢于叙事上市量子同业上市多年、技术也有进展,但仍未盈利意味着投资者应大幅折价看待前瞻性主张重复部署和合作伙伴转化证据会缓和这一风险

核心争议不是赛道是否相关,而是当前证据密度是否配得上要价估值。

[CV005, CV006, CV015, CV016, CV019, CV020]
可比估值表
可比公司类别公开估值或收入信号与 EigenQ 的相关性局限
IonQ上市量子硬件龙头2025 年收入 $130M;一致预期指向 2026 年约 $270M说明只要收入清晰、技术推进明确,市场愿意给溢价估值收入披露比 EigenQ 更成熟,计算敞口也更广
D-Wave上市量子硬件 / 系统公司2025 年收入 $25M;一致预期指向 2026 年约 $44M说明即便收入不高,只要系统和项目可见,上市量子叙事也能延续退火加门模型策略与 EigenQ 安全基础设施并非直接匹配
Rigetti上市超导硬件公司2025 年收入 $7M;一致预期指向 2026 年约 $24M有助于判断政府牵引的商业化为何短期收入仍小计算优先的商业模式不同于 EigenQ
Arqit上市抗量子加密软件公司FY2025 初步收入约 $0.53M;截至 9 月 30 日现金 $36.9M在安全叙事和商业化挑战上更接近 EigenQ软件授权模式和更早的炒作周期会扭曲直接比较
SEALSQ上市后量子硬件安全公司公开信息强调监管驱动的 PQC 硬件需求和商业协议以硬件为根的量子安全基础设施中最接近的上市参照公开来源提供的财务披露不如大型同业标准化

可比信号说明主题需求存在,但本身不能验证 EigenQ 公布的价格。

[CV011, CV012, CV013, CV014, CV015, CV016]
FV002: 估值敏感性

承销判断对收入披露和现金确定性最敏感,其次是伙伴转化和客户验证。

[CV018, CV024, CV025, CV031, CV032]

8.3 情景分析指向被拉伸的基准定价和不对称尽调风险

由于 EigenQ 尚未公开披露收入或毛利率数据,情景分析必须把假设摊开。牛市情境下,投资者假设 CNSA 2.0 和 NIST 驱动的迁移紧迫性,会把伙伴公告转化为可衡量的 OEM 和政府部署,赎回保持可控,公司借助公开资本成为更大范围量子升级周期中的安全层受益者。在这种情境下,公告交易价格可以被辩护为:在经营杠杆可见之前,为一个品类平台付费。基准情境更保守:信托现金因赎回缩水,PQC 需求落地慢于宣传材料暗示,客户需要漫长认证周期,生态公告转化为收入的时间被推迟。熊市情境下,EigenQ 上市时,市场已经看到公开量子同行比预期更久处于盈利前状态,因此变得更挑剔,迫使隐含倍数降低、融资摊薄,或两者同时出现。共同主线是,执行和披露质量比主题机会更重要。没有经审计收入、管线转化数据或伙伴经济性,虚假精确带来的下行大于提前参与叙事带来的上行。[CV023, CV024, CV025, CV026, CV027, CV028]

乐观 / 基准 / 悲观情景表
情景核心假设隐含估值逻辑概率信号关键风险
乐观PQC 迁移预算加速;合作伙伴路径转化为具名部署;赎回保持可控;S-4 显示可信的早期收入公布的约 $3.0B EV 可以解释为在完全规模化前为品类龙头付费需要多项正面披露和交割后的执行证明即使政策顺风强,商业转化仍可能滞后
基准需求真实,但认证周期长;信托现金被赎回削减;收入披露偏温和,不是突破性质量在运营证据跟上前,投资测算区间应低于标示交易价值最符合当前公开证据规模可见前,投资者可能为时点支付过高价格
悲观上市撞上更弱情绪;客户采用仍窄;商业化慢于预期,随后需要融资或稀释估值通过交易价格或未来融资大幅下修至标示值以下如果披露仍薄、可比公司估值下修,该情景可能成立对前沿硬件 / 安全公司而言,叙事受损的影响可能比一次里程碑落空更久
未上市 / 延迟情形SEC 流程、赎回或交割条件拖延并购流动性事件后移,价值仍停留在名义层面低到中等,但并非零;SPAC 交割依赖路径私有期资金跑道压力拉长,会削弱议价能力

这些情景是投资测算框架,不是目标价格。

[CV023, CV024, CV025, CV026, CV027, CV028]
投资主线破裂与否决触发项表
触发项阈值为什么会打破投资主线行动含义
收入不透明延续到生效阶段S-4 / 委托书材料没有披露经审计收入或毛利率市场仍要在缺少运营锚的情况下给数十亿美元价值定价披露改善前保持观望
赎回压力大幅压缩现金信托或交割现金显著低于标示预期削弱资助硬件认证、渠道扩张和获客的能力重新测算下行和稀释风险
具名客户证据没有扩展除现有稀疏证明点外,没有新增具名部署说明合作伙伴公告没有转化为需求将故事视为比估值暗示更早期
合作伙伴路径停滞HPE / AMD / WNC / TD SYNNEX 渠道仍是没有收入支撑的叙事渠道优势是乐观情景的核心支柱下调确信度,等待订单证据
上市可比公司估值重定价下行量子 / PQC 同业估值压缩,而 EigenQ 没有相应证据增量抵消降低对投机性溢价倍数的容忍度提高要求回报门槛,或避免进入

每个触发项都能从文件、披露或后续合作伙伴 / 客户证据中观察到。

[CV003, CV006, CV024, CV028, CV031, CV036]
FV003: 估值 / 回报区间

在经营披露改善前,纪律化承销区间应把这笔交易的公布价值放在偏乐观端。

[CV001, CV023, CV026, CV027, CV028]

8.4 建议、否决条件,以及升级观点所需的尽调

现有证据支持「继续研究」建议,信心中等,风险高,估值立场偏拉伸。这不是否定量子安全基础设施需求,而是在定价层面判断:在支付一个与披露更充分同行相当的公告公开市场估值前,投资者手里到底有多少已验证商业证据。正面逻辑真实存在:EigenQ 站在政府密码迁移、硬件根信任、主权基础设施担忧,以及可能压缩市场进入时间的伙伴栈交叉点上,前提是真实客户采用能跟上。但负面逻辑同样真实:公司要求投资者在没有公开收入证据的情况下承保数十亿美元价值,而公开量子公司已经证明,即使上市后,商业化也可能耗时且极其吃资本。如果 S-4 披露可信的收入、现金、毛利率和转化指标,或具名客户胜利从孤立证据点扩展出去,观点会迅速改善。在那之前,正确姿态是纪律化可选性,而不是高确信仓位。[CV033, CV034, CV035, CV036, CV037, CV038]

建议摘要表
决策项当前判断证据基础什么会上调判断什么会下调判断
建议继续研究估值已经明示,但收入、利润率和客户密度未公开S-4 披露经审计收入、客户集中度和合作伙伴转化指标生效流程后仍缺少收入或销售管线细节
信心交易主要条款清楚,但商业指标不清楚多个一手级来源披露运营 KPI关键主张仍依赖叙事,而非经审计运营数据
风险评级SPAC 执行、赎回、稀释和商业化风险仍然重大赎回托底、现金桥和客户多元化变得可见高赎回或交割延迟减少可用于扩张的资本
估值立场偏高现有公开证据不足以让人照单全收约 $3B 的标示估值运营指标证明其相对上市同业可享有溢价定位上市可比公司估值压缩,或 EigenQ 披露的商业化速度低于暗含预期

本表总结投资决策,不估算交易价格。

[CV001, CV003, CV023, CV033, CV034, CV035]
最终尽调问题表
主题缺失证据重要性负责人或尽调路径
经审计收入桥TTM 收入、订单额、如适用 ARR,以及硬件 / 软件 / 服务收入组合必须用来把约 $3B 估值与实际产出对齐审阅最终 S-4 财务报表和管理层预测桥
现金和稀释资金来源与用途、PIPE 或旁侧融资、认股权证压力和赎回敏感性标示信托现金不等于可用增长资本从备案文件和投资者材料索取股权结构表和交易模型细节
合作伙伴经济性按路径拆分的毛利率、OEM / 分销商抽成、保修负担和认证成本如果经济性弱,合作伙伴牵引的规模化会毁掉价值通过 NDA 或董事会材料索取商业条款
客户转化具名销售管线、部署数量、合同规模、续约信号和集中度验证生态公告是否转化为可重复需求索取客户分群和漏斗报告
技术护城河持久性独立验证以硬件为根的差异化和实施摩擦用来判断 EigenQ 是否能相对纯软件 PQC 同业获得溢价委托技术尽调,对照替代架构评估

若要从继续研究上调到跟踪或买入,至少前四行需要显著更强的证据。

[CV006, CV018, CV023, CV032, CV037, CV038]
FV001: 推荐逻辑

推荐结论从强品类顺风和高质量伙伴出发,穿过薄弱商业披露和高执行风险,落到继续研究。

[CV005, CV006, CV023, CV033, CV034, CV035]
FV004: 投资 KPI

评分卡显示主题需求很强,但公开来源中的经济性和验证质量仍有限,因此可投资性只在中等水平。

[CV005, CV006, CV015, CV018, CV033, CV034]

8.5 展品

免责声明

本 report-meta 产物仅反映截至 2026-07-30 保留在各章 YAML 中的公开证据。EigenQ 仍是尚未交割的 SPAC 标的,公开经营披露存在重大缺口,因此推荐和估值判断高度依赖后续 S-4 财务报表、股权结构细节、客户证据,以及保留公开来源尚未提供的交割现金结果。

证据索引

结论
编号陈述可信度来源
CO001 EigenQ is a Texas-headquartered quantum technology company commercializing hardware and software for post-quantum security and related quantum infrastructure. SO001, SO003, SO005
CO002 EigenQ and Silicon Valley Acquisition Corp. announced a definitive business combination agreement on 2026-06-17. SO001, SO002, SO009
CO003 The announced transaction values EigenQ at approximately $3.0 billion pro forma enterprise value. SO001, SO002, SO009
CO004 The business-combination agreement summary uses a $2.93 billion equity consideration formula divided by a $10.00 share reference in its exchange-ratio mechanics. SO002
CO005 Approximately $215 million was held in SVAQ’s trust account before shareholder redemptions and transaction expenses at announcement. SO001, SO009
CO006 The merger announcement targets a fourth-quarter 2026 close subject to customary approvals and the registration statement becoming effective. SO001, SO002, SO009
CO007 Upon closing, the combined company is expected to trade on Nasdaq under the ticker symbol EIGQ. SO001, SO002, SO003
CO008 EigenQ publicly describes its broader technology scope as spanning quantum security, AI, communications, sensing, and computing. SO001, SO003
CO009 EigenQ says its initial commercialization focus is quantum-resilient security and trusted infrastructure rather than only long-horizon quantum computing. SO001, SO004
CO010 EigenQ markets its platform as OEM-ready, no-redesign-required infrastructure that can be deployed in under 90 days. SO004
CO011 EigenQ’s public stack includes QMA quantum entropy, qTPM device identity, qTEE trusted execution, and the PQC+ cryptographic layer. SO004, SO008
CO012 The EigenQ QMA PCIe x4 QRNG acceleration board is presented as a server and data-center module with up to 12.8 Gbps accelerated quantum-randomness throughput and NIST-validated entropy features. SO008
CO013 The EigenQ QMA M.2 module is presented as an edge and embedded QRNG product with up to 1.24 Gbps accelerated randomness throughput. SO008
CO014 EigenQ explicitly targets government, defense, enterprise, and critical-infrastructure deployments in its technology messaging. SO006, SO025
CO015 EigenQ frames its customer mission as helping both public and private sectors prepare for a future shaped by quantum computing and AI. SO003, SO007
CO016 Dr. José R. Rosas-Bustos is publicly listed as EigenQ’s CEO. SO003, SO005
CO017 Dr. Jesse Van Griensven Thé is publicly presented as EigenQ’s chairman and a founder-level strategic leader. SO003, SO005
CO018 Mark Pecen was appointed vice chairman on 2026-07-28 after previously serving as an EigenQ board member and strategic adviser. SO003, SO016
CO019 Alexander Truskovsky was promoted to a newly established Chief Information Security Officer role on 2026-07-28. SO003, SO016
CO020 EigenQ named Rika Nakazawa chief growth officer on 2026-06-10 to lead global growth strategy and strategic partnerships. SO015, SO007
CO021 William Berghoff is publicly disclosed as EigenQ’s interim or acting chief financial officer. SO005
CO022 EigenQ’s public leadership materials also name a chief product executive and commercial leaders, indicating functional build-out beyond core research leadership. SO005
CO023 Pecen’s public biography centers on ETSI quantum-safe and telecommunications standards work, adding standards-ecosystem credibility to EigenQ’s leadership bench. SO003, SO016
CO024 EigenQ consistently cites HPE, AMD, WNC, and TD SYNNEX as strategic alliances or channel partners in public commercialization materials. SO001, SO007, SO014
CO025 The WNC collaboration positions WNC for contract manufacturing and HPE-related server ecosystem enablement of EigenQ quantum-safe hardware. SO011, SO012
CO026 The TD SYNNEX collaboration is meant to help public-sector, defense, critical-infrastructure, and enterprise customers assess quantum-readiness for AMD EPYC server environments. SO007, SO013, SO014
CO027 The Intel announcement extends EigenQ’s story from new platforms into retrofitting already-deployed Intel Xeon infrastructure for post-quantum readiness. SO007, SO025, SO026
CO028 CISA maintains a product-categories resource for technologies using post-quantum cryptography standards, showing that U.S. cyber agencies now treat PQC migration as a practical procurement category. SO017
CO029 NIST’s PQC standards page identifies FIPS 203, FIPS 204, and FIPS 205 as approved standards, reinforcing the standards backdrop behind EigenQ’s timing narrative. SO019, SO022
CO030 NSA’s CNSA 2.0 resources provide national-security migration guidance that aligns with EigenQ’s emphasis on long-lived high-assurance infrastructure. SO020, SO021
CO031 Reviewed public materials do not disclose current revenue, ARR, customer count, or headcount for EigenQ. SO001, SO007, SO024
CO032 EigenQ should still be treated as private-undisclosed from a disclosure-profile perspective because core operating metrics are not public even though a SPAC transaction has been announced. SO001, SO007, SO024
CO033 Merger-period materials say transaction capital is intended to support commercialization, manufacturing scale-up, strategic partnerships, and global expansion. SO001, SO009
CO034 The business-combination agreement permits termination if the transaction has not been consummated by 2027-02-14, subject to specified exceptions. SO002
CO035 Closing conditions include registration-statement effectiveness, approvals of SVAQ and EigenQ security holders, and conditional listing approval for the combined company. SO002, SO001
CO036 The June 2026 filing warns that redemptions, customer adoption, pricing pressure, supply-chain risk, and OEM integration timing could cause actual results to differ materially from projections. SO002, SO001
CO037 EigenQ’s investor messaging explicitly links its opportunity to a global infrastructure transition driven by standards finalization and regulatory timelines. SO007, SO004
CO038 EigenQ’s website disclaimer says examples, figures, diagrams, and projections on the site may not reflect actual events, data, or performance. SO004, SO006
CO039 The July 28, 2026 filing describes EigenQ as headquartered in Texas, USA, while some collaboration releases list Columbia, Maryland as the release dateline, creating a top-level-versus-operational-location distinction rather than a direct contradiction. SO003, SO014
CO040 SVAQ is a publicly traded blank-check company listed on Nasdaq under the symbols SVAQ, SVAQU, and SVAQW. SO002, SO024
CO041 EigenQ’s public positioning is hardware-anchored trust infrastructure rather than a software-only PQC overlay. SO004, SO006
CO042 The WNC announcement said pilot quantities of the PQU Gen2 card were already shipping to select integrators and described a path toward early-2026 HPE-qualified bundles. SO011
CO043 The Intel announcement claims EigenQ can augment existing Xeon-based environments without requiring a full hardware replacement cycle. SO025
CO044 Nakazawa’s appointment broadened EigenQ’s public narrative into sovereign AI, global growth, and strategic ecosystem development. SO015
CO045 EigenQ says it works alongside a global ecosystem of OEMs, technology partners, and industry leaders. SO003, SO004
CO046 The SPAC website markets SVAQ as a technology-focused blank-check platform, reinforcing the public-listing channel but adding little operating evidence about EigenQ itself. SO023
CO047 Because trust-account cash is pre-redemption, actual transaction proceeds available to EigenQ can be materially lower than the headline $215 million figure. SO001, SO002
CO048 Reviewed public sources do not provide a supportable reconstruction of EigenQ’s private financing history before the SPAC announcement. SO001, SO007, SO024
CM001 The commercially relevant market around EigenQ is post-quantum cryptography migration for digital infrastructure rather than the entire quantum-technology economy. SM018, SM019, SM021
CM002 Most reviewed market sources define the PQC market as some combination of software, hardware, and services that implement or support quantum-resistant cryptography. SM008, SM009, SM011
CM003 CISA now organizes PQC-capable technologies into acquisition categories, indicating that federal buyers treat PQC as a procurement problem rather than only a research topic. SM001, SM015
CM004 NCCoE frames PQC adoption as an interoperability and migration exercise designed to ease replacement of quantum-vulnerable public-key infrastructure. SM004, SM007
CM005 Axis Intelligence estimates the PQC market at roughly $2.2 billion to $2.8 billion in 2026 after placing 2025 around $1.3 billion to $1.6 billion. SM008
CM006 The Business Research Company places the PQC market at $0.78 billion in 2026 and $2.23 billion by 2030. SM009
CM007 360ResearchReports places the PQC market at about $1.106 billion in 2026 and more than $18 billion by 2035. SM010
CM008 Business Research Insights places the PQC market at about $0.68 billion in 2026 and $1.47 billion by 2035. SM011
CM009 The wide spread across published 2026 market estimates shows that the PQC category still lacks a settled commercial denominator. SM008, SM009, SM010, SM011
CM010 Estimate divergence is partly explained by whether publishers include hardware modules, services, and broader quantum-secure networking adjacencies. SM008, SM009, SM011
CM011 For diligence purposes, a range-based sizing view is more defensible than choosing one headline TAM from the reviewed market reports. SM008, SM009, SM010, SM011
CM012 North America appears as the leading current region across multiple reviewed PQC market summaries. SM008, SM009, SM011
CM013 Government and defense, BFSI, healthcare, and IT or telecom recur across reviewed sources as primary verticals for PQC adoption. SM009, SM011
CM014 EigenQ’s own public positioning aligns most closely with government, defense, critical infrastructure, and enterprise compute buyers rather than consumer or SMB segments. SM018, SM019, SM020, SM021
CM015 In many PQC programs the user, buyer, and payer are different parties, often splitting between security engineers, platform teams, and executive or program-office budget owners. SM001, SM006, SM007, SM009
CM016 Adoption usually follows a staged path of crypto inventory, standards selection, hybrid pilot, procurement qualification, and production rollout rather than an immediate swap. SM004, SM007, SM012
CM017 The strongest near-term market driver is standards and policy momentum from NIST finalization, White House action, and federal procurement guidance. SM001, SM003, SM005, SM017
CM018 Harvest-now-decrypt-later risk pulls forward demand because buyers with long-lived secrets cannot wait for large-scale quantum computers to arrive before migrating. SM011, SM012
CM019 Installed-base retrofit potential is a relevant buying wedge because many regulated organizations need migration paths that preserve existing infrastructure. SM019, SM022, SM023, SM024
CM020 High implementation cost and infrastructure complexity are major restraints on PQC adoption. SM007, SM011, SM012
CM021 Skills shortages and crypto-agility gaps make services and partner ecosystems important to actual deployment. SM008, SM011
CM022 Because the market denominator is unstable, headline TAM alone is a weak justification for EigenQ’s announced valuation. SM008, SM009, SM010, SM011
CM023 Standards evolution is still incomplete because NIST migration work continues and additional schemes beyond FIPS 203-205 remain in progress. SM004, SM017
CM024 Multiple sources imply that non-regulated enterprise adoption will lag federal or high-assurance demand because complexity, cost, and competing priorities slow migration. SM006, SM008, SM012
CM025 Cloudflare describes the transition as effectively two migrations and warns that certificate adoption still trails key-agreement migration, illustrating real operational friction. SM012
CM026 GSA’s 2026 PQC summit and CISA buyer guidance both indicate that U.S. federal procurement attention has moved beyond abstract standards awareness. SM001, SM016
CM027 The White House order and Federal News Network coverage suggest that federal migration planning is moving on a deadline-driven basis rather than as an optional long-term research agenda. SM005, SM006
CM028 CISA guidance instructs agencies to plan acquisitions around PQC-capable product categories in areas where standards are mature enough to procure against. SM001, SM015
CM029 Post-Quantum’s 2026 policy guides highlight dual-track civilian and national-security timing, reinforcing the idea that regulated buyers will not move uniformly. SM013, SM014
CM030 EigenQ’s usable market should exclude broad quantum computing, sensing, and AI budgets unless they directly fund security migration infrastructure. SM018, SM019, SM021
CM031 Public evidence is insufficient to isolate a supportable EigenQ-specific SOM because the company has not disclosed pricing, pipeline, conversion rates, or buyer concentration. SM020, SM021, SM022
CM032 The Business Research Company explicitly includes solutions and services as the two main PQC categories in its market framing. SM009
CM033 The Business Research Company identifies network security and application security as core use cases within PQC spending. SM009
CM034 Business Research Insights highlights government standardization and mandates as the biggest market-expanding factor in its narrative framing. SM011
CM035 360ResearchReports attributes 27% of application share to civilian government and 11% to military in its modeled segmentation. SM010
CM036 Axis argues that broad-market forecasts projecting nearly 48% CAGR usually include managed migration services and hardware security modules, not only algorithms and libraries. SM008
CP001 The PQC competitive landscape in 2026 includes pure-play startups, incumbent infrastructure vendors, and large systems integrators rather than a single homogeneous peer group. SP016, SP017, SP019
CP002 SandboxAQ, QuSecure, and ISARA are publicly positioned more around cryptographic inventory, posture, or remediation than around OEM hardware roots of trust. SP002, SP008, SP011
CP003 PQShield, SEALSQ, and Crypto4A are cited as hardware-oriented or silicon-oriented PQC competitors in independent industry coverage. SP016, SP017
CP004 Independent landscape coverage also identifies Thales, AWS, IBM, Entrust, Cisco, and systems integrators as material competitive alternatives in PQC adoption. SP016, SP019, SP021
CP005 SandboxAQ positions AQtive Guard around universal cryptographic inventory, risk context, and migration planning tied to federal and enterprise compliance pressure. SP002, SP003
CP006 PQShield publicly markets both software libraries and hardware accelerators for embedded or chip-level post-quantum deployments. SP004, SP005
CP007 QuSecure positions QuProtect as a production-ready platform for discovery, remediation, and reporting across cryptographic estates. SP007, SP008
CP008 ISARA positions itself around cryptographic inventory, posture management, certificate discovery, and hybrid migration support. SP010, SP011
CP009 SEALSQ positions itself as a secure-semiconductor and PKI platform spanning secure elements, provisioning, root of trust, and post-quantum security. SP012, SP014
CP010 evolutionQ emphasizes cryptographic resilience, roadmap services, and hybrid migration rather than a narrowly defined hardware product story. SP015, SP016
CP011 Independent coverage describes SandboxAQ as funded at more than $1.4 billion, making it visibly better funded than EigenQ’s publicly disclosed standalone operating metrics. SP016, SP017
CP012 SEALSQ’s public-company materials provide operational disclosure that private competitors, including EigenQ, generally do not provide on their websites. SP013, SP012
CP013 ISARA’s federal distribution via Carahsoft is cited in independent coverage as an advantage for public-sector procurement access. SP016
CP014 EigenQ’s clearest differentiation versus inventory-first vendors is its hardware-rooted trust positioning tied to entropy, identity, trusted execution, and OEM integration. SP022, SP023, SP024
CP015 EigenQ appears weaker than discovery-first platforms where the buyer prioritizes enterprise-wide cryptographic inventory and remediation before selecting trust hardware. SP002, SP008, SP011, SP022
CP016 Channel and partner leverage matter because multiple rivals emphasize distributors, federal resellers, or semiconductor design-ins rather than direct greenfield sales alone. SP003, SP009, SP016, SP025
CP017 Discovery and posture platforms can become sticky because they map and monitor certificates, keys, and cryptographic assets across large estates. SP002, SP008, SP011
CP018 Embedded or hardware-rooted solutions can become sticky once they are qualified into chips, boards, firmware, or server-platform bundles. SP005, SP012, SP022, SP024
CP019 PQShield markets high-performance hardware accelerators and embedded libraries that reduce EigenQ’s uniqueness on “hardware plus PQC” alone. SP004, SP005
CP020 SEALSQ’s secure microcontrollers, root-of-trust stack, and PKI services create another hardware-rooted alternative to EigenQ for device and infrastructure trust use cases. SP012, SP014
CP021 QuSecure and SandboxAQ both present simpler software-first migration narratives than EigenQ’s broader hardware-rooted platform story. SP002, SP007, SP008, SP022
CP022 No reviewed competitor website provides clean list pricing for enterprise PQC platforms or hardware, leaving packaging more visible than realized pricing. SP001, SP004, SP007, SP010, SP012
CP023 QuSecure packages its offer as recon, remediation, and reporting modules rather than publicly posting simple per-seat or per-asset pricing. SP007, SP008
CP024 ISARA packages its offer as inventory, crypto-agility, posture management, SDKs, and services rather than publishing list prices. SP010, SP011
CP025 EigenQ’s publicly visible commercial packaging is still channel- and OEM-oriented rather than exposed as transparent public pricing. SP022, SP023, SP024, SP025
CP026 SEALSQ’s packaging spans chips, trust services, PKI, and provisioning, implying volume- and design-win-based economics rather than easily comparable software pricing. SP012, SP013
CP027 One moat risk for EigenQ is that hardware-rooted trust is claimed by multiple rivals, including PQShield, SEALSQ, and Crypto4A-style vendors. SP016, SP017, SP012
CP028 Another moat risk is that migration-control vendors can become the system of record before infrastructure buyers choose a hardware module vendor. SP002, SP008, SP011, SP022
CP029 Independent coverage describes large cloud, certificate, HSM, and networking vendors as already embedding PQC into broader platforms, increasing bundled-competition risk. SP016, SP021
CP030 Systems integrators and consultancies are emerging as important PQC coordinators for complex multi-vendor migrations. SP016, SP017
CP031 As NIST standards mature, some layers of PQC are likely to commoditize and shift value toward distribution, integration, and lifecycle control. SP006, SP017, SP021
CP032 If customers remain in inventory and roadmap phases longer than expected, EigenQ could lose early budget capture to discovery-first vendors. SP008, SP011, SP021, SP022
CP033 The most relevant competitive axes for EigenQ are hardware intensity and migration-control influence, not simply whether a vendor claims to be “quantum-safe.” SP016, SP017, SP022
CP034 EigenQ’s public positioning clusters closer to hardware-heavy vendors than to pure inventory-control platforms. SP022, SP024, SP025, SP017
CP035 The competitor field divides structurally between control-plane vendors and embedded or physical trust vendors. SP004, SP008, SP011, SP012, SP015
CP036 Distribution and workflow ownership are at least as important as raw algorithm support in competitive durability for PQC vendors. SP003, SP016, SP021, SP025
CP037 EigenQ is best positioned when post-quantum migration is treated as a trusted-infrastructure design choice rather than a software-policy problem alone. SP022, SP024, SP025
CP038 Bundled incumbents and integrators are the deepest long-term displacement risk because they can turn PQC into a feature within products customers already buy. SP016, SP019, SP021
CI001 The announced business combination values EigenQ at a pro forma enterprise value of approximately $3 billion. SI001, SI014, SI016, SI017
CI002 The transaction is supported by approximately $215 million held in SVAQ’s trust account before shareholder redemptions and transaction expenses. SI001, SI014, SI016, SI017
CI003 Public transaction materials say capital from the deal is expected to support commercialization, manufacturing scale-up, strategic partnerships, and global expansion. SI001, SI007, SI016, SI017
CI004 EigenQ markets hardware-rooted trust infrastructure, qTPM, entropy, and post-quantum security capabilities as concrete product components. SI004, SI005, SI006
CI005 Public product materials imply EigenQ can monetize both hardware and software components rather than only a single software subscription. SI004, SI005, SI006, SI008, SI011
CI006 The WNC collaboration describes contract-manufacturing and joint-design-and-manufacturing services for EigenQ’s Post-Quantum Unit hardware and Quantum Encryption Module software stack. SI008
CI007 The TD SYNNEX and AMD collaboration frames EigenQ’s offer around post-quantum readiness for AMD EPYC CPU-based server environments. SI010, SI011
CI008 No reviewed official product or partner source disclosed list pricing for EigenQ products, bundles, or deployment programs. SI004, SI005, SI006, SI008, SI010, SI011
CI009 Because pricing is undisclosed and partner mediated, the realized economics of EigenQ deployments likely depend on contract-specific discounting and services mix. SI008, SI010, SI011
CI010 EigenQ’s initial commercialization efforts are focused on government, defense, and critical infrastructure markets. SI001, SI007, SI016, SI017
CI011 Company materials also describe later expansion targets including enterprise infrastructure, AI platforms, financial services, telecommunications, healthcare, industrial systems, and international markets. SI001, SI016, SI017
CI012 Public evidence suggests EigenQ’s revenue recognition could mix hardware shipments, software components, and deployment or integration services rather than clean recurring ARR. SI004, SI005, SI006, SI008, SI010, SI011
CI013 No reviewed public source disclosed EigenQ’s current revenue, ARR, customer count, gross margin, backlog, or burn. SI001, SI002, SI003, SI018, SI019, SI020, SI021, SI022, SI023, SI024
CI014 EigenQ’s sales motion appears partner led through HPE, AMD, WNC, and TD SYNNEX rather than broad public direct pricing. SI001, SI008, SI009, SI010, SI011
CI015 A partner-led model can accelerate enterprise access but also implies that OEMs, distributors, or manufacturers may capture part of the gross economics. SI008, SI010, SI011, SI014
CI016 Hardware-rooted deployment implies bill-of-materials, qualification, and deployment-support costs that software-only PQC vendors may not bear. SI004, SI005, SI006, SI008
CI017 The WNC collaboration says pilot quantities of the PQU Gen2 card were shipping to select integrators and that volume production through WNC would begin in Q4 2025 with HPE-qualified bundles expected early 2026. SI008
CI018 Official merger materials portray the SPAC transaction as the financial bridge for EigenQ’s next phase of commercialization and manufacturing expansion. SI001, SI007, SI016, SI017
CI019 The combined company is expected to trade on Nasdaq as EIGQ if the business combination closes. SI001, SI007, SI016, SI017
CI020 Existing EigenQ shareholders intend to roll substantially all of their equity and no material EigenQ shareholders are expected to sell shares or receive cash consideration as part of the transaction. SI001, SI016, SI017
CI021 The proposed business combination is expected to close in the fourth quarter of 2026 subject to shareholder approval and the Form S-4 being declared effective by the SEC. SI001, SI007, SI016, SI017
CI022 Reviewed filings warn that future results depend on shareholder redemptions, purchase-price adjustments, and management assumptions about expenses and profitability. SI001, SI002, SI015, SI016, SI017, SI022
CI023 Reviewed filings explicitly cite pricing pressure and erosion as risks to EigenQ’s future financial performance. SI001, SI002, SI016, SI017
CI024 Reviewed filings also identify supply chain risks as a potential threat to EigenQ’s financial and operating outcomes. SI001, SI002, SI016, SI017
CI025 Costs related to the proposed business combination are themselves named as a transaction risk in the reviewed filings. SI001, SI002, SI016, SI017
CI026 MarketBeat and Last10K indicate that SVAQ filed a 10-K on March 31 2026 and a 10-Q on February 5 2026, confirming the shell company’s public reporting cadence. SI018, SI019, SI020
CI027 July 28 2026 SEC filing indexes show that additional transaction materials were filed after the merger announcement. SI023, SI024
CI028 No reviewed public source disclosed a PIPE amount, debt facility, or other incremental financing commitment beyond trust cash and rolled equity. SI001, SI002, SI003, SI014, SI015, SI016, SI017, SI023, SI024
CI029 If shareholder redemptions materially reduce trust cash and no large backstop exists, EigenQ’s usable proceeds could fall well below the headline capital framing. SI002, SI015, SI022
CI030 Public evidence supports commercialization readiness and partner access more strongly than it supports currently recognized recurring revenue. SI001, SI004, SI008, SI010, SI011, SI013
CI031 Unit economics remain unverified because no public source breaks out BOM, partner margin, support burden, or software attach rates. SI004, SI006, SI008, SI010, SI011, SI013
CI032 Government, defense, and critical-infrastructure focus likely lengthen sales cycles even when regulatory urgency is high. SI001, SI010, SI011, SI012
CI033 CISA procurement guidance shows that federal buyers are being directed toward PQC-capable hardware and software categories, supporting strategic demand but not guaranteeing EigenQ order timing. SI012, SI013
CI034 SVAQ’s CEO publicly described EigenQ as having a capital-efficient operating model and compelling unit economics. SI016, SI017
CI035 Because EigenQ’s public roadmap spans security, AI, communications, sensing, and computing, proceeds may be spread across multiple initiatives rather than a single narrow security SKU. SI001, SI003, SI004, SI017
CI036 Private diligence still needs current cash, burn, backlog, recognized revenue, gross margin, and partner-term schedules before EigenQ’s margin path or capital adequacy can be underwritten confidently. SI013, SI018, SI023, SI024
CE001 EigenQ publicly positions itself as building hardware-rooted trust for servers, gateways, edge systems, and long-life devices. SE001, SE002, SE004
CE002 Public EigenQ materials highlight secure hardware-rooted device identity with qTPM. SE001, SE004
CE003 Public EigenQ materials highlight quantum-grade entropy as a foundational trust input. SE001, SE002, SE003
CE004 EigenQ’s public product story combines hardware trust components with post-quantum cryptographic software rather than offering only software migration tools. SE001, SE003, SE004, SE012
CE005 The WNC collaboration frames EigenQ’s stack as something that can be delivered as deployable hardware modules rather than only as abstract cryptographic IP. SE008
CE006 The WNC collaboration says WNC will provide contract-manufacturing and joint-design-and-manufacturing services for EigenQ’s PQU hardware and QEM software stack. SE008
CE007 WNC and EigenQ publicly named PCIe, M.2, and 1U secure-server modules as deployment form factors. SE008
CE008 EigenQ’s Intel release positions the product as a retrofit path for existing in-field Xeon-based infrastructure. SE009, SE010, SE011
CE009 EigenQ’s AMD and TD SYNNEX materials position the product as a readiness and migration path for AMD EPYC server environments, including already-deployed systems where technically appropriate. SE012, SE013, SE014
CE010 The AMD collaboration describes customer jobs including readiness assessment, deployment-model identification, and phased infrastructure modernization. SE012, SE013, SE014
CE011 Public materials frame EigenQ’s customer jobs around encrypted communications, identity, key generation, lifecycle management, attestation, and workload protection. SE009, SE012, SE013
CE012 The Intel materials say EigenQ combines quantum entropy technology, PQC+ cryptographic libraries, and qTPM capabilities in its platform. SE009, SE010, SE011
CE013 The Intel materials connect EigenQ’s platform to encrypted communications, identity, key generation, attestation, and modernization of high-assurance systems. SE009, SE010, SE011
CE014 The AMD materials say EigenQ’s platform combines post-quantum cryptographic software, cryptographic-agility tooling, quantum entropy hardware, and integration capabilities. SE012, SE013, SE014
CE015 EigenQ’s public architecture is designed around existing server environments rather than only new greenfield systems. SE008, SE009, SE012, SE015
CE016 EigenQ’s product narrative treats post-quantum migration as an operational deployment problem, not just an algorithm-selection problem. SE009, SE010, SE012, SE017
CE017 Public evidence shows integration pathways with Intel, AMD, HPE, and WNC rather than a purely standalone product motion. SE008, SE009, SE012, SE015
CE018 TD SYNNEX is presented as the channel and public-sector pathway for AMD EPYC-related EigenQ deployments where approved and applicable. SE012, SE013, SE014
CE019 Public manufacturing scale-up depends on WNC’s facilities and execution rather than on evidence of in-house EigenQ production at scale. SE008
CE020 The WNC release claims pilot quantities of the PQU Gen2 card were shipping to select integrators. SE008
CE021 The WNC release claims volume production through WNC would begin in Q4 2025. SE008
CE022 The WNC release claims HPE-qualified server bundles would be available in early 2026. SE008
CE023 The Intel Xeon and AMD EPYC releases are stronger evidence of productization than generic “future quantum” positioning because they identify named infrastructure environments. SE009, SE010, SE012, SE013, SE014
CE024 Public roadmap language extends beyond security into AI, communications, sensing, and computing. SE005, SE006, SE007
CE025 Leadership and investor materials imply the roadmap is broad, which can expand optionality but widen execution surface. SE005, SE007, SE024, SE025
CE026 Public evidence is stronger on partner and infrastructure integration than on versioned software release history. SE005, SE008, SE009, SE012
CE027 The reviewed public record did not provide module-level throughput benchmarks, reliability metrics, or interoperability test packs for EigenQ products. SE001, SE003, SE004, SE009, SE012, SE015
CE028 EigenQ’s core differentiation claim is that long-lived or high-assurance systems need trusted entropy, hardware-rooted identity, and secure execution scaffolding underneath PQC migration. SE001, SE002, SE009, SE012
CE029 Publicly reviewed evidence suggests EigenQ is more differentiated as a deployable infrastructure package than as a unique algorithm inventor. SE003, SE016, SE017, SE020
CE030 NIST’s PQC standards page identifies FIPS 203, FIPS 204, and FIPS 205 as the approved standards relevant to post-quantum deployment. SE016, SE026, SE027
CE031 NIST IR 8547 frames PQC migration as a transition of information-technology products, services, and infrastructure rather than only a cryptography research exercise. SE017, SE020
CE032 CISA’s guidance says organizations should procure only PQC-capable products in listed categories where such products are widely available. SE020, SE021
CE033 CISA’s list explicitly covers hardware and software product categories, supporting EigenQ’s combined infrastructure positioning but also raising the bar for practical product readiness. SE020, SE021
CE034 EigenQ’s product delivery is exposed to standards bodies, OEM ecosystems, manufacturing partners, and procurement channels simultaneously. SE008, SE017, SE020
CE035 EigenQ repeatedly references FIPS 203 and FIPS 204 alignment in public product messaging. SE001, SE008, SE016
CE036 NIST describes FIPS 203 as ML-KEM and FIPS 204 and FIPS 205 as digital-signature standards relevant to post-quantum deployment. SE016, SE026, SE027
CE037 EigenQ’s public releases frame deployments as relevant to CNSA 2.0-style requirements and high-assurance federal or defense environments. SE009, SE012, SE018, SE019
CE038 NSA and CISA materials show that PQC migration requirements are pressuring both algorithms and the surrounding infrastructure categories. SE018, SE019, SE020
CE039 The reviewed public record did not provide a clean product-by-product certification ledger for EigenQ’s modules. SE001, SE004, SE008, SE015
CE040 The reviewed public record did not provide a formal reliability dashboard, update-policy documentation, or public security incident history for EigenQ products. SE001, SE003, SE004, SE005
CE041 Standards alignment is much more visible in public materials than module-level proof artifacts. SE016, SE020, SE026, SE027
CE042 The absence of benchmark and certification detail is the strongest adverse evidence against assuming production-grade maturity from marketing alone. SE001, SE004, SE015, SE020
CU001 EigenQ publicly targets government, defense, critical infrastructure, and enterprise environments for initial commercialization. SU001, SU004, SU022
CU002 Public materials link demand most directly to long-lived infrastructure under PQC migration pressure. SU001, SU016, SU019, SU020, SU021
CU003 The likely buyer centers are infrastructure security teams, federal or defense procurement programs, and OEM or channel-led platform owners. SU001, SU003, SU012, SU019
CU004 Intel, AMD, HPE, WNC, and TD SYNNEX are part of the practical route through which EigenQ reaches customers. SU005, SU006, SU012, SU018
CU005 The user jobs emphasized publicly include secure communications, identity, attestation, key management, and workload protection. SU006, SU012, SU013
CU006 Public materials do not provide a geography or revenue-band segmentation of customers. SU001, SU002, SU003, SU024
CU007 The customer story implies relatively few high-value accounts rather than a broad self-serve customer base. SU003, SU012, SU019
CU008 Government and defense relevance is bound up with compliance mandates such as CNSA 2.0 and federal PQC procurement guidance. SU019, SU020, SU021
CU009 Public customer acquisition depends on partner and procurement pathways rather than a publicly visible direct-sales motion. SU004, SU012, SU018
CU010 BlackVe is the clearest named public customer-proof signal in the reviewed record. SU006, SU007, SU008, SU009
CU011 BlackVe publicly said it planned to use EigenQ’s Intel-compatible PQC technologies for secure video systems and national-security space applications. SU006, SU007, SU008, SU009
CU012 WNC and EigenQ publicly said pilot quantities of the PQU Gen2 card were shipping to select integrators. SU005
CU013 WNC and EigenQ publicly said HPE-qualified server bundles were expected early 2026. SU005
CU014 The AMD and TD SYNNEX pathway is described as readiness and deployment support for AMD EPYC server environments rather than as a named buyer deployment list. SU012, SU013, SU014
CU015 The Intel-related releases frame EigenQ’s offer as relevant to federal, defense, space, critical infrastructure, and enterprise environments. SU006, SU007, SU008
CU016 The reviewed public record contains route-to-market and qualification evidence beyond BlackVe, but not a broad list of named end users. SU005, SU012, SU014, SU018
CU017 Logos, partner pathways, and qualified bundle language do not prove production deployment on their own. SU005, SU012, SU018, SU025
CU018 Public adoption evidence is stronger for mission-oriented pilots and partner routes than for mass-market usage metrics. SU006, SU012, SU016
CU019 The named customer proof table is sparse enough that customer-quality assessment still depends heavily on inference. SU006, SU008, SU012, SU014
CU020 No reviewed source disclosed NRR, GRR, churn, renewal rates, or customer cohort data for EigenQ. SU001, SU003, SU024, SU025
CU021 Hardware-rooted infrastructure that is qualified into deployed systems could be sticky over time, but public evidence does not measure that stickiness. SU005, SU006, SU012, SU018
CU022 Public releases include “approved and applicable” and technical-appropriateness qualifiers that caution against assuming immediate broad repeat deployments. SU012, SU013, SU025
CU023 The public record does not disclose contract length, renewal terms, or satisfaction metrics for named or unnamed EigenQ users. SU001, SU003, SU024
CU024 Retention today is a thesis based on infrastructure embedding and compliance pressure rather than a published KPI. SU019, SU020, SU021, SU025
CU025 BlackVe and other mission-oriented use cases may imply stronger account durability than generic enterprise pilots, but the evidence is still early. SU006, SU008, SU011
CU026 No reviewed source provided independent customer satisfaction surveys, review scores, or broad testimonial evidence for EigenQ. SU001, SU003, SU024
CU027 Illustrative retention heuristics can be built for diligence, but they cannot substitute for account-level data. SU020, SU024, SU025
CU028 Expansion upside depends heavily on whether partner pathways convert into repeat deployments across more systems or programs. SU005, SU012, SU018
CU029 BlackVe demonstrates a credible adjacent expansion path from secure communications into other space or intelligence workloads. SU006, SU008, SU009
CU030 Channel concentration is meaningful because TD SYNNEX, HPE, Intel, AMD, and WNC help control access to the buyer environments EigenQ targets. SU004, SU005, SU012, SU018
CU031 Federal and defense procurement friction can slow expansion even where the need for PQC migration is explicit. SU019, SU020, SU021, SU025
CU032 The public record does not show a diversified roster of named paying customers across segments. SU006, SU008, SU012, SU014, SU024
CU033 Because named proof is narrow, any single marquee account or partner program carries outsized signaling importance. SU006, SU011, SU025
CU034 Public sources do not reconcile which target segment is paying today versus which segments are still pre-revenue pathways. SU003, SU015, SU016, SU025
CU035 Investors need named-account, deployment, renewal, and revenue-split data before they can underwrite customer quality confidently. SU020, SU024, SU025
CU036 EigenQ’s customer story is credible but concentrated: strategically aligned with urgent segments yet still thin on diversified production proof. SU004, SU006, SU011, SU025
CR001 EigenQ’s financing bridge remains dependent on the proposed SPAC closing and the usable value of trust cash after redemptions and expenses. SR002, SR003, SR004, SR005
CR002 The business combination agreement and public summaries explicitly contemplate termination, breach, and closing-condition failure scenarios. SR001, SR002, SR025
CR003 Redemptions and the possible need for additional financing are specifically highlighted as transaction risks in public coverage of the agreement. SR002, SR004, SR027
CR004 Nasdaq listing continuity matters because the public-market route is part of EigenQ’s credibility and financing story. SR003, SR024, SR026
CR005 Financing, manufacturing, customer-proof, and partner-concentration risks together form the highest-severity risk cluster for EigenQ. SR001, SR014, SR021, SR030
CR006 Public evidence supports a hardware-and-partner-heavy operating model rather than a low-dependency software-only model. SR014, SR015, SR016, SR017
CR007 Customer-proof risk remains elevated because public evidence of end-user breadth is much thinner than the ambition of the commercialization narrative. SR018, SR021, SR028, SR030
CR008 Compliance commitments lower legal uncertainty directionally but do not eliminate residual risk where public operating proof is absent. SR001, SR006, SR009
CR009 Residual risk is still high enough that the strategic narrative should be discounted until scale and closing are better evidenced. SR001, SR003, SR021, SR030
CR010 Risk transmission in EigenQ runs from operating and compliance proof into customer confidence, financing confidence, and valuation confidence. SR002, SR021, SR027, SR030
CR011 The merger documents explicitly cover litigation, compliance with laws, labor, environmental matters, intellectual property, and privacy and security. SR001, SR002, SR004
CR012 Government approvals and regulatory compliance are material conditions embedded in the transaction process. SR001, SR002, SR003
CR013 EigenQ’s privacy policy says the company is committed to PIPEDA, GDPR, Israeli privacy law, and other applicable international privacy standards. SR006, SR007, SR008
CR014 The merger agreement defines sanctions and export-control laws with reference to EAR, OFAC, State Department, EU, and UK-related frameworks. SR001, SR004
CR015 Export-control and sanctions compliance matters strategically because EigenQ targets federal, defense, and international high-assurance environments. SR001, SR012, SR013
CR016 No material public litigation against EigenQ surfaced in the reviewed sources, but litigation remains an expressly disclosed risk topic. SR001, SR002, SR004
CR017 Federal PQC migration guidance raises the bar for commercial readiness because buyers are being steered toward PQC-capable hardware and software categories. SR010, SR011, SR012, SR013
CR018 Public sources describe pilot shipments, HPE-qualified bundles, and server retrofit pathways, which imply real qualification and manufacturing execution risk. SR014, SR015, SR017, SR020
CR019 The reviewed public record did not provide field reliability metrics, throughput benchmarks, or interoperability test packs for EigenQ modules. SR014, SR017, SR021
CR020 Public trust claims are stronger than public operational-proof artifacts for security, updates, and reliability. SR006, SR009, SR021
CR021 A hardware-rooted infrastructure model carries supply, quality, and logistics risks that a software-only model would bear less heavily. SR014, SR015, SR016
CR022 No reviewed public source provided a security incident history, independent control audit pack, or public reliability dashboard for EigenQ. SR006, SR017, SR018
CR023 WNC is a high-concentration dependency because it is publicly tied to EigenQ’s manufacturing and scale-up path. SR014, SR015
CR024 HPE is a high-concentration dependency because server qualification and public-sector enablement are part of EigenQ’s route to market. SR014, SR015
CR025 Intel is a strategically important dependency because the installed-base retrofit story is tied to Xeon compatibility and mission-system use cases. SR017, SR018, SR023
CR026 AMD and TD SYNNEX are strategically important dependencies because the EPYC pathway and public-sector channel story rely on them for reach and execution. SR016, SR020
CR027 SVAQ is a high-severity dependency because it is both the capital-market bridge and the source of trust-account proceeds. SR002, SR003, SR024
CR028 Public customer-proof concentration amplifies partner dependence because a narrow proof set gives each pathway outsized signaling importance. SR017, SR018, SR021, SR030
CR029 Recent leadership expansion helps but also signals a company scaling governance and commercialization capacity under public-market pressure. SR003, SR028, SR029
CR030 The broad roadmap across security, AI, communications, sensing, and computing increases product-focus risk relative to a narrower company. SR005, SR028, SR029
CR031 Mitigation maturity is strongest where standards clarity and ecosystem alignment already exist. SR010, SR011, SR012, SR013
CR032 Mitigation maturity is weakest where financing certainty still depends on redemption outcomes and final closing mechanics. SR002, SR003, SR004, SR027
CR033 The most important legal diligence items are privacy controls, export classifications, IP ownership, and the exact closing-condition package in the S-4. SR001, SR006, SR007, SR008
CR034 The most important operational diligence items are reliability metrics, qualification status, certification scope, and shipment-to-deployment conversion. SR014, SR015, SR017, SR021
CR035 The most important partner diligence items are commercial terms, roadmap commitments, exclusivity or non-exclusivity, and contingency plans across the ecosystem. SR014, SR015, SR016, SR017
CR036 The most important people and execution diligence items are org depth, ownership of partner programs, and capital allocation discipline across product pillars. SR005, SR028, SR029
CR037 Failure to close on time, failure to convert partner pathways into named deployments, or failure to produce benchmark and certification evidence would be thesis-break triggers. SR002, SR014, SR017, SR021
CR038 Compliance failures, large partner slips, or clear diffusion of focus across too many product pillars should all increase the residual risk rating. SR001, SR006, SR016, SR030
CR039 Even with real mitigants, EigenQ still has high residual exposure to concentration and under-disclosure risk. SR017, SR021, SR026, SR030
CR040 The correct investment posture is to monitor specific milestones rather than assume that regulatory urgency alone will de-risk commercialization. SR010, SR021, SR027, SR030
CV001 The announced business combination values EigenQ at approximately $3.0 billion of pro forma enterprise value. SV001, SV002, SV024
CV002 The business-combination materials describe an equity consideration formula of about $2.93 billion underlying the transaction mechanics. SV002, SV004
CV003 Public announcement materials cite approximately $215 million in SVAQ trust cash before shareholder redemptions and transaction expenses. SV001, SV002, SV024
CV004 The transaction had not yet closed as of 2026-07-30 and remained subject to SEC effectiveness, shareholder approvals, and other closing conditions. SV003, SV004, SV005, SV006
CV005 EigenQ is positioned publicly as quantum-safe infrastructure built around hardware-rooted trust and post-quantum cryptography rather than only long-horizon fault-tolerant compute. SV007, SV008, SV001
CV006 The public record reviewed for this chapter does not disclose EigenQ revenue, ARR, gross margin, or retention metrics sufficient for a conventional multiple analysis. SV001, SV002, SV003
CV007 NIST continues to maintain the federal post-quantum cryptography project as a live standards transition effort. SV012
CV008 CISA has published 2026 guidance directing product categories and technologies toward use of PQC standards. SV013
CV009 EigenQ has public partner pathways through WNC, HPE, AMD, and TD SYNNEX that could shorten manufacturing or distribution cycles if demand converts. SV009, SV010, SV011
CV010 Because the trust figure is pre-redemption, usable closing cash can be materially lower than the headline number. SV002, SV017
CV011 S&P Global Market Intelligence reports that IonQ generated about $130 million of revenue in 2025. SV014, SV016
CV012 S&P Global Market Intelligence cites consensus expectations for IonQ revenue of about $270 million in 2026. SV014
CV013 S&P Global Market Intelligence reports D-Wave revenue of about $25 million in 2025 and a 2026 forecast near $44 million. SV014
CV014 S&P Global Market Intelligence reports Rigetti revenue of about $7 million in 2025 and a 2026 forecast near $24 million. SV014
CV015 Public quantum comparables demonstrate that public markets will fund frontier quantum narratives even while near-term revenue remains relatively small. SV014, SV015, SV016, SV018
CV016 IonQ, D-Wave, and Rigetti are relevant comparables for EigenQ because they show how government credibility and technical milestones interact with early public-market valuation. SV014, SV016, SV019, SV020, SV021
CV017 Arqit is a relevant security-side comparable because it sells quantum-safe encryption services rather than quantum-compute hardware. SV018, SV023, SV029
CV018 SEALSQ is a meaningful hardware-rooted PQC analogue because its public messaging centers on post-quantum secure elements and regulation-driven demand. SV018, SV022, SV030
CV019 The Quantum Insider describes post-quantum cryptography companies as nearer-term business opportunities than pure compute platforms because they address current cybersecurity budgets. SV018
CV020 The same comparable set does not prove that EigenQ deserves a full ~$3 billion valuation today because better-known peers disclose more operating detail. SV014, SV016, SV018
CV021 The Quantum Insider cites IonQ at roughly $22 billion of market capitalization as of October 2025, illustrating how large valuation dispersion already exists inside public quantum names. SV018
CV022 The Quantum Insider also notes that most quantum public companies remain pre-profit even when valuations reach billions. SV018
CV023 A bull-case defense of EigenQ at the announced valuation requires partner pathways to convert into named deployments and revenue faster than the current public proof set shows. SV009, SV010, SV011, SV019
CV024 The base case is that valuation should be discounted below the headline transaction value until audited operating disclosures appear. SV006, SV014, SV017
CV025 A realistic base case also assumes partner announcements still need long qualification and procurement cycles before showing up in revenue. SV010, SV011, SV013
CV026 A bear case includes the possibility that quantum and PQC multiples compress while EigenQ is still early in commercialization. SV017, SV018
CV027 If the company lists without meaningful new disclosures, future financing could occur at terms less attractive than the headline transaction framing implies. SV002, SV017
CV028 The current public record does not support a precise target return because both entry price discovery and normalized operating metrics are missing. SV001, SV002, SV006
CV029 Quantum-computing SPAC history shows that public-market access can arrive before durable commercialization is proven. SV016, SV017
CV030 Entangled Future highlights PIPE size, closing cash, and long-term forecast assumptions as core diligence items for SPAC-era quantum listings. SV017
CV031 Post-listing monitoring should focus immediately on closing cash, named customer additions, and whether partner pathways generate observable orders. SV003, SV009, SV011, SV017
CV032 The most important diligence asks remain revenue bridge, cap-table and redemption sensitivity, partner economics, and customer conversion evidence. SV002, SV017, SV018
CV033 The evidence in this chapter supports a research-more recommendation rather than buy or track. SV006, SV017, SV018, SV024
CV034 Confidence should remain medium because transaction terms are concrete but commercial metrics are still largely undisclosed. SV001, SV002, SV006
CV035 Risk rating should remain high because underwriting still depends heavily on successful SPAC close, partner conversion, and future disclosure quality. SV002, SV004, SV017
CV036 Valuation stance should remain stretched because the announced headline value outruns the current public evidence base. SV001, SV006, SV014, SV018
CV037 An upgrade toward track would require audited revenue disclosure plus more than one clearly named customer or deployment reference. SV003, SV006, SV017
CV038 A true buy case would require evidence that EigenQ can monetize PQC migration faster than public quantum peers monetized compute demand. SV014, SV018, SV019, SV020
CV039 Exit readiness is improving because July 2026 filing cadence shows active transaction progress, but public evidence is still insufficient for conviction sizing. SV003, SV005, SV006
CV040 The main unresolved blocker to conviction is not absence of thematic demand but absence of auditable commercialization evidence. SV006, SV012, SV013, SV018
来源
编号出版方标题引文
SO001 Securities and Exchange Commission Exhibit 99.1 press release dated June 17, 2026
SO002 Securities and Exchange Commission Form 8-K / 425 for Silicon Valley Acquisition Corp. business combination agreement summary
SO003 Securities and Exchange Commission Form 425 filed by EigenQ on leadership appointments
SO004 EigenQ EigenQ homepage
SO005 EigenQ EigenQ About page
SO006 EigenQ EigenQ Technology page
SO007 EigenQ EigenQ Investors page
SO008 EigenQ EigenQ Products page
SO009 PR Newswire EigenQ and Silicon Valley Acquisition Corp. announce definitive business combination agreement
SO010 The Quantum Insider EigenQ And Silicon Valley Acquisition Corp. announce definitive business combination agreement
SO011 PR Newswire EigenQ and WNC announce strategic collaboration to deliver FIPS-certified quantum-safe hardware at HPE Discover 2025
SO012 Hewlett Packard Enterprise Upgrade to next-generation security for the quantum era
SO013 Yahoo Finance EigenQ announces collaboration with TD SYNNEX to Advance Post-Quantum Security Readiness for AMD EPYC CPU-based Server Environments
SO014 PR Newswire EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SO015 PR Newswire EigenQ names Rika Nakazawa Chief Growth Officer to accelerate global expansion
SO016 PR Newswire EigenQ appoints Mark Pecen as vice chairman and promotes Alexander Truskovsky to chief information security officer
SO017 Cybersecurity and Infrastructure Security Agency Product Categories for Technologies That Use Post-Quantum Cryptography Standards
SO018 NIST CSRC Post-Quantum Cryptography project page
SO019 NIST CSRC Post-Quantum Cryptography FIPS approved standards page
SO020 National Security Agency CNSA 2.0 cybersecurity page
SO021 National Security Agency CNSA 2.0 algorithms page
SO022 National Quantum Initiative / Quantum.gov NIST Releases Post-Quantum Encryption Standards
SO023 Silicon Valley Acquisition Corp. SVAQ company website
SO024 Nasdaq SVAQ quote page
SO025 PR Newswire EigenQ announces post-quantum security readiness capabilities for existing in-field Intel Xeon-based systems
SO026 The Quantum Insider EigenQ announces post-quantum security integration for Intel Xeon systems
SM001 Cybersecurity and Infrastructure Security Agency Product Categories for Technologies That Use Post-Quantum Cryptography Standards
SM002 NIST CSRC Post-Quantum Cryptography project page
SM003 NIST CSRC Post-Quantum Cryptography FIPS approved standards page
SM004 NIST NIST IR 8547 initial public draft, Transition to Post-Quantum Cryptography Standards
SM005 The White House Securing the Nation Against Advanced Cryptographic Attacks
SM006 Federal News Network White House PQC order lights a fire under post-quantum transition
SM007 NCCoE Migration to Post-Quantum Cryptography
SM008 Axis Intelligence Research Post-Quantum Cryptography Statistics 2026: Market Size, Adoption & Migration Data
SM009 The Business Research Company Post-Quantum Cryptography (PQC) Market Size and Share Report 2026
SM010 360 Research Reports Post-Quantum Cryptography Market Size, Trend & Share
SM011 Business Research Insights Post-Quantum Cryptography Market Share & Trends [2026-2035]
SM012 Cloudflare The state of the post-quantum Internet
SM013 Post-Quantum The Complete US Post-Quantum Cryptography (PQC) Regulatory Framework in 2026
SM014 Post-Quantum CNSA 2.0: Complete Guide to NSA's PQC Requirements
SM015 The Quantum Insider CISA Issues Federal Buying Guidance for Post-Quantum Cryptography
SM016 General Services Administration 2026 Post-Quantum Cryptography Summit - In Person 9/16/26
SM017 NIST Transition to Post-Quantum Cryptography Standards | Draft NIST IR 8547 is Available for Comment
SM018 EigenQ EigenQ homepage
SM019 EigenQ EigenQ Technology page
SM020 EigenQ EigenQ Investors page
SM021 Securities and Exchange Commission EigenQ and Silicon Valley Acquisition Corp. announcement exhibit
SM022 Yahoo Finance EigenQ announces collaboration with TD SYNNEX to advance PQC readiness for AMD EPYC environments
SM023 PR Newswire EigenQ announces post-quantum security readiness capabilities for existing in-field Intel Xeon-based systems
SM024 PR Newswire EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SM025 PR Newswire EigenQ and WNC announce strategic collaboration to deliver FIPS-certified quantum-safe hardware at HPE Discover 2025
SP001 SandboxAQ Transforming the World with AI and Advanced Computing
SP002 AQtive Guard Secure your Cryptographic Assets
SP003 SandboxAQ SandboxAQ Supports White House Executive Order as Post-Quantum Cryptography Moves to Implementation for National Security
SP004 PQShield Post-quantum Cryptography Experts | Quantum-safe and Quantum-resistant Solutions
SP005 PQShield Quantum-safe and Quantum-resistant Software, Hardware and Upgrades
SP006 PQShield Regulatory Landscape
SP007 QuSecure Post-Quantum Cryptography (PQC) | Crypto-Agility
SP008 QuSecure QuProtect | Quantum-Resilient Cybersecurity. Delivered Simply.
SP009 QuSecure QuSecure 2026 Technology Pioneer by World Economic Forum
SP010 ISARA Quantum Readiness & Cryptographic Management
SP011 ISARA Cryptographic Inventory & Posture Management | ISARA Advance
SP012 SEALSQ SEALSQ | Sovereign Semiconductor Security for the AI & Quantum Era
SP013 SEALSQ SEALSQ Reports Q1 2026 Key Financial and Operational Metrics and Provides Business Update
SP014 SEALSQ SEALSQ Welcomes the Official Launch of the Year of Quantum Security 2026 and Confirms Active U.S. Deployments of Post-Quantum Semiconductor Technology
SP015 evolutionQ evolutionQ | Cybersecurity Solutions for Cryptographic Resilience
SP016 The Quantum Insider Top Quantum Cryptographic Companies in 2026
SP017 Quantum Zeitgeist Post-Quantum Cryptography Companies: Top 2026 NIST Standards Guide
SP018 StartUs Insights Top 5 Post-Quantum Cryptography Companies in 2026
SP019 The Business Research Company Post-Quantum Cryptography (PQC) Market Size and Share Report 2026
SP020 Cybersecurity and Infrastructure Security Agency Product Categories for Technologies That Use Post-Quantum Cryptography Standards
SP021 Cloudflare The state of the post-quantum Internet
SP022 EigenQ EigenQ Technology page
SP023 EigenQ EigenQ Investors page
SP024 PR Newswire EigenQ announces post-quantum security readiness capabilities for existing in-field Intel Xeon-based systems
SP025 PR Newswire EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SI001 SEC Exhibit 99.1: EigenQ and Silicon Valley Acquisition Corp. announce definitive business combination agreement
SI002 SEC Form 8-K / 425 filing for Silicon Valley Acquisition Corp business combination materials
SI003 SEC Form 425: EigenQ leadership announcement and transaction update
SI004 EigenQ EigenQ homepage
SI005 EigenQ EigenQ technology page
SI006 EigenQ EigenQ products page
SI007 PR Newswire EigenQ and Silicon Valley Acquisition Corp. announce definitive business combination agreement
SI008 PR Newswire EigenQ and WNC announce strategic collaboration to deliver FIPS-certified quantum-safe hardware at HPE Discover 2025
SI009 Hewlett Packard Enterprise HPE post-quantum security collaboration document
SI010 Yahoo Finance EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SI011 PR Newswire EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SI012 CISA Product categories and technologies to use post-quantum cryptography standards
SI013 NIST Post-Quantum Cryptography project
SI014 Stock Titan EigenQ, Silicon Valley Acquisition sign $3B merger deal
SI015 Stock Titan SVAQ to take EigenQ public in definitive merger
SI016 TMCnet EigenQ and Silicon Valley Acquisition Corp. announce definitive business combination agreement
SI017 Nasdaq EigenQ and Silicon Valley Acquisition Corp. announce definitive business combination agreement
SI018 MarketBeat Silicon Valley Acquisition latest SEC filings 2026
SI019 Last10K Silicon Valley Acquisition Corp. 10-K annual report overview
SI020 SEC EDGAR entity landing page for Silicon Valley Acquisition Corp.
SI021 SEC EDGAR filing index for 0001213900-26-069434
SI022 SEC EDGAR filing index for 0001213900-26-071185
SI023 SEC EDGAR filing index for 0001213900-26-082379
SI024 SEC EDGAR filing index for 0001213900-26-082376
SI025 Silicon Valley Acquisition Corp. Silicon Valley Acquisition Corp. website
SE001 EigenQ EigenQ homepage
SE002 EigenQ EigenQ about page
SE003 EigenQ EigenQ technology page
SE004 EigenQ EigenQ products page
SE005 EigenQ EigenQ investors page
SE006 SEC Exhibit 99.1 business combination press release
SE007 SEC Form 425 transaction and leadership filing
SE008 PR Newswire EigenQ and WNC announce strategic collaboration to deliver FIPS-certified quantum-safe hardware at HPE Discover 2025
SE009 PR Newswire EigenQ announces post-quantum security readiness capabilities for existing in-field Intel Xeon-based systems
SE010 The Quantum Insider EigenQ announces post-quantum security integration for Intel Xeon systems
SE011 HPCwire EigenQ targets post-quantum upgrades for existing Intel Xeon infrastructure
SE012 PR Newswire EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SE013 TMCnet EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SE014 The Quantum Insider EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SE015 Hewlett Packard Enterprise HPE post-quantum security collaboration document
SE016 NIST Post-Quantum Cryptography FIPS standards page
SE017 NIST NIST IR 8547 draft transition to post-quantum cryptography standards
SE018 NSA Commercial Solutions for Classified Program CNSA 2.0 algorithms page
SE019 NSA CNSA 2.0 overview page
SE020 CISA Product categories and technologies to use post-quantum cryptography standards
SE021 The Quantum Insider CISA issues federal buying guidance for post-quantum cryptography
SE022 GitHub GitHub topic: post-quantum-cryptography
SE023 GitHub PQ Code Package GitHub organization
SE024 PR Newswire EigenQ names Rika Nakazawa chief growth officer to accelerate global expansion
SE025 PR Newswire EigenQ appoints Mark Pecen as vice chairman and promotes Alexander Truskovsky to chief information security officer
SE026 NIST FIPS 203: Module-Lattice-Based Key-Encapsulation Mechanism Standard
SE027 NIST FIPS 204: Module-Lattice-Based Digital Signature Standard
SU001 EigenQ EigenQ homepage
SU002 EigenQ EigenQ about page
SU003 EigenQ EigenQ investors page
SU004 SEC Exhibit 99.1 business combination press release
SU005 PR Newswire EigenQ and WNC announce strategic collaboration to deliver FIPS-certified quantum-safe hardware at HPE Discover 2025
SU006 PR Newswire EigenQ announces post-quantum security readiness capabilities for existing in-field Intel Xeon-based systems
SU007 Morningstar EigenQ announces post-quantum security readiness capabilities for existing in-field Intel Xeon-based systems
SU008 The Quantum Insider EigenQ announces post-quantum security integration for Intel Xeon systems
SU009 TechIntelPro EigenQ enables PQC readiness for Intel Xeon-based systems
SU010 HackerNoon EigenQ and Intel partner to harden deployed Xeon systems against quantum threats
SU011 HyperFRAME Research Is a software layer enough to make Xeon fleets quantum safe?
SU012 PR Newswire EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SU013 TMCnet EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SU014 The Quantum Insider EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SU015 Quantum Computing Report EigenQ to go public via $3 billion SPAC merger with Silicon Valley Acquisition Corp.
SU016 TechTimes Post-Quantum Cryptography Startup EigenQ Eyes $3B Nasdaq Listing via SPAC
SU017 Channel News Asia Quantum tech firm EigenQ to go public in $3 billion SPAC deal
SU018 Hewlett Packard Enterprise HPE post-quantum security collaboration document
SU019 CISA Product categories and technologies to use post-quantum cryptography standards
SU020 NIST NIST IR 8547 draft transition to post-quantum cryptography standards
SU021 NSA CNSA 2.0 overview page
SU022 Nasdaq EigenQ and Silicon Valley Acquisition Corp. announce definitive business combination agreement
SU023 Stock Titan EigenQ, Silicon Valley Acquisition sign $3B merger deal
SU024 MarketBeat Silicon Valley Acquisition latest SEC filings 2026
SU025 SEC Form 8-K / 425 filing for Silicon Valley Acquisition Corp business combination materials
SU026 Supaterminal EigenQ launches post-quantum security platform for Intel Xeon systems, targeting CNSA 2.0 readiness
SR001 SEC Business Combination Agreement exhibit 2.1
SR002 SEC Form 8-K / 425 summary of the business combination agreement
SR003 Greenberg Traurig Greenberg Traurig advising SVAQ in connection with $3B merger with EigenQ
SR004 Minichart Key terms and conditions of the Silicon Valley Acquisition and EigenQ business combination agreement
SR005 SEC EigenQ and SVAQ definitive business combination press release exhibit
SR006 EigenQ EigenQ privacy policy
SR007 GDPR.eu What is GDPR?
SR008 Office of the Privacy Commissioner of Canada PIPEDA overview
SR009 FTC Data Security guidance
SR010 CISA Product categories and technologies to use post-quantum cryptography standards
SR011 NIST NIST IR 8547 draft transition to post-quantum cryptography standards
SR012 NSA CNSA 2.0 overview
SR013 NSA CNSA 2.0 algorithms page
SR014 PR Newswire EigenQ and WNC strategic collaboration at HPE Discover 2025
SR015 Hewlett Packard Enterprise HPE post-quantum security collaboration document
SR016 PR Newswire TD SYNNEX and AMD collaboration for post-quantum readiness
SR017 PR Newswire Intel Xeon post-quantum readiness announcement
SR018 The Quantum Insider EigenQ post-quantum integration for Intel Xeon systems
SR019 Morningstar Intel Xeon readiness PR mirror
SR020 TMCnet AMD EPYC pathway PR mirror
SR021 HyperFRAME Research Is a software layer enough to make Xeon fleets quantum safe?
SR022 HackerNoon EigenQ and Intel partner to harden deployed Xeon systems against quantum threats
SR023 TechIntelPro EigenQ enables PQC readiness for Intel Xeon-based systems
SR024 Nasdaq SVAQ market activity page
SR025 SEC EDGAR filing index for the June 23 2026 filing
SR026 MarketBeat Silicon Valley Acquisition latest SEC filings 2026
SR027 Stock Titan SVAQ to take EigenQ public in definitive merger
SR028 Quantum Computing Report EigenQ to go public via $3 billion SPAC merger
SR029 Channel News Asia Quantum tech firm EigenQ to go public in $3 billion SPAC deal
SR030 TechTimes Post-Quantum Cryptography Startup EigenQ Eyes $3B Nasdaq Listing via SPAC
SR031 FTC Protecting Personal Information: A Guide for Business
SV001 SEC Exhibit 99.1: EigenQ and Silicon Valley Acquisition Corp. announce definitive business combination agreement
SV002 SEC Form 8-K / 425 filing for Silicon Valley Acquisition Corp business combination materials
SV003 SEC Form 425: EigenQ leadership announcement and transaction update
SV004 SEC Business combination agreement exhibit
SV005 SEC EDGAR filing index for 0001213900-26-082376
SV006 SEC EDGAR filing index for 0001213900-26-082379
SV007 EigenQ EigenQ homepage
SV008 EigenQ EigenQ technology page
SV009 PR Newswire EigenQ and WNC announce strategic collaboration to deliver FIPS-certified quantum-safe hardware at HPE Discover 2025
SV010 Hewlett Packard Enterprise HPE post-quantum security collaboration document
SV011 PR Newswire EigenQ announces collaboration with TD SYNNEX to advance post-quantum security readiness for AMD EPYC CPU-based server environments
SV012 NIST Post-Quantum Cryptography project
SV013 CISA Product categories and technologies to use post-quantum cryptography standards
SV014 S&P Global Market Intelligence Quantum computing stocks rise as US stakes USD2B on sector build-out
SV015 LevelFields Top Quantum Computing Stocks to Watch 2026
SV016 Entangled Future Quantum computing stocks guide
SV017 Entangled Future Quantum computing SPAC and IPO guide 2026
SV018 The Quantum Insider Public quantum stocks 2025: from pure plays to tech giants
SV019 IonQ News
SV020 Rigetti Rigetti Newsroom
SV021 D-Wave Newsroom | D-Wave
SV022 SEALSQ Investors news releases
SV023 Arqit Quantum Security Solutions | Arqit
SV024 Nasdaq EigenQ and Silicon Valley Acquisition Corp. announce definitive business combination agreement
SV025 Stock Titan EigenQ, Silicon Valley Acquisition sign $3B merger deal
SV026 Nasdaq IONQ
SV027 Nasdaq QBTS
SV028 Nasdaq RGTI
SV029 Nasdaq ARQQ
SV030 Nasdaq LAES