Implement · Berget AI

Can you run it?

Ownership levelSubstantialnone·limited·partial·substantial·fullAnalytical input B · 70.4/100

This page is a projection of the one entry record, the Doesn't fail you and Data control factors that Implement covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.

Which domain expands which factor

AssessUse & modify + Transparency
ImplementData control + Doesn't fail you
UseDoesn't fail you
SupportTransparency

API integration

Berget exposes an OpenAI-compatible chat/completions API at https://api.berget.ai/v1 - point an existing OpenAI client at the base URL and API key. Because the surface is OpenAI-shaped, it works with LangChain, LlamaIndex and the standard OpenAI SDKs. Integration is a configuration change, not a rewrite.

Authentication & account setup

Authentication uses bearer API keys; migrating from OpenAI is a matter of switching the API key and endpoint. Fine-grained organisation/project key scoping and rotation policy were not detailed in the sources reviewed this session, so if key-scoping is a control requirement, confirm the available granularity in the account console before rollout.

Region & ZDR configuration

There is no region toggle to configure - all inference runs in Sweden/EU by default per the Privacy page, and zero data retention is the default under the Terms of Service (Berget never stores prompt input or model output content). EU residency and no-store behaviour are the out-of-the-box posture rather than a gated enterprise add-on, which removes the most common EU-residency onboarding friction: there is no non-EU region to accidentally route to, and no sales step required to enable ZDR.

Portability & exit

The exit path is clean. Berget speaks the OpenAI-compatible API over portable open-weight checkpoints (Llama, Mistral, Gemma, gpt-oss, GLM), so the same models run on other providers or self-hosted stacks. Switching cost is dominated by re-pointing the base URL and re-validating outputs, not re-engineering. On exit, the Terms give a 30-day post-termination export window for Customer Data before it is irreversibly deleted.

How this scores

The ownership factors this domain covers, drawn from the one entry record.

Doesn't fail youDoes it stay up and stay secure?

Moderate

Independent press reports production customers (Riksbanken, 300+ pilots), but there is no public uptime SLA, status page or independent pen-test, and no SOC 2 / ISO 27001 attestation is confirmed.

How this scores (AOI sub-dimensions)

Reliability2/5whether it stays up, with an SLA and status historyIndependent press reports production customers (the Swedish central bank Riksbanken as flagship, 300+ pilot/commercial customers), but no public uptime SLA, status page or failover documentation is available, so availability is not independently observable.

Security3/5the controls protecting your traffic and dataThe Security page documents industry-standard technical/organisational measures - encryption in transit, network isolation, access controls, monitoring - and a PGP-based vulnerability-reporting channel; inference runs inside a secure Swedish network and content is not retained.

Compliance2/5which independent certifications and attestations it holdsA GDPR DPA is published (governing processing of personal data), but SOC 2 / ISO 27001 / ISO 27701 / HIPAA attestations are not confirmed and the DPA's own clauses were not readable this session.

Doesn't extract your dataDo the binding terms keep your data and IP yours?

Strong

The Terms of Service (read this session) state Berget never stores prompt input or model output content, the Customer retains all title and IP under a licence scoped only to providing the Service, and Customer Data is exportable for 30 days post-termination then deleted; EU-only infrastructure with no US transfers puts it outside US CLOUD Act reach.

How this scores (AOI sub-dimensions)

Data governance4/5retention, training-on-inputs and data ownershipZero data retention (Berget never stores prompt input or model output content), customer retains all title and IP under a service-scoped licence, a 30-day post-termination export window and open-weight-only routing are all confirmed in the Terms of Service read this session - a strong, now document-grounded posture.

Residency5/5where your data is processed and storedInfrastructure entirely on EU/Sweden-only servers with no US data transfers per the Privacy and Security pages, Swedish ownership (a public-record jurisdictional fact) placing Berget outside the US CLOUD Act, and independent EU tech-press corroboration of the sovereign-infrastructure positioning.

What this means for adoptionYou substantially own workloads here: the binding Terms confirm zero retention of prompt/output content, customer-retained ownership under a service-scoped licence, and a 30-day export window, while EU-only residency and Swedish ownership keep you outside US CLOUD Act reach and a portable open-weight exit keeps switching cheap. What holds it below full is verification depth - no independent audit or SOC 2 / ISO 27001 attests the data-handling guarantees, and the GDPR DPA's clauses and sub-processor list were not reachable. Adopt as an EU-sovereign default, but contractualise the data terms in the DPA and request current attestation status for regulated procurement.

Sources

The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.

Terms of serviceread2026-07-25

Berget AI Terms of Service: Berget will never store any of the actual prompt content used as model input or any of the output content generated by the LLMs it hosts (zero data retention); as between Berget and the Customer, the Customer retains all title and intellectual property rights in the Customer Data and grants Berget a licence limited to hosting, processing and transmitting it to provide the Service; Customer Data is retained for 30 days after termination for export/recovery then irreversibly deleted; Berget may process aggregated, anonymised data that does not identify the Customer or any natural person.

Privacy Policyread2026-07-25

Berget AI Data Privacy Policy: all data stays within EU-based servers in Sweden and never leaves Berget's infrastructure; zero retention; GDPR-compliant by design.

Securityread2026-07-25

Berget AI Security page: industry-standard technical and organisational measures including encryption in transit, network isolation, access controls and system monitoring, plus a PGP key for encrypted vulnerability reporting; no SOC 2 / ISO 27001 certification is stated.

Data Processing Addendumunverified2026-07-25

Berget AI publishes a Data Processing Agreement governing the processing of personal data contained in Customer Data; its internal clauses (transfer mechanism, SCCs, sub-processor list) were not reachable this session.

Vendor announcementread2026-07-25

Berget AI landing page - Swedish-owned, EU-sovereign inference, not subject to the US CLOUD Act, no US data transfers, OpenAI-compatible (marketing framing).

Documentationunverified2026-07-25

OpenAI-compatible chat completions API at https://api.berget.ai/v1 with bearer API keys; developer documentation.

Third-party analysisread2026-07-25

Independent Mastra model directory lists Berget.AI as a provider using the OpenAI-compatible /chat/completions endpoint at https://api.berget.ai/v1, serving multiple open-weight models.

Third-party analysisread2026-07-25

Independent EU tech press (Tech.eu): Berget AI is a Stockholm-founded (2024) provider running open language models on sovereign infrastructure in Sweden so sensitive data stays within national borders under EU jurisdiction; raised EUR 2.1M (Luminar Ventures), with the Swedish central bank (Riksbanken) as flagship customer and 300+ pilot/commercial customers.

Vendor announcementunverified2026-07-25

Pay-as-you-go per-token pricing plus prepaid token packs; ZDR the default.

Vendor announcementread2026-07-25

Berget Code launch: agentic coding assistants that keep code in Sweden; Berget does not train any models on the code sent to the service.