the usual one
In your project
Installed beside the project the questions are about. Every source is reachable, including the runtime state that only exists once something has booted.
Which way to run it
The same server, started from three places. They differ in what runs around it, which is the only thing that decides what it can answer — there is no edition, no tier, and nothing to buy.
unattended
In CI
Nothing boots and nothing leaves the machine. Answers come from bundled knowledge and from files on disk, and every result says which of the two.
no project
From a checkout
The server answers about itself and about the documentation. No installation takes part, so it claims nothing about one.
The reach of each
Six sources, and the gaps are the reason this table exists. A comparison in which everything is present somewhere tells the reader nothing they cannot guess.
| What it can answer | In your project | In CI | From a checkout |
|---|---|---|---|
| bundled knowledge | |||
| package files | — | ||
| booted installation | — | — | |
| dynamic registrations | — | — | |
| docs.typo3.org | — | ||
| this server’s own rules |
A dash is not a failure. It is a source that is not reachable from there — and a tool that needs it says so at registration rather than answers from the next one down and says nothing.
Pick the first one unless you cannot
The other two exist because a machine sometimes cannot boot a TYPO3 installation — a pipeline, a review of a project you do not run, a skill in the making against nothing in particular. Neither is a smaller version of the first; each answers less and says so.
The same binary in all three
Nothing is compiled differently and no flag turns a capability on.
What changes is what the machine around it can be asked, which is why
this page compares places rather than products.