Methodology
How this data is made
Last updated 2026-10-17
Primary sources only
Every fact in the vendor database is taken from a primary source: the vendor's own documentation, trust centre, legal terms, or pricing pages, read at the time of the check. Third-party writeups, forum threads, and press coverage are not sources. Nothing is filled in from general knowledge or assumption.
What "verified" means
A populated fact always carries two things: the URL of the primary source it was checked against, and the date of that check. "Verified" means the linked page supported the claim on that date, not that the claim is true forever. Dates are shown per section so staleness is visible rather than hidden.
Where a fact could not be confirmed from a primary source, the profile shows "Not verified". An honest gap is more useful to a procurement decision than a guess.
Evidence levels
Certifications and data residency are graded on one rule, applied the same way to every vendor:
- Contractual: the commitment is in the vendor's data processing agreement, terms or service agreement, or the certification can be traced to a certificate, an audit report, or the certifying body (for example a downloadable certificate, a report available on request, or a regulator's authorisation).
- Stated: the vendor says it on its own product, documentation or trust pages, but nothing contractually binding or independently traceable backs it.
- Not verified: nothing was found, or the only wording is "aligns with", "designed to" or similar. A certification at this level is not listed; data residency shows "Not verified".
For data residency, Contractual means the agreement lets the customer choose where data is stored or processed and commits the vendor to it. Stated means the vendor's pages say data stays in a region, or document a product control that keeps it there. A HIPAA BAA or GDPR DPA counts only when a BAA or DPA is named: "HIPAA compliant" or a HIPAA programme alone does not. A certification must cover the product being profiled; one held for an unrelated product line is not listed. Equivalent wording always gets the same level, whichever vendor uses it.
Inclusion criteria
The database covers vendors offering single-tenant LLM hosting (inference infrastructure where the customer's workload runs on capacity not shared with other customers), wherever the vendor is based. Category describes how the service is delivered, in three kinds: dedicated GPU/inference clouds, hyperscaler dedicated capacity, and managed self-host platforms. Geography is never a category; it is recorded as parent jurisdiction, regions and sovereign for (below). A vendor qualifies if it publicly documents a dedicated or single-tenant deployment option. Commercial relationships play no part in inclusion; see the disclosure page. The rules on sourcing, verification, corrections, and conflicts of interest are set out in the editorial policy.
Regions
The Regions column records where a vendor documents capacity, not every named data-centre location. A region is added only where the vendor's own material names that geography; it is never inferred from a neighbouring one. Regions use one controlled vocabulary, extended as vendors are added:
- Countries: ISO 3166-1 alpha-2 codes, shown by name
(for example
US, orGBfor the United Kingdom). A country outside a bloc is never folded into it. - Blocs: a named group of countries treated as one
data area.
EUcovers the EU/EEA member states. - Areas: coarse geographies that carry no law of
their own:
APAC(Asia-Pacific), andGLOBALwhere the vendor documents worldwide availability without a per-region breakdown.
Category, jurisdiction and residency
Four facts are kept apart, because buyers often conflate them:
- Category: how the service is delivered.
- Parent jurisdiction: the country (ISO code) where the vendor's parent company is incorporated, from a register or the vendor's legal terms. This is the law that can compel the company, wherever its data sits.
- Data residency: whether the vendor commits to keeping data in a customer-chosen region, graded by the evidence levels above.
- Sovereign for: recorded for a jurisdiction only when all of these hold, each from a primary source: the parent company is incorporated there (or in a member state, for a bloc); the vendor documents capacity there; data residency is at least Stated; and the vendor itself claims sovereignty for that jurisdiction for the profiled service. Parent incorporation alone is not enough, and the field is never inferred. The schema rejects a record where these do not line up.
A region in one country does not change the parent's jurisdiction. See the jurisdictions index for vendors and analysis grouped by jurisdiction.
Update cadence
The database is reviewed manually. There is no automated collection. Every addition, update, and correction is a dated entry in the public changelog, so you can see exactly what changed and when.
Corrections
If a fact on this site is wrong or has gone stale, email simon@singletenant.ai with the page, the claim, and (if you have it) a link to the primary source that contradicts it. We re-check the claim against the vendor's published material; if it fails, the data is corrected, the verified date is updated, and the correction is recorded in the changelog, as set out in the editorial policy. Vendors are welcome to submit corrections about their own profiles on the same terms: a correction needs a primary source, whoever sends it.