frontier_labs_count.
What counts as a frontier lab
p(Doom)1 publishes a number for how many frontier AI labs are in its model. A count is meaningless without its boundary, so the boundary is pinned here, above the count, along with the parts of it that are genuinely arguable. Everything below is derived from one roster file you can read yourself.
The definition
A frontier lab, for p(Doom)1's purposes, is an organisation that meets all four of the following. This is version 1 of the boundary; changing it changes the count, so it is versioned rather than quietly edited.
- Trains its own foundation models from scratch. Not fine-tuning someone else's base model, not serving someone else's weights. The organisation runs the pre-training.
- Trains at or near the largest publicly known scale. It has the compute, and it spends it on frontier runs rather than only on inference.
- Sets its own research agenda. A subsidiary counts if it decides what to train and whether to release it. A team that executes a parent's roadmap does not.
- Is currently active. It has shipped or announced a frontier-scale model recently enough that treating it as a live actor is not a fiction.
Note what is not in the definition: safety posture, openness, jurisdiction, or headcount. Those are attributes of a lab, and the game models several of them — but putting any of them in the membership test would turn a count into an editorial.
Status stamp: Definition under review
Criterion 2 has no number attached to it yet, and that is the honest state of affairs rather than an oversight — see what is contested. Until a threshold is pinned, this boundary is applied by judgement, and two careful people applying it would not produce identical rosters.
Form PD-1/FL · Boundary v1 · Ref pdoom-data#37 · Clerk: unassigned
What the count actually counts
Roster unavailable right now — no count is being shown rather than a remembered one.
The roster count is the size of a list you can read, not a claim about how many frontier labs exist in the world. Those are different statements and only the first one is ours to make.
What this replaced. The headline figure here used to be 7, which was six real labs plus one hypothetical entrant added together. Meanwhile the site's data file said 5, because the script that produced it counted how many of a hardcoded list of names appeared anywhere in the homepage's HTML and then applied a floor of five — so the published number was the floor, not a count. Both numbers are gone. The figure above is the length of the roster file, and nothing else.
The roster
Status stamp: Provisional — hand-entered
Every row below was typed in by hand and carries a tertiary reference, not a primary citation. Founding years are recorded at year precision because that is the precision we can stand behind. The destination for this data is pdoom-data, where it will arrive cleaned and cited; this file is the interim.
Form PD-1/FL · Source: hand-entered, interim · Destination pdoom-data#37 · Consumer pdoom1-website#177
Loading the roster…
Known omissions
Status stamp: File incomplete
The roster is knowingly missing labs that meet the definition. Listing them is cheaper and more honest than either pretending the list is complete or filling it with founding dates nobody sourced. The incompleteness is itself data, and it lives in the same file.
Form PD-1/FL · Completeness: known incomplete · Blocking: primary citations
- Loading…
Tracking over time
Status stamp: Awaiting data
This section will show the roster as a time series — labs appearing, merging, being acquired and exiting, from roughly 2000 to today — so you can replay the frontier at any date rather than only read it as of now.
No such series exists yet, in this repo or any other. A snapshot list of founding years is not a time series: it cannot tell you when a lab stopped being one, and it has no events in it. So there is no chart here. An axis with nothing on it is a claim that we measured something, and we have not.
What has to land first: pdoom-data publishes a fetchable artifact with a
labs array and an events array; pdoom1 integrates
it into the engine timeline and confirms the shape; this page then renders it. The exact
artifact URL and schema this page will consume are written down in
the roster file under tracking, so
the implementing repo does not have to re-derive them.
Form PD-1/FL · Ref pdoom-data#37 · pdoom1#962 · pdoom1-website#177 · Status: awaiting upstream
What is genuinely contested
These are not caveats added for politeness. Each one would change the number on this page if it were settled differently, and none of them is settled.
-
The compute threshold is arbitrary, and it moves
Regulators have drawn different lines — the EU AI Act uses 1025 FLOP for systemic-risk obligations, the 2023 US executive order used 1026 for reporting. Any fixed number is wrong within about a year, and whichever one you pick largely determines the count. This is the single biggest lever on the figure above, and criterion 2 deliberately does not pin it rather than pretending to a precision we do not have.
-
Where one lab ends and its parent begins
Google DeepMind is one row on this page, but DeepMind and Google Brain were separate labs until 2023. Meta runs more than one AI organisation under one roof. Counting corporate entities and counting research programmes give different answers, and it is not obvious which unit a game about labs making decisions should use.
-
The roster is Anglophone-biased, and that is a defect
Several Chinese labs train at frontier scale and are missing from the roster. That is not a ruling that they fall outside the definition — they do not. It is an artefact of where the original list came from. They are named in the omissions above rather than quietly added with dates nobody sourced.
-
Serving a frontier model is not training one
Anyone can host open-weights models. Criterion 1 counts organisations that train from scratch, which excludes a large and commercially important set of companies a casual reader might expect to find here.
-
Safety posture is an attribute, not a membership test
An earlier version of this page rated each lab's "Compute" and "Safety Focus" on an invented ordinal scale — Very High, High, Medium — with no source behind any of them. Those ratings have been removed. Putting an unsourced ordinal beside a sourced founding year makes the two look equally solid, and they are not.
-
A modelling parameter is not a lab
The AI-2027 entrant below is a slot in the game's model. It is shown because it affects the simulation, and excluded from every count because including it is exactly how the old headline figure of 7 was produced from six real labs.
Hypothetical entrant (not counted)
Why these labs matter
These organizations are developing the most advanced AI systems on Earth. Their decisions about safety, openness, and deployment directly impact global AI risk levels - the core mechanic of p(Doom)1.
In the game, you manage a lab competing in this ecosystem, making strategic choices about:
- Research priorities (capabilities vs. safety)
- Publication strategy (open vs. closed)
- Compute allocation and scaling
- Collaboration vs. competition
- Policy advocacy and governance
Learn more about real AI Safety considerations at Stampy.ai or explore our AI Safety Resources.
How this page stays honest: the definition and the contested points are written into this page's source, so they survive without scripting and change only in a reviewable diff. Every number is derived from /data/frontier-labs.json at page load — nothing is typed into the markup — and if that file fails to load the page shows nothing rather than a remembered value. Colours are pulled from the game's shipped palette.