Method & status
What sets this service apart from a directory is that every field carries evidence. These are the rules we never bend.
Status discipline
- Confirmed — verified against a primary source, with source link and date. Technical/product facts on the provider's own site (API, pricing, models) qualify here.
- Claimed — the provider asserts it, but it has not been verified against a DPA/certificate. All sovereignty and compliance marketing starts here.
- Planned — a stated goal or "coming soon". Never conflated with achieved. Certifications are marked achieved vs. planned — that distinction is decision-critical.
- Unknown — not researched yet. Reported honestly; we never guess. A wrong "confirmed" is worse than an honest "unknown".
Selection criteria — why these providers
The register is organised into four layers — what you actually buy: (1)inference APIs (the core comparison: they host models and sell a token API — Swedish ones like Berget and grunden.ai AND European ones like Mistral and Scaleway, with jurisdiction honestly stated per field), (2) AI gateways/routers that route to others' models (Opper), (3) assistant platforms procured as finished products (Intric), and (4) compute/GPU where you run the model yourself (Glesys, Aixia, Mimer). Swedish versus European is thus not a category — it is the jurisdiction axis, shown as a tag and a filter. Pure consultancies, resellers without their own operations and products without public information are not included. Providers whose identity or category is contested are clearly marked and excluded from requirement answers until resolved.
Who verifies
The database is built and maintained by Gustaf Baltsar Garnow within the OpenSverige community, on a non-profit basis and with no ties to any provider — no affiliate links, no sponsored placement (see About). Corrections with a source are accepted on an ongoing basis via the community's Discord; providers can upgrade claimed to confirmed by submitting binding documentation (DPA, certificate, price list).
How a verification works
Every data point goes through the same chain: (1) the primary source is read — the provider's own documentation, pricing page or legal terms, never secondary sources for confirmed; (2) the value is classified according to the status discipline above — technical product facts on the provider's own page can become confirmed directly, while sovereignty and compliance statements remain claimed until verified against binding documents; (3) source and date are stored on the field, not on the page — every individual data point can be traced; (4) contradictions are flagged — if a new scrape conflicts with a manually verified value, nothing is overwritten; the record goes into the review queue and is resolved by hand. A false "confirmed" is worse than an honest "unknown".
Are you a provider and want a data point confirmed?
We never change a status on request — but we are happy to read evidence: publish the document at a public URL on your own domain and post the link in our Discord. The full process, and what counts as evidence per field type, is on the page for providers.
Data sources & scraping
The foundation is manually verified facts (source + date per field). On top of it, an automatic re-scrape of the providers' public pages runs every week — robots.txt and machine-readable TDM reservations (tdmrep, noai) are respected by all fetch engines, an identifying User-Agent, rate limiting, ungated content only. Under-rendered pages are escalated to a rendering fetch, and known pricing views that require interaction (tabs that load on click) are fetched by a headless browser that the pipeline drives — the same robots rules apply to it too. Which engine fetched what is logged in the raw data, so the fetch itself has provenance too. The scrape replaces earlier observations of the same field — it never accumulates the sources' material. The scraper may only corroborate existing values or fill fields that stand as unknown — it may never silently change a verified value. The detectors are deterministic (patterns, not AI guesses), and their findings are reviewed against evidence excerpts before they become facts.
Freshness & change history
Every run is diffed against the previous one. Changed fields are logged with a date and shown openly in the change history (also as JSON). That history — who changed what, and when — is the part no answer engine can replicate by re-scraping today, and it means a claim can always be traced back in time.
Open data
The entire comparison dataset is free to cite and reuse with attribution (CC-BY-4.0): machine-readable via the JSON API, llms.txt and llms-full.txt. Please cite with status and verification date — "claimed" is not "confirmed".