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 92

Printed filing page 81 · Extracted page text

View on the SEC
Read the page text
Table of Contents

from  these  efforts  would  face  the  lengthy,  costly,  and  uncertain  development  and  regulatory  pathways 
characteristic of the life sciences industry, and may never generate revenue.

If  we  fail  to  manage  our  technical  operations  infrastructure,  or  experience  service  outages, 
interruptions,  or  delays  in  the  deployment  of  our  models,  platform,  and  applications,  our 
results of operations may be adversely affected.

Our systems and operations are subject to disruptions resulting from changes to our technology infrastructure. 
We have experienced, and may continue to experience, service interruptions or degraded performance due to 
software deployments, configuration changes, system updates, and new model introductions. These disruptions 
may  adversely  affect  our  ability  to  service  customers  and  could  result  in  lost  revenue,  customer  attrition,  or 
reputational harm. Further, our mitigation efforts and processes may be insufficient to prevent or minimize the 
impact  of  system  changes  on  service  availability,  and  we  may  lack  adequate  testing,  rollback  procedures,  or 
monitoring  capabilities  to  detect  and  remediate  issues  arising  from  system  changes  in  a  timely  manner.  For 
example, in March 2026, we experienced a service outage and periods of degraded performance resulting from 
a  combination  of  factors,  including  a  significant  and  rapid  increase  in  usage  demand,  compute  constraints  in 
certain components of our infrastructure, and other factors. Although we have taken and continue to take steps 
to  address  these  issues,  including  migrating  to  more  scalable  infrastructure  and  enhancing  our  operational 
processes, similar incidents may occur in the future.

In addition, continued growth in our customer base could place additional demands on our models, platform, 
and applications and could cause or exacerbate slowdowns or interrupt the availability of our models, platform, 
and  applications.  If  there  is  a  substantial  increase  in  the  volume  of  usage  of  our  models,  platform,  and 
applications,  we  will  be  required  to  further  expand  and  upgrade  our  technology  and  infrastructure.  Any 
substantial  increase  in  usage  will  also  require  increased  compute.  Because  our  compute  is  procured  well  in 
advance based on projected demand across all workloads, a significant acceleration in customer demand could 
cause aggregate capacity to fall short of the levels required to support all of our workloads concurrently at the 
scale we intend. If our committed compute proves insufficient, or the composition of our committed compute 
portfolio  differs  materially  from  our  demand  forecasts,  we  may  experience  service  disruptions,  degraded 
response times, or limitations on customer and user access to our models, platform, and applications, while also 
experiencing  constraints  on  the  compute  available  to  support  ongoing  model  development.  There  can  be  no 
assurance  that  we  will  be  able  to  accurately  project  the  rate  or  timing  of  increases,  if  any,  in  the  use  of  our 
models,  platform,  and  applications  or  expand  and  upgrade  our  systems  and  infrastructure  to  accommodate 
such increases on a timely basis. If our users are not able to access our models, platform, and applications or 
encounter slowdowns, we may lose customers or partners. In order to remain competitive, we must continue to 
enhance and improve the responsiveness, functionality, and features of our models, platform, and applications 
and the underlying compute infrastructure supporting them. Our disaster recovery plan may not be sufficient to 
address all aspects or any unanticipated consequence or incidents, and our insurance may not be sufficient to 
compensate us for the losses that could occur.

Moreover, Amazon, Google, and Microsoft provide substantial portions of the compute infrastructure that we 
use  to  host  our  models,  platform,  and  applications  and  many  of  the  internal  tools  we  use  to  operate  our 
business. Any significant disruption of, limitation of our access to, or other interference with this infrastructure 
would negatively impact our operations, degrade the availability and performance of our models, platform, and 
applications, and could cause us to lose customers who are unable to access or experience difficulties accessing 
our models, platform, and applications. Even absent a full disruption, the level of service provided by Amazon, 
Google,  and  Microsoft  could  affect  the  availability  or  speed  of  our  models,  platform,  and  applications,  which 
may also impact the usage of, and our customers’ satisfaction with, our models, platform, and applications and 
could seriously harm our business and reputation. 

Any  transition  of  the  services  and  infrastructure  currently  provided  by  Amazon,  Google,  and  Microsoft  to 
another CSP would require significant time and expense and could further disrupt or degrade delivery of our 
models,  platform,  and  applications.  Such  a  transition  could  require  us  to  re-architect  portions  of  our 
infrastructure,  retrain  or  migrate  models  and  large  datasets,  incur  data  transfer  and  duplication  costs,  and 
adapt  our  systems  to  new  tools  and  configurations,  which  could  result  in  operational  delays  and  reduced 
performance during the transition period. If Amazon, Google, or Microsoft increases pricing terms, terminates 
or  seeks  to  terminate  our  contractual  relationship,  whether  for  competitive  reasons  or  otherwise,  establishes 
more favorable relationships with our competitors, or changes or interprets its terms of service or policies in a 

81

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.