Startup Diligence
Diligence report Enterprise Tech / AI infrastructure and foundation models Private unicorn / Series A

Zyphra

Zyphra Standard-Depth Startup Diligence Report

Zyphra could be attractive if AMD-optimized long-context inference plus open research converts into enterprise customers and favorable unit economics; the public record does not yet prove that conversion.

Company profile

Zyphra Standard-Depth Startup Diligence Report

Track / diligence-required. Zyphra has strong public technical and strategic-partner signals for an early AI infrastructure/model company, but standard investment diligence should treat financials, customers, unit economics, cap table, legal controls and supplier commitments as unverified until primary documents are reviewed.

Website
www.zyphra.com
Sector
Enterprise Tech / AI infrastructure and foundation models
Geography
United States — Palo Alto / San Francisco, California
Stage
Private unicorn / Series A
Known aliases
Zyphra Technologies, Zyphra Technologies Inc.
Report version
1.0
Timezone
America/Los_Angeles

Executive summary

Strengths

  • CB and IBM support the $1B private-unicorn / Series A valuation signal.
  • Zyphra has visible public technical assets across language, speech and EEG research plus 23 GitHub repositories.
  • IBM, AMD and TensorWave relationships substantiate a serious compute/infrastructure strategy.
  • Zyphra Cloud’s initial commercial wedge is serverless long-context inference on AMD MI355X, while several adjacent capabilities are roadmap items.

Risks

  • Financial statements, revenue quality, burn, gross margin and customer concentration are not public.
  • Public funding totals and valuation details conflict across databases and need cap-table reconciliation.
  • Product execution depends heavily on AMD/IBM/TensorWave infrastructure and unknown commercial terms.
  • Voice cloning, EEG research, unmoderated base-model warnings and agent execution raise safety/legal risks.
  • Open research visibility supports credibility but may weaken moat without proven enterprise conversion.

Gaps

  • Audited financials and revenue/ARR bridge.
  • Customer list, contracts, revenue concentration and retention.
  • Cap table, financing documents and investor rights.
  • Supplier and strategic partnership contracts.
  • Security/privacy/SOC/AUP/DPA and model-safety documentation.
  • Org chart, headcount, employment/IP agreements and turnover.

Recommended next steps

  • Request primary financial, cap-table and financing documents before relying on valuation headlines.
  • Conduct customer/reference diligence and review top contracts, usage cohorts and pipeline.
  • Review IBM/AMD/TensorWave agreements, capacity commitments and gross-margin model.
  • Commission technical benchmark/safety review for inference, agent environments, voice cloning and EEG research.
  • Run counsel-led legal/IP/privacy/security diligence, including litigation dockets and IP/data-rights schedules.

Risk register

high high likelihood

R-001: Financial opacity and revenue quality

No audited financials, revenue by product/customer, gross margin, cash runway, backlog or AR schedules are public.

Diligence request: Obtain full financial statements, ARR bridge, customer schedule, cloud cost/margin model and board-approved forecast.

high high likelihood

R-003: Compute and supplier concentration

IBM Cloud, AMD silicon/ROCm and TensorWave infrastructure are central to the product roadmap and likely cost base.

Diligence request: Review supplier contracts, capacity, minimum commitments, failover plans and utilization/margin data.

high high likelihood

R-004: Customer traction and concentration opacity

No top-customer list, revenue concentration, churn, NRR/GRR, pipeline or named production customer evidence is public.

Diligence request: Conduct customer reference calls and review contracts, usage cohorts, pipeline and churn.

high medium likelihood

R-002: Valuation and funding source inconsistency

CB list, IBM and secondary profiles support a near-$1B valuation, but public funding totals and dates conflict.

Diligence request: Reconcile cap table, financing documents, proceeds, share price, liquidation preferences and side letters.

high medium likelihood

R-005: Model safety, abuse and regulated-use exposure

Public assets include voice cloning, EEG research-use disclaimers and unmoderated model warnings, plus agentic execution risk.

Diligence request: Review red-team reports, safety policies, AUP enforcement, data rights, consent controls and incident history.

high medium likelihood

R-007: Legal/privacy/security packet not public

Public Terms reference separate customer agreement, AUP and DPA, but those documents, SOC/security audits, privacy controls and insurance are not reviewed.

Diligence request: Request SOC 2/security packet, customer terms, DPA, AUP, privacy policy, insurance, litigation and regulatory schedules.

medium high likelihood

R-006: Competitive pressure and uncertain moat

Zyphra competes with larger frontier labs, hyperscalers, inference providers and neoclouds; open assets may be replicable.

Diligence request: Obtain win/loss, independent benchmarks, customer switching analysis and defensibility/IP memo.

medium high likelihood

R-009: Roadmap and commercial maturity risk

Inference is launched, while several cloud/agent/post-training/dedicated-capacity capabilities are roadmap or not backed by public customer metrics.

Diligence request: Review product roadmap, GA criteria, backlog, engineering milestones and customer commitments.

Chapter 01

01Financial Information

The public record supports Zyphra’s unicorn-screening status and a major IBM/AMD infrastructure relationship, but not revenue quality, cash runway, gross margin, cap table, debt-like commitments, or forecast reliability.

I.A Annual and quarterly financial information for the past three years

inconclusive confidence: low

No audited or management income statements, balance sheets, cash-flow statements, backlog, AR aging, or revenue by product/channel/geography were found in public sources.

Evidence gaps

  • Audited financial statements for FY2023-FY2025 and YTD 2026.
  • Revenue by product, channel, geography, customer, cohort, and backlog.
  • Cloud/inference usage, GPU utilization, gross margin and support costs.

Hidden risks

  • Valuation may be disconnected from verified revenue.
  • Hidden minimum cloud/GPU commitments could materially affect runway.

Follow-up questions

  • Provide monthly P&L, balance sheet, cash flow, ARR bridge, deferred revenue, backlog and AR aging.
  • Show inference margin by model, average context length, concurrency and GPU vendor.
Financial-statement and KPI evidence matrix
metricpublic signalevidence qualitymissing primary documentsrisk read
Revenue / ARRNo company disclosure; Latka estimates 2024 ARR $8.8MWeakAudited income statements, ARR bridge, customer invoices, deferred revenueValuation may rely on R&D/strategic scarcity rather than demonstrated revenue.
Gross margin / COGSProduct depends on AMD/IBM/TensorWave compute; no unit economics disclosedMedium for cost-driver, weak for numbersInference margin by model/context, cloud bills, GPU utilization, customer pricingLong-context MoE workloads may pressure margins.
Cash / burnLarge funding/compute partnership implied; no cash balanceWeakBalance sheet, cash runway, capex commitments, cloud prepayCapital intensity likely high.
Backlog / ARNo named backlog/customer revenue tableWeakBacklog, AR aging, signed customer contractsCommercial traction cannot be verified publicly.

I.B Financial Projections

inconclusive confidence: low

No company projections were public. Public growth drivers are the cloud launch, Maia/agent roadmap, open-source funnel, and strategic compute access; cost and financing assumptions are not disclosed.

Evidence gaps

  • Three-year quarterly model by revenue line, gross margin, capex/cloud spend and headcount.
  • Pipeline conversion assumptions, pricing assumptions, and scenario analyses.
  • External financing and runway assumptions.

Hidden risks

  • Forecasts could be highly sensitive to model mix, context length, utilization, hardware availability and pricing pressure.

Follow-up questions

  • What customer cohorts, committed contracts and utilization levels support the 2026-2028 plan?
  • What minimum spend or capacity commitments are embedded in IBM/TensorWave/AMD agreements?
Public valuation and funding signals Chart shows public point estimates rather than primary financing records.

I.C Capital Structure

partially verified confidence: medium

The $1B unicorn headline is supported by CB Insights and IBM, with secondary profiles around $989M-$1B, but shares outstanding, investor rights, option pool, debt and other dilutive instruments are non-public.

Evidence gaps

  • Fully diluted cap table, option pool, SAFE/note conversion, board/investor rights, debt and warrants.
  • Series A/A-1 closing documents and side letters.

Hidden risks

  • Headline valuation may obscure investor preferences, structured terms, or debt-like compute obligations.

Follow-up questions

  • Provide cap table pre/post Series A, securities ledger, financing docs, investor rights, board consents and debt schedule.
Capital structure visibility
capital itempublic evidencenot publicdiligence implication
ValuationCB list $1B; IBM Series A $1B; Forge $989.39M post-moneyTerm sheet, share price, liquidation preferences, valuation capVerify valuation mechanics and investor rights before accepting unicorn headline.
Total fundingForge/EquityZen about $121M-$122M; CB financial profile visible total-raised field $11M; Latka $111.4MCap table, SAFE/note conversions, debt, warrantsContradictory public totals require primary financing schedule.
OwnershipSelect investors in CB list and profilesFounders, employees, investors, option pool, warrantsDilution and control cannot be assessed publicly.
Debt / commitmentsIBM/AMD/TensorWave multi-year infrastructure relationshipsTake-or-pay, prepaid cloud, equipment leases, minimum spend, debt covenantsCompute commitments could be economically debt-like.

I.D Other financial information

partially verified confidence: medium

Financing history is partially triangulated from CB, IBM and secondary-market profiles. Tax, accounting policies, revenue recognition, NOLs and deferred revenue are not public.

Evidence gaps

  • Tax returns and NOL schedule.
  • Revenue-recognition policies for cloud/API and reserved capacity.
  • Signed financing history with percentage ownership and current basis.

Hidden risks

  • Tax/accounting treatment of cloud credits, prepayments, model licensing and services could affect revenue quality.

Follow-up questions

  • Provide revenue recognition memo, tax filings, NOL schedule and financing proceeds/use-of-funds bridge.
Public financing chronology
dateevent or roundamount or valuationinvestors or counterpartiesconfidencenotes
2021 / 2020Company formation windowNot publicFoundersMedium-lowForge/EquityZen say 2021; Tracxn/AI Market Watch say 2020.
2024-10-01Seed / seed-1 rowsForge: ~$11.42M plus small seed-1; post-money not primary verifiedBison Ventures, Future Ventures, Gaia, Metaplanet, others per ForgeMediumSecondary-market profile; reconcile with CB profile total-raised field.
2025-06-06 to 2025-06-09Series A / A-1 / unicorn-list date joinedCB: $1B valuation; Forge: $100M Series A + $10.1M A-1 and $989.39M post-moneyCB list: Bison Ventures, Future Ventures, Intel Capital; IBM says Series A closed at $1B valuationMedium-highPrimary source for amount/cap table still required.
2025-10-01IBM/AMD infrastructure collaboration announcedNo purchase amount disclosed; IBM repeats $1B Series A valuationIBM, AMDHigh for partnership; low for economicsMulti-year cloud/GPU infrastructure, not necessarily equity financing.
Public financing and infrastructure timeline Sequencing of public financing and infrastructure milestones; private transaction terms remain unverified.
Chapter 02

02Products

Zyphra’s public product surface is broad for its stage—open foundation models, speech/EEG research, MAIA agent, Inference, Compute and Agent Environments—but commercial maturity, pricing, production reliability and safety controls need primary validation.

II.A Description of each product

partially verified confidence: medium

Public materials verify Zyphra Research, Zyphra Cloud, serverless Inference and a pipeline of agent/compute/environment capabilities. Public materials do not verify customer adoption, margins, pricing, market share or production SLAs.

Evidence gaps

  • Current SKU/rate card and customer contract templates.
  • Product-level revenue, gross margin, retention and support costs.
  • Independent benchmark results and production incident history.
  • Safety evaluations for voice cloning, agent execution, hosted third-party models and EEG research.

Hidden risks

  • Roadmap breadth may exceed current execution capacity.
  • Open model artifacts create safety and data-rights obligations.
  • Company-authored benchmark claims may not generalize to customer workloads.

Follow-up questions

  • Which Zyphra Cloud capabilities are GA, beta, private preview or roadmap?
  • Provide product usage metrics by SKU, paid customer, workload type and average context length.
  • Provide red-team reports and AUP enforcement statistics for agent, speech and hosted-model features.
Product and research asset matrix
assetcategorydisclosed statustarget user or use caseevidence strengthkey diligence question
Zyphra InferenceCommercial cloud serviceAvailable / launched; serverless inference first componentLong-horizon agentic workloads, large MoE servingStrong company evidenceVerify paying customers, pricing, uptime, margin, and SLAs.
MAIA / AgentAgent productPublicly positioned as general/multiplayer enterprise agent; adoption metrics not publicEnterprise knowledge workers and agentic workflowsMediumSeparate demo capability from production deployment and usage.
Agent EnvironmentsSandbox/runtimeListed by cloud pages; some components described as upcomingIsolated code, browser, terminal, and workflow executionMediumVerify security architecture, tenant isolation, SOC controls.
Compute / dedicated clustersInfrastructureGPU clusters, bare metal, dedicated capacity described; dedicated clusters/bare metal listed as upcoming in blogTraining, RL, simulations, custom AMD kernelsMediumVerify supply commitments and resale/hosting economics.
ZonosOpen-weight TTS modelPublic GitHub model with strong community interestText-to-speech, voice cloning, multilingual audioStrong technical evidenceAssess voice-cloning safety, license obligations, and monetization path.
Zamba / Zamba2 / ZUNAOpen research modelsPublic blogs and repositories disclose architecture and limitationsEfficient language models, EEG foundation modelingStrong technical evidenceIndependently reproduce benchmark, data-rights, safety, and clinical-use claims.
Product monetization and disclosure gaps
dimensionwhat is publicwhat is missingrisk or opportunity
PricingCloud/inference marketing pages and contact-sales flows; no full public rate card foundToken prices, reserved-capacity rates, discounts, committed-use contractsPricing opacity limits margin and adoption assessment.
AvailabilityInference described as launched; future post-training/RL/environments/dedicated capacity describedRegion availability, service limits, beta/GA definitions, uptime historyRoadmap risk remains material.
Safety/complianceTerms reference AUP/DPA/customer agreement; demos should not receive sensitive or regulated dataAUP text, privacy/SOC packet, model cards for every hosted model, abuse-monitoring metricsEnterprise procurement may stall without controls.
DifferentiationAMD/ROCm/custom-kernel/long-context positioning and open research portfolioIndependent TCO benchmarks versus Nvidia/cloud alternativesCould be strong if verified; risky if company-authored benchmarks do not generalize.
Public product architecture Public architecture inferred from Zyphra Cloud and model pages.
Chapter 03

03Customer Information

Public customer diligence is the weakest area: no top-customer list, revenue by customer, churn or concentration table is public. Disclosed relationships are strategic infrastructure partnerships rather than proven paying-customer adoption.

III.A Top customers by application

inconclusive confidence: low

No top-15 customers, product ownership, purchase timing or customer-level revenue were found in public sources. Public segments are developers, enterprises/knowledge workers and frontier AI hyperscalers.

Evidence gaps

  • Top 15 customer list by application for FY2024, FY2025 and YTD 2026.
  • Product ownership, contract term, ACV, usage, renewal and churn for each top account.

Hidden risks

  • Product-market fit could be earlier than the valuation implies.
  • Enterprise references may be concentrated in partners rather than paying customers.

Follow-up questions

  • Provide customer reference calls, top-customer revenue by product, and signed customer contracts.
Named customer and usage evidence
relationship or segmenttypepublic evidencerevenue evidencediligence read
DevelopersTarget segmentCloud pages target developers and agentic workflowsNo revenue disclosedDeveloper traction should be verified through usage cohorts and paid conversion.
Enterprises / knowledge workersTarget segmentMAIA described for enterprise knowledge workers and long-horizon workflowsNo named enterprise logosObtain top-customer list and pipeline stage definitions.
Frontier AI hyperscalersTarget segmentAbout/Cloud pages name hyperscalers as target usersNo contracts disclosedAssess whether Zyphra is supplier, customer, competitor, or partner in each account.
Open-source usersCommunity demand signalGitHub stars/forks on Zonos and other reposNo conversion dataCommunity adoption is useful but not equivalent to ARR.

III.B Strategic relationships

verified confidence: high

IBM Cloud, AMD and TensorWave relationships are well-supported publicly, but relationship economics, exclusivity and revenue/customer impact are not public.

Evidence gaps

  • Signed agreements, economics, co-sell rights, exclusivity and minimum-commitment schedules.
  • Partner-sourced pipeline and customer conversion metrics.

Hidden risks

  • Strategic partnerships can validate technology while masking unfavorable unit economics or exclusivity.

Follow-up questions

  • What revenue, cost, equity or minimum-spend commitments are attached to IBM, AMD and TensorWave?
Strategic relationships
counterpartyrelationship typepublic termsevidence strengthunknowns
IBM CloudTraining infrastructure provider / cloud partnerMulti-year agreement; large AMD MI300X cluster; initial deployment in September 2025 and expansion planned in 2026Strong for existenceGPU count, price, minimums, SLAs, exclusivity, termination rights.
AMDSilicon/platform partnerMI300X training, MI355X inference, AMD networking hardware; quotations in public releasesStrong for existenceEquity participation, product co-marketing economics, roadmap commitments.
TensorWaveInference infrastructure providerMI355X infrastructure provider for Zyphra InferenceStrong for existenceCapacity allocation, cloud spend, resiliency, resale margins.
Open-source ecosystemResearch distribution/communityPublic GitHub repos and open model checkpointsStrong for visibilityLicense compliance, contributor agreements, enterprise conversion.
Disclosed relationship concentration by diligence criticality Qualitative criticality score for public relationships; not revenue contribution.

III.C Revenue by customer

inconclusive confidence: low

No revenue by customer or any customer accounting for 5%+ of revenue is public.

Evidence gaps

  • Revenue concentration schedule and cohort retention.
  • Gross margin and support burden by customer/application.

Hidden risks

  • One or a few strategic relationships could dominate revenue or cost exposure.

Follow-up questions

  • List all customers above 5% of revenue and all no-revenue strategic deployments.

III.D Significant relationships severed within the last two years

inconclusive confidence: low

No severed customer, partner or supplier relationships surfaced in accessible public searches, but there is no public relationship ledger.

Evidence gaps

  • Lost customer/partner list, churned pilots, terminated supplier agreements, legal demand letters.

Hidden risks

  • Failed pilots or supplier disputes may be non-public.

Follow-up questions

  • Provide churn/lost-deal register and terminated relationship schedule since 2024.

III.E Top suppliers

partially verified confidence: medium

AMD, IBM Cloud and TensorWave are highly visible suppliers/partners. Purchase amounts and supplier contracts are not public.

Evidence gaps

  • Supplier spend, capacity, SLAs, failover plans and termination rights.
  • Redundancy and portability plans across hardware/cloud providers.

Hidden risks

  • Supplier concentration, ROCm/software risk and GPU supply constraints could affect margin and availability.

Follow-up questions

  • Provide supplier contracts, capacity reservations, spend history, committed-use obligations and contingency plan.
Top supplier dependency screen
supplier or dependencycriticalityevidencepurchase amount publicrisk note
AMD Instinct MI300X / MI355X silicon and ROCm stackHighTraining and inference positioning are centered on AMD hardware/softwareNoRoadmap, software maturity, and supply constraints could affect execution.
IBM CloudHighLarge multi-year training clusterNoCommitment terms may drive burn or constrain flexibility.
TensorWaveHigh for launched inferenceNamed MI355X infrastructure partnerNoAvailability, utilization, and redundancy should be tested.
Open-source model ecosystems / third-party modelsMediumInference serves external models such as Kimi, DeepSeek, GLMNoLicensing, model availability, and supplier changes can affect service continuity.
Chapter 04

04Competition

Zyphra has a differentiated public narrative—open models plus AMD-optimized long-context inference—but competes against heavily funded model labs, hyperscale clouds, inference specialists and neocloud providers with better-known customer scale.

IV.A Competitive landscape by market segment

partially verified confidence: medium

Zyphra’s basis of competition is technology architecture, open research, AMD optimization, long-context inference and enterprise agents. Public evidence does not prove market share, price leadership or customer preference.

Evidence gaps

  • Market share by segment, price comparison, win/loss reports, independent benchmarks.
  • Customer reference comparison against incumbent inference/model platforms.

Hidden risks

  • Larger competitors can subsidize pricing, bundle distribution or replicate open architectures.
  • Supplier differentiation may narrow if AMD support becomes broadly available.

Follow-up questions

  • Provide competitive win/loss for top 20 opportunities and independent benchmark study versus three named alternatives.
Competitive landscape
segmentrepresentative competitorszyphra positioningpublic strengthpublic weakness
Frontier model labs / agentsOpenAI, Anthropic, Google DeepMind, xAI, Mistral, CohereOpen superintelligence, MAIA agent, multimodal models, open researchOpen-source technical footprint and strategic infrastructureNo disclosed customer/revenue scale versus much larger incumbents.
Inference/cloud model servingTogether, Fireworks, Replicate, Cerebras, Groq, hyperscale cloudsAMD-optimized long-context inference for large MoE/agentic workloadsClear hardware differentiation and partner storyPricing, uptime, independent benchmarks, and customers not public.
AI infrastructure / neocloudLambda, CoreWeave, Crusoe, TensorWave, cloud GPU providersProduct company plus compute layer rather than pure capacity rentalIBM/AMD cluster access and TensorWave relationshipSupplier concentration and unclear resale economics.
Open models / research communitiesMeta Llama ecosystem, Mistral, Hugging Face model publishersOpen models across language, speech, and EEG with architectural experimentationGitHub engagement and disclosed research assetsOpen assets can diffuse moat unless monetization is differentiated.
Basis-of-competition scorecard
basiszyphra public score 1 to 5supporting evidencemain validation needed
Technology architecture4Zamba/Zamba2/Zonos/ZUNA repos and blogs disclose architectures and datasetsIndependent benchmark reproduction, data lineage, safety review.
Cost/performance3AMD/ROCm/custom-kernel and MI355X memory-positioning claimsWorkload-specific TCO versus Nvidia and other inference providers.
Distribution2Website, GitHub, blogs, contact sales; no channel partner revenuePipeline, win/loss, customer references, sales productivity.
Trust/compliance2Terms reference AUP/DPA/customer agreements but public compliance package is absentSOC 2, security architecture, model safety governance, privacy review.
Capital access4$1B unicorn listing and strategic IBM/AMD relationshipCash runway, future financing needs, obligations under compute deals.
Zyphra market map Positioning across model openness and infrastructure specialization.
Chapter 05

05Marketing, Sales, and Distribution

Zyphra’s public GTM engine is technical content, open-source distribution, product pages/contact-sales and strategic partner announcements. There is no public sales productivity, funnel conversion, pipeline or budget evidence.

V.A Strategy and implementation

partially verified confidence: medium

Public positioning emphasizes open/sovereign AI, long-horizon agents, AMD-optimized inference and enterprise/hyperscaler use cases. Implementation metrics are not public.

Evidence gaps

  • GTM plan, ICP, channels, demand-gen budget, pipeline source and conversion metrics.
  • International distribution and regulated-industry plan.

Hidden risks

  • Narrative strength may outrun sales capacity and enterprise compliance readiness.

Follow-up questions

  • What percentage of pipeline comes from open-source, inbound product, partner referrals and outbound sales?
GTM channels and public funnel evidence
channelobservable activitybuyer or userpublic metric or gapdiligence request
Company website / cloud pagesProduct positioning and contact-sales pathsDevelopers, enterprises, hyperscalersNo traffic, signup, activation, or paid conversion dataProvide funnel by source, activation and paid conversion by cohort.
GitHub/open-source23 public repos; Zonos has high stars/forksResearchers and developersStars/forks visible; enterprise conversion unknownShow repo-to-cloud conversion and enterprise leads.
Strategic partner PRIBM/AMD/TensorWave announcementsEnterprise buyers and AI infrastructure buyersPartner economics and co-sell activity not publicProvide signed co-marketing/co-sell terms and sourced pipeline.
Model launch/blog contentInference, Zamba, model pages and research postsAI builders, technical evaluatorsNo MQL/SQL attribution publicProvide attribution from content to opportunities.
Marketing signal and claim verification tracker
public claim or signalsourcecurrent statusverification needed
Inference built for long-horizon agentic workloadsCompany pages/blogsPublicly assertedProduction workload logs, latency/throughput by context length, customer references.
Open superintelligence and sovereign controlHomepage/AboutPositioning verifiedSecurity/privacy controls, deployment options, model customization, regulated-industry proof.
Enterprise superagent MAIAIBM release/company cloud pagesRoadmap/product direction verifiedLive deployments, active users, retention, accuracy and safety metrics.
$1B valuation and Series ACB/IBM/secondary profilesHeadline verified, terms not publicClosing docs, cap table, investor list, option pool and preferences.
Public GTM evidence funnel Proxy funnel based on observable public signals; management should provide real counts.

V.B Major Customers

inconclusive confidence: low

No major customer relationships or customer trend data are public; strategic partner relationships are not necessarily customers.

Evidence gaps

  • Customer relationship status, expansion/contraction, NRR/GRR, referenceability, pipeline growth.

Hidden risks

  • Customer pipeline may consist of trials, free usage or partner demos rather than paid production workloads.

Follow-up questions

  • Provide top-account pipeline with stage, ACV, use case, technical owner, economic buyer and close date.

V.C Principal avenues for generating new business

partially verified confidence: medium

Observable avenues are open-source/community, product-led website/cloud access, partner credibility and technical content.

Evidence gaps

  • Lead-source attribution, activation, usage-to-paid conversion, and sales-cycle data.

Hidden risks

  • Open-source users may not convert into enterprise revenue.

Follow-up questions

  • Show cohort conversion from repo download/star, cloud signup, activated workloads and paid spend.

V.D Sales force productivity model

inconclusive confidence: low

No sales headcount, quotas, compensation, productivity, sales-cycle or hiring plan data were public.

Evidence gaps

  • Sales org chart, quotas, attainment, ramp, compensation and pipeline coverage.
  • Customer success/support staffing for cloud reliability.

Hidden risks

  • Sales capacity may not match enterprise pipeline or valuation expectations.

Follow-up questions

  • Provide sales productivity model by rep, segment, channel and cohort.

V.E Ability to implement marketing plan with current and projected budgets

inconclusive confidence: low

Marketing budget and implementation capacity are not public. Compute commitments may compete with GTM budget for cash.

Evidence gaps

  • Marketing budget, hiring plan, agency/PR contracts, partner MDF/co-sell budget.
  • Runway allocation between R&D/compute and GTM.

Hidden risks

  • Underfunded GTM could delay revenue while compute spend continues.

Follow-up questions

  • Provide budget-to-plan, GTM hiring plan and monthly burn allocation by function.
Chapter 06

06Research and Development

R&D is Zyphra’s strongest public diligence area: models, repos and technical blogs substantiate research activity. The open questions are cost, data rights, safety validation, key-person concentration, and conversion from research to durable commercial products.

VI.A Description of R&D organization

partially verified confidence: medium

Public sources show active model research and named founders/leadership, but full org structure, personnel biographies, IP assignments and retention plan are not public.

Evidence gaps

  • R&D org chart, current key personnel, employment/IP agreements, attrition and hiring plan.
  • Compute budget and model-training cost by project.

Hidden risks

  • Key-person risk and rapid hiring needs may be significant.
  • Open publication may aid recruiting but expose roadmap and reduce proprietary moat.

Follow-up questions

  • Provide R&D org chart, project roadmap, compute budget, model cards and IP assignment schedule.
R&D organization and personnel visibility
person or grouppublic role or signalevidenceconfidencediligence need
Krithik PuthalathCEO and Chairman; founder/CEO in partner releases/profilesIBM release and company/market profilesHigh for CEO/ChairmanBiography, employment agreement, equity, board role, technical involvement.
Tomás FiglioliaCofounder in secondary profilesForge/Tracxn/AI Market WatchMediumCurrent role, reporting line, retention package.
Beren MillidgeCofounder in secondary profilesForge/Tracxn/AI Market WatchMediumCurrent role, publications, IP assignment.
Danny MartinelliCofounder / products and partnerships; low-confidence sources conflict on CEO roleEquityZen/Forge/AI Market Watch/LatkaMedium-lowResolve title, responsibilities, customer relationships.
Research engineering teamPublic model work; Zamba blog claims seven-person team for model trainingZamba blog and GitHubMediumOrg chart, hiring plan, publication/IP ownership, key-person risk.

VI.B New Product Pipeline

partially verified confidence: medium

The pipeline includes launched inference, MAIA, post-training/RL/fine-tuning, agent environments, dedicated clusters and open research models. Public materials identify several items as upcoming, so timing and development cost remain unverified.

Evidence gaps

  • Product roadmap with GA/beta dates, acceptance criteria and development cost.
  • Independent security/safety reports for agent environments, voice cloning and EEG-related research.
  • Model data provenance and license compliance schedule.

Hidden risks

  • Roadmap slippage, model safety incidents or data-rights claims could impair commercialization.

Follow-up questions

  • Which pipeline items are revenue-generating today versus demos or roadmap?
  • Provide model evaluation, safety red-team, data lineage and incident response materials.
New product and research pipeline
pipeline itemstatus from public sourcescritical technologydevelopment cost visibilityrisk
Zyphra InferenceLaunched/available as first cloud componentAMD MI355X, ROCm, custom kernels, long-context inferenceNo cost disclosedMargin and uptime for long-context workloads.
Distributed post-training / RL / fine-tuningUpcomingGPU cluster, data pipelines, RL infrastructureNo cost disclosedRoadmap slippage and compute burn.
Agent environments / sandboxed dev environmentsCloud page plus upcoming roadmapIsolation, tool orchestration, secure executionNo cost disclosedSecurity, abuse, tenant isolation.
MAIA general-purpose enterprise agentNamed in IBM release and cloud/product pagesMultimodal models, long-term memory, continual learningNo cost disclosedEnterprise reliability and safety validation.
Open model research portfolioGitHub/blog repositories for Zamba, Zamba2, Zonos, ZUNASSM/transformer hybrids, speech synthesis, EEG diffusion modelsMostly not disclosedData rights, license, safety, and monetization.
Research-to-product pipeline How public research assets appear to map into commercial cloud capabilities.
Chapter 07

07Management and Personnel

Zyphra appears founder-led with Krithik Puthalath publicly identified as CEO/Chairman, but public headcount, roles, compensation, turnover and employment arrangements are not verified and commercial databases conflict materially.

VII.A Organization Chart

partially verified confidence: medium

Only a public leadership sketch can be constructed. Internal reporting lines, board composition and functional headcount are not public.

Evidence gaps

  • Current org chart by function/location, board observer rights, committees and reporting lines.

Hidden risks

  • Governance and key-person concentration cannot be assessed publicly.

Follow-up questions

  • Provide org chart, board structure, executive reporting lines and delegated authorities.
Public leadership view Only publicly identified roles; this is not a verified internal reporting chart.

VII.B Historical and projected headcount by function and location

inconclusive confidence: low

Commercial databases show conflicting team-size estimates ranging from about 20 to 65 and differing location/founding-year signals.

Evidence gaps

  • Payroll census, contractors, location split, hires/terminations, projected headcount and recruiting pipeline.

Hidden risks

  • Burn and execution capacity cannot be modeled without verified headcount.

Follow-up questions

  • Provide month-end headcount by function/location since founding and hiring plan through 2028.
Headcount and personnel data conflicts
sourcefounding year or stageheadcount or team sizelocation signalconfidencenote
TracxnFounded 2020; Series A65 as of Mar. 2026San FranciscoLow-mediumUseful for triangulation but funding date conflicts with CB/Forge.
AI Market WatchFounded 202020San Francisco plus Montreal/LondonLowConflicts with Tracxn/Latka; use only as directional.
Latka2024/2025 profile fields44Palo AltoLowRevenue and leadership fields conflict with stronger sources.
Forge/EquityZenFounded 2021Not disclosed in rows reviewedPalo Alto / San FranciscoMediumBetter for financing/location than for employee census.
Conflicting public headcount estimates Third-party estimates only; payroll census required.

VII.C Senior management biographies

partially verified confidence: medium

Public profiles identify a founder/leadership group, but detailed biographies, ages, tenure, prior employment and current responsibilities are incomplete.

Evidence gaps

  • Detailed bios, references, background checks, prior IP/conflict review, immigration/work authorization if applicable.

Hidden risks

  • Unclear current roles may hide departure, diminished involvement or succession risk.

Follow-up questions

  • Provide executive bios, references, role descriptions, start dates and prior invention/IP assignment confirmations.
Senior-management public roster
namepublic rolesource confidencematerial follow up
Krithik PuthalathFounder; CEO and Chairman in IBM releaseHighFull bio, employment agreement, board composition, key-person plan.
Danny MartinelliCofounder; products and partnerships in EquityZen; conflicting Latka CEO fieldMedium-lowConfirm current title, customer ownership, retention and equity.
Beren MillidgeCofounder in commercial profilesMediumConfirm current title, research/IP assignments.
Tomás FiglioliaCofounder in commercial profilesMediumConfirm current title, reporting line, retention risk.

VII.D Compensation arrangements

inconclusive confidence: low

No employment agreements, founder compensation, severance, benefits or bonus terms were public.

Evidence gaps

  • Founder/executive employment agreements, salary/bonus/equity, severance, benefits, contractor terms.

Hidden risks

  • Retention or change-of-control obligations may affect runway and acquisition economics.

Follow-up questions

  • Provide compensation summary, executive agreements and benefits plan documents.

VII.E Incentive stock plans

inconclusive confidence: low

No option pool, equity incentive plan, grants, vesting schedules or exercises were public.

Evidence gaps

  • Equity incentive plan, option ledger, ISO/NSO treatment, 409A valuations, refresh grants.

Hidden risks

  • Unexpected dilution or retention challenges could be material.

Follow-up questions

  • Provide option pool, 409A history and vesting/grant schedule by employee.

VII.F Significant employee relations problems, past or present

inconclusive confidence: low

No public employee-relations issue surfaced in accessible searches, but no HR/legal records were reviewed.

Evidence gaps

  • HR complaints, investigations, worker classification, harassment/discrimination claims, employee litigation.

Hidden risks

  • Employee issues may be private and material for a small technical team.

Follow-up questions

  • Provide HR/legal employee-relations schedule and counsel confirmation.

VII.G Personnel Turnover

inconclusive confidence: low

Turnover data are not public and cannot be inferred reliably from database estimates.

Evidence gaps

  • Monthly hire/termination list, regretted attrition, offer acceptance, retention plans.

Hidden risks

  • Competition for AI talent could pressure retention and compensation.

Follow-up questions

  • Provide trailing-24-month turnover by function, level, location and reason.
Chapter 08

08Legal and Related Matters

No public red-flag litigation, SEC company match, IPO, acquisition or shutdown signal was found, but legal diligence remains incomplete. Key exposures are model safety, data rights, voice/biometric misuse, EEG/medical disclaimers, customer terms, supplier contracts and missing IP/insurance schedules.

VIII.A Pending lawsuits against the Company

inconclusive confidence: low

No direct lawsuit against Zyphra surfaced in accessible public searches, but comprehensive docket searches were not completed due public-source/tool limits.

Evidence gaps

  • Federal/state litigation search, arbitration/demand letters, counsel confirmation, threatened claims.

Hidden risks

  • Non-public disputes with employees, suppliers, data owners or customers could exist.

Follow-up questions

  • Provide litigation schedule and outside counsel representation letter.
Legal, regulatory, and public-record screen
areapublic resultconfidencediligence follow up
Pending lawsuits against ZyphraNo direct public lawsuit surfaced in accessible web search results reviewedLow-mediumRun full litigation search across federal/state dockets, arbitration, demand letters, and counsel confirmation.
Lawsuits initiated by ZyphraNo direct public result surfaced in accessible web searchesLow-mediumRequest litigation schedule and IP enforcement docket.
SEC public company statusEDGAR company search returned no matching companiesMediumConfirm no confidential filing, Reg D filings, or entity-name variants.
Regulatory agency problemsNo direct agency action surfaced in public sources reviewedLowRequest regulatory inquiry/complaint schedule and compliance counsel memo.
Terms / governing lawWebsite terms updated May 4, 2026; California law/San Francisco courts; site liability cap $100HighReview customer agreement, AUP, DPA, privacy policy, order forms, SLAs.

VIII.B Pending lawsuits initiated by Company

inconclusive confidence: low

No public lawsuit initiated by Zyphra surfaced in accessible searches.

Evidence gaps

  • IP enforcement, collections, supplier/customer disputes, arbitration claims.

Hidden risks

  • IP or contract disputes could be non-public.

Follow-up questions

  • Provide affirmative-claims schedule and dispute history.

VIII.C Environmental and employee safety issues and liabilities

partially verified confidence: medium

Physical environmental exposure appears low for a software/AI company, but data-center energy/carbon, employee safety, and AI safety/abuse risks require diligence. Public terms restrict misuse and warn against sensitive data in demos.

Evidence gaps

  • EHS policy, remote-work/office safety, supplier sustainability, incident response, abuse monitoring.

Hidden risks

  • AI misuse, unsafe agent execution or data mishandling could create customer and regulatory exposure.

Follow-up questions

  • Provide safety policies, abuse-response metrics and supplier sustainability/compliance commitments.

VIII.D Material patents, copyrights, licenses, and trademarks

partially verified confidence: medium

Public GitHub/model assets and website terms are visible, but no complete IP schedule, patent/trademark inventory, data-license schedule or contributor agreement review was available.

Evidence gaps

  • Patent/trademark schedule, license inventory, data provenance, contributor agreements, model-card and third-party dependency audit.

Hidden risks

  • Copyright/data rights, right-of-publicity, biometric voice and medical-use risks could become material.

Follow-up questions

  • Provide IP schedule, FTO analysis, data-rights memo, open-source compliance report and model licenses.
IP and license diligence matrix
asset or rightpublic evidencelicense or control publicrisk
Zyphra website/materialsTerms claim Zyphra and licensors own site materialsSite evaluation/documentation use only; competing AI training restriction in TermsNeed customer-data/model-output IP terms.
Open-source repositories/models23 public GitHub repositories and model READMEs; Zamba blog references Apache 2.0 checkpointsVaries by repository/model; full schedule not reviewedOpen licensing can reduce defensibility; compliance and contributor/IP assignment need review.
Speech/voice model ZonosOpen-weight TTS with voice cloningRepository-specific license/usage controls require legal reviewDeepfake, consent, biometric voice, copyright/right-of-publicity exposure.
EEG model ZUNAResearch-use-only; not medical/clinical useResearch disclaimer publicMedical-device, human-subject/data-rights, and health-data risks if commercialized.
Patents/trademarksNo patent/trademark schedule verified in this passUnknownFreedom-to-operate and brand protection remain unverified.

VIII.E Insurance coverage and material exposures

inconclusive confidence: low

No cyber, E&O, D&O, media/IP, product liability or workers compensation coverage details were public.

Evidence gaps

  • Insurance policies, limits, exclusions, claims history and broker letter.

Hidden risks

  • Coverage gaps may be material for voice, agent, healthcare-adjacent and cloud products.

Follow-up questions

  • Provide insurance schedule, claims history and broker adequacy assessment.
Material contracts and exposure screen
contract or exposurepublicly knownundisclosed termsrisk level
IBM Cloud multi-year GPU clusterLarge AMD MI300X training cluster for Zyphra; expansion plannedFees, minimums, uptime/SLA, data residency, termination, exclusivity, capacityHigh
AMD collaboration / MI355X platformAMD silicon central to cloud and inference storyEquity/investment terms, roadmap commitments, warranty/support, supply guaranteesHigh
TensorWave infrastructureMI355X infrastructure provider for Zyphra InferenceCapacity, price, failover, shared responsibility, securityHigh
Customer agreements/AUP/DPA/ordersTerms say service use is governed by separate agreementsCustomer data rights, indemnity, SLAs, model output ownership, limitations, audit rightsHigh
Insurance coverageNo insurance disclosure foundCyber, E&O, D&O, media/IP, workers compMedium-high
Diligence risk heatmap Risk severity and likelihood from public evidence.

VIII.F Material contracts

partially verified confidence: medium

Public materials identify IBM, AMD and TensorWave relationships and separate customer agreements, but signed contracts and material terms are not public.

Evidence gaps

  • Signed supplier, customer, investor, cloud, data-processing, model-license and partnership agreements.

Hidden risks

  • Unfavorable minimum commitments, indemnities, data rights or SLAs could alter valuation.

Follow-up questions

  • Provide all material contracts and an obligations matrix.

VIII.G Regulatory agency problems

partially verified confidence: medium

No SEC public-company match or direct regulatory agency problem surfaced, but regulatory risk remains from AI safety, privacy/data processing, voice cloning, EEG/health data, export controls and customer data handling.

Evidence gaps

  • Regulatory inquiry schedule, privacy policy/DPA/AUP, security audits, export-control review, AI governance materials.

Hidden risks

  • Regulatory scrutiny could arise from hosted models, agentic tools, voice cloning, biometrics/EEG and enterprise data processing.

Follow-up questions

  • Provide compliance controls, AUP, privacy/DPA, SOC report, export-control memo and regulatory correspondence.
Legal and regulatory diligence timeline Publicly observed legal/compliance signals and gaps.

Evidence

Evidence claims
IDClaimStatusSources
EC-001 CB Insights unicorn list row identifies Zyphra as a $1B Enterprise Tech unicorn that joined on 6/9/2025, located in Palo Alto, United States, with Bison Ventures, Future Ventures, and Intel Capital as select investors. verified high SRC-001SRC-002
EC-002 CB Insights company financials page verifies Zyphra has a public profile with four funding events and latest Series A dated June 9, 2025, but the page’s visible total-raised value and gated valuation fields do not fully reconcile with the unicorn-list valuation. partially verified medium SRC-003SRC-001
EC-003 IBM/AMD announced a multi-year infrastructure collaboration for Zyphra to train frontier multimodal foundation models on AMD Instinct MI300X GPUs on IBM Cloud; the release says Zyphra recently closed Series A at a $1B valuation and identifies Krithik Puthalath as CEO and Chairman. verified high SRC-004
EC-004 Independent industry coverage corroborates the IBM/AMD GPU-cluster relationship while noting GPU count was not disclosed and an initial deployment was available in September 2025 with planned expansion in 2026. verified medium SRC-005SRC-025
EC-005 Secondary-market profiles present Zyphra as pre-IPO, founded around 2021, headquartered in Palo Alto/San Francisco, with approximately $121M-$122M total funding and a near-$1B Series A post-money valuation; these are secondary estimates, not company financial statements. partially verified medium SRC-006SRC-007
EC-006 Zyphra’s own site positions the company as building a full-stack for open superintelligence and emphasizes sovereign AI control, transparency, safety, alignment, open foundation models, and heterogeneous compute. verified high SRC-008SRC-009
EC-007 Zyphra Cloud is publicly presented as a four-part platform—Agent/MAIA, Agent Environments, Inference, and Compute—with emphasis on long-horizon agentic workflows, long context, model/tool orchestration, distributed training/RL, and AMD-optimized infrastructure. verified high SRC-010SRC-011
EC-008 Zyphra announced Zyphra Inference as a production-grade service for large MoE and long-running agentic workloads, powered by AMD MI355X GPUs in partnership with TensorWave and serving Kimi K2.6, DeepSeek V3.2, and GLM 5.1. verified high SRC-012SRC-013
EC-009 Zyphra’s AMD/TensorWave blog says the initial commercial service is serverless inference and that distributed post-training, RL/fine-tuning, sandboxed agent environments, dedicated clusters, and bare-metal capacity are upcoming rather than fully evidenced as generally available. verified high SRC-013
EC-010 Zyphra’s public model work includes the Zamba hybrid architecture, with company blog claims of open Apache 2.0 checkpoints trained by a seven-person team on 128 H100 GPUs in 30 days. verified medium SRC-014
EC-011 Zyphra has a visible public open-source footprint: 23 GitHub repositories were observed, led by Zonos, zuna, BlackMamba, Zamba2, and tree_attention by public stars/forks at research time. verified high SRC-015
EC-012 Zonos is an open-weight TTS model trained on more than 200k hours of multilingual speech with voice-cloning capability and high-quality audio output, which is a technical asset and a misuse/safety exposure. verified high SRC-016
EC-013 ZUNA is presented as a 380M-parameter EEG foundation model trained on about 2M channel-hours with explicit research-use-only and not-for-medical/clinical-use disclaimers. verified high SRC-018
EC-014 Zamba2 is presented as a 2.7B hybrid SSM/transformer model trained on 3T tokens plus 100B annealing tokens, but its README warns the base model is not instruction-tuned and may produce harmful or offensive content. verified high SRC-017
EC-015 Zyphra Terms of Use indicate commercial cloud/API users are governed by separate customer agreement, Acceptable Use Policy, Data Processing Agreement, and orders; public demos may log and process activity; benchmarks are informational only; site liability is capped at $100. verified high SRC-019
EC-016 Public leadership and headcount data are directionally consistent that Zyphra is founder-led by Krithik Puthalath with named cofounders, but commercial databases conflict on founding year, financing date, team size, and some leadership roles. partially verified medium SRC-004SRC-006SRC-007SRC-020SRC-021SRC-022
EC-017 Public revenue, ARR, gross margin, burn, cash, debt, backlog, and customer concentration are not verified; one low-confidence commercial estimate reports 2024 ARR of $8.8M and 44 employees, but it conflicts with stronger sources on leadership and funding. inconclusive low SRC-022SRC-003
EC-018 No public IPO, acquisition, shutdown, direct SEC company match, or directly surfaced lawsuit was found in accessible sources during this public-screening pass; this is not a legal opinion or exhaustive court search. partially verified medium SRC-001SRC-006SRC-008SRC-013SRC-023SRC-024
EC-019 No named paying customer list, revenue by customer, or customer accounting for 5%+ of revenue is publicly disclosed; the public demand signal is mostly strategic partner announcements, product pages, GitHub adoption, and target-segment language. partially verified medium SRC-009SRC-010SRC-012SRC-015
EC-020 Zyphra’s strategic dependencies are concentrated around AMD silicon, IBM Cloud MI300X training infrastructure, and TensorWave MI355X inference infrastructure; terms, exclusivity, minimum commitments, and take-or-pay economics are not public. verified high SRC-004SRC-005SRC-012SRC-013
EC-021 Zyphra competes in crowded frontier model, AI agent, inference, and AI infrastructure markets where public unicorn data already includes highly valued model labs and where differentiation depends on open models, AMD optimization, long-context inference, and enterprise agent workflows. partially verified medium SRC-001SRC-006SRC-010SRC-011SRC-012
EC-022 Commercial maturity remains early from public evidence: Inference is described as available/launching, while agent environments, post-training/RL, fine-tuning, dedicated clusters, and bare metal are disclosed as upcoming or not accompanied by customer metrics. verified medium SRC-010SRC-013
EC-023 Public legal/IP diligence is incomplete: open repositories and Terms are visible, but no patent/trademark schedule, insurance coverage, signed material contracts, SOC/security audit, or complete privacy/compliance packet was reviewed. inconclusive medium SRC-015SRC-019SRC-024
EC-024 Technical evidence is unusually visible for a young unicorn because public repositories, model READMEs, and company blogs disclose architectures, datasets, hardware, and limitations; however, benchmark and safety claims remain company-authored and require independent technical validation. verified medium SRC-014SRC-016SRC-017SRC-018SRC-019
Sources
IDPublisherTitleAccessed
SRC-001 CB Insights The Complete List Of Unicorn Companies 2026-05-21
SRC-002 User-provided diligence input CB Insights unicorn list excerpt for Zyphra 2026-05-21
SRC-003 CB Insights Zyphra Stock Price, Funding, Valuation, Revenue & Financial Statements 2026-05-21
SRC-004 IBM Newsroom / PRNewswire IBM and AMD Collaborate to Advance Zyphra AI Model Training on IBM Cloud 2026-05-21
SRC-005 Data Center Dynamics AI research and product company Zyphra signs deal for large AMD MI300X cluster on IBM Cloud 2026-05-21
SRC-006 Forge Global Zyphra Technologies IPO and Stock Price 2026-05-21
SRC-007 EquityZen Zyphra Stock 2026-05-21
SRC-008 Zyphra Zyphra homepage 2026-05-21
SRC-009 Zyphra About Zyphra 2026-05-21
SRC-010 Zyphra Zyphra Cloud 2026-05-21
SRC-011 Zyphra Zyphra Inference 2026-05-21
SRC-012 Zyphra The Zyphra Inference Cloud 2026-05-21
SRC-013 Zyphra Zyphra and AMD Partner to Power Zyphra Cloud on AMD Instinct MI355X GPUs 2026-05-21
SRC-014 Zyphra Zamba: A Compact 7B SSM Hybrid Model 2026-05-21
SRC-015 GitHub Zyphra organization repositories 2026-05-21
SRC-016 GitHub / Zyphra Zonos README 2026-05-21
SRC-017 GitHub / Zyphra Zamba2 README 2026-05-21
SRC-018 GitHub / Zyphra zuna README 2026-05-21
SRC-019 Zyphra Website Terms of Use 2026-05-21
SRC-020 AI Market Watch Zyphra - AI Startup Profile 2026-05-21
SRC-021 Tracxn Zyphra - Company Profile & Team 2026-05-21
SRC-022 Latka Zyphra Revenue, Valuation & Founder Profile 2026-05-21
SRC-023 SEC EDGAR EDGAR company search for Zyphra 2026-05-21
SRC-024 DuckDuckGo / public web search Zyphra litigation, IPO, acquisition, and shutdown searches 2026-05-21
SRC-025 Futurum Group IBM and AMD Team with Zyphra to Build AI Infrastructure on IBM Cloud 2026-05-21

Disclaimer

This report is a public-evidence diligence snapshot, not investment advice. Important financial, legal, technical, and contractual facts remain non-public and should be verified directly with management and primary documents before any investment decision.