The paper trail

Small print.
Wide open.

A clear path from a claim to the page it came from. Here’s the filing, the research, and how we read it.

The documentS–1Anthropic, PBC26 OCT 2026 · 421 PP.
01The original SEC filingThe authoritative source, in your browser.SEC · HTML 02Download the saved filingThe complete 421-page document, optimized for downloading.PDF · 46 MB 03Download the full researchFindings, customer examples, calculations, and source references.Markdown

Page by page

Go straight to the source.

Page references count physical pages in the saved PDF, starting at 1. The printed filing number is shown separately when available.

Enter a page from 1 to 421. No PDF download needed.

From the filing

PDF page 42

Printed filing page 31 · Extracted page text

View on the SEC
Read the page text
Table of Contents

performance  characteristics  across  workload  types,  the  composition  of  our  committed  compute  portfolio, 
including  the  mix  of  accelerator  architectures  procured  from  our  partners,  reflects  our  demand  forecasts  and 
development  roadmap  assumptions  at  the  time  those  commitments  are  made.  If  the  magnitude  or  mix  of 
workloads  we  need  to  support  differs  materially  from  those  forecasts,  whether  due  to  changes  in  model 
architecture,  customer  demand,  internal  operations,  or  research  priorities,  the  composition  of  our  available 
compute may not optimally match our needs in a given period. This could affect our ability to serve customers, 
develop models, and support internal operations. 

If we fail to secure sufficient compute, or if we fail to effectively direct the limited compute we have across our 
workloads to develop and deploy models with capabilities at least comparable to those of our competitors, we 
risk  falling  behind  the  technological  frontier.  The  pace  of  AI  development  is  extremely  rapid,  with  successive 
versions  of  models  emerging  in  compressed  timeframes,  often  measured  in  months  rather  than  years.  As  a 
result, even a brief period without access to sufficient compute could cause us to fall behind quickly. With AI 
development, the gap between frontier models and those one or two versions behind can be significant in terms 
of  capability,  performance,  and  commercial  applicability.  Customers,  partners,  and  software  developers  may 
shift  to  competitors  whose  models  offer  superior  capabilities,  and  we  may  be  unable  to  attract  or  retain  the 
technical talent necessary for frontier research if our researchers lack access to adequate compute or if we are 
not perceived as operating at the forefront of model development. Any inability to maintain our position at the 
frontier could result in loss of customers and revenue, diminished brand and reputation, and a decline in our 
competitive position, each of which may be difficult to regain. If we are unable to manage the foregoing risks, 
our business, financial condition, and results of operations could be adversely affected.

If  our  actual  compute  requirements  differ  materially  from  our  projections,  we  may  fail  to 
secure sufficient compute to meet our needs or we may be committed to excess compute that 
remains underutilized.

The  competitive  and  structural  dynamics  of  the  compute  market  require  us  to  make  binding  financial 
commitments for compute months or years in advance of our day-to-day delivery and use. Chip manufacturers, 
CSPs, and data center developers require advance commitments in order to allocate production capacity, plan 
infrastructure  investments,  and  manage  their  own  supply  chains.  As  a  result,  we  must  forecast  our  compute 
requirements well in advance of their deployment and commit capital accordingly, often with limited ability to 
adjust commitments if our needs change.

These forecasts for future compute usage are inherently uncertain. Our actual compute requirements depend on 
numerous factors that are difficult to predict, including the pace of our research progress, the compute intensity 
of  training  techniques  we  develop  or  adopt,  changes  in  the  competitive  landscape  that  may  require  us  to 
accelerate  or  modify  our  development  plans,  customer  demand  for  inference  compute,  and  the  evolution  of 
hardware or other technological efficiencies and changes. If we underestimate our compute requirements, we 
may  be  unable  to  secure  sufficient  compute  to  support  our  forecasted  customer  demand  and  model 
development roadmap. In the past, we have significantly underestimated our compute requirements, which left 
us  capacity  constrained  and  impacted  both  product  development  and  deployment.  Further,  the  timing  of 
compute  coming  online  may  not  align  with  the  timing  of  demand  growth,  which  could  result  in  periods  of 
excess or underutilized compute and committed cash outflows that do not produce immediate revenue.

Our ability to forecast and secure the compute we need is further challenged by our ongoing transition from a 
cloud-only, fixed-time arrangement compute model to a hybrid model that includes directly leased chips that 
are  hosted  in  dedicated  data  center  facilities  leased  and  operated  on  our  behalf,  to  our  specification.  This 
transition  introduces  additional  variables  into  our  procurement  planning,  including  the  timing  of  facility 
completion,  the  pace  at  which  newly  commissioned  facilities  achieve  full  operational  capacity,  our  ability  to 
operate,  maintain,  and  integrate  on-premise  capacity  with  cloud-based  infrastructure,  the  operational 
execution of our suppliers, and the performance of hardware in new facility environments. Delays in securing 
energy,  water,  and  other  critical  services  for  these  facilities  could  further  slow  the  pace  at  which  newly 
commissioned  compute  becomes  available  for  use.  Errors  in  forecasting  any  of  these  transition-related 
variables  could  compound  our  risks  related  to  securing  sufficient  compute  and  result  in  either  capacity 
shortfalls or underutilized capacity during the transition period.

We  have  entered  into,  and  expect  to  continue  to  enter  into,  long-term  agreements  for  compute  and  other 
compute resources that involve minimum purchase commitments, take-or-pay provisions, and other terms that 

31

Text is provided for reference. Check the original for tables, images, and exact formatting.

Find a section 16 starting points

Section links may begin before the exact paragraph cited in a finding. PDF numbers below use physical pages.

  1. Founders’ letterp. 3SEC
  2. Defined termsp. 12SEC
  3. Prospectus summaryp. 16SEC
  4. Risk factorsp. 38SEC
  5. Management’s discussion & analysisp. 144SEC
  6. Businessp. 190SEC
  7. Governancep. 254SEC
  8. Executive compensationp. 275SEC
  9. Related-person transactionsp. 293SEC
  10. Principal & selling stockholdersp. 299SEC
  11. Capital-stock rightsp. 303SEC
  12. Shares eligible for future salep. 318SEC
  13. Underwritingp. 327SEC
  14. Auditor change & expertsp. 345SEC
  15. Financial statements & notesp. 347SEC
  16. Part II & exhibit indexp. 413SEC

How this was made

Read in full.
Kept in context.

A snapshot of the filing dated , rather than a live record of later events.

3primary reviewers
421pages reviewed
43image instances checked

The review

Three primary reviewers read non-overlapping ranges of the complete main filing. All 43 embedded image instances were transcribed and visually reviewed, including the founders’ letter, charts, and customer case studies. Financial tables were also checked visually for dates, units, and column alignment.

A separate reviewer checked the draft’s calculations, accounting interpretations, and customer qualifications. An additional check covered the later merged findings. The result is 62 findings and 21 customer examples.

The boundary

Companion contracts and other exhibits named in the filing’s index are separate documents and were not independently reviewed. Customer outcomes, technical benchmarks, forecasts, and scientific priority claims remain attributed company or customer disclosures.

The numbers

Dollar figures are U.S. dollars. H1 means the six months ended June 30; Q2 means the three months ended June 30. The 2026 interim financial statements are unaudited. Our calculations show their inputs and are labeled separately from reported values.

Blank fields stay undisclosed. Figures with different periods, conditions, or potentially overlapping scopes are kept separate. An earlier tender price is not an IPO price.

What the evidence labels mean
Reported in filing
A company disclosure, with the period and accounting basis retained.
Company estimate / company claim
An estimate or assertion attributed to the company, with its uncertainty preserved.
Our calculation
A derived figure using cited inputs. It is not a separately reported company metric.
Customer example
A selected case study, with its measurement limits. It is not representative ROI.
Proposed / conditional
A status qualifier for an arrangement that is not yet effective or depends on stated conditions.

About updates. This edition is tied to the October 26, 2026 filing. Any later revision should identify its new source date and preserve the basis of earlier claims.

The footnotes are only the beginning.Explore the findings Read the story
The original, in context

Open the footnote.

A closer look at the filing

Anthropic · Form S-1PDF 1

Opening page 1…

Filed October 26, 2026. PDF is approximately 46 MB and opens only when requested. Section links may precede the exact cited paragraph.