Alpha
Contact
Assess · Infercom

Can you own it?

Ownership levelSubstantialnone·limited·partial·substantial·fullAnalytical input B ยท 78.4/100

This page is a projection of the one entry record, the Use & modify and Transparency factors that Assess 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 + Reliability
  • UseReliability
  • SupportTransparency

Data governance - retention, ZDR & training

Zero content retention is the default and is set out in three binding documents. The Privacy Statement (v2.4, 2026-10-30) says "Infercom does not store, log, or retain the content of your prompts or model outputs" and that it does not use inference data for "model training, fine-tuning, or service improvement", for both EU-hosted models and the Global Model Catalog. The Terms (v2.1) repeat the no-training commitment and add that Input and Output are used for no purpose other than delivering the response.

Usage logs hold metadata only (timestamps, model identifiers, token counts, response times, error codes, API key identifiers) for 90 days. Authentication logs are kept 12 months. The DPA (v1.4, 24 September 2026) adds that personnel have no access to prompt content in the ordinary course and that sub-processors may not train either.

Two limits matter. The DPA covers EU-hosted models only. For Non-EU Models it requires a separate written addendum, so the Global Catalog's no-store commitment rests on the Privacy Statement and Terms alone. And confidentiality is only functional: the Terms contain no clause making inputs confidential, so trade secrets need an NDA or the enterprise contract.

Data & IP ownership

Your data and the knowledge derived from it stay yours. Terms v2.1 Sec 6 say you keep all rights in Input and Output and grant only a limited licence to process them to provide the Services. Nothing is retained or used to improve the service, and only open-weight models are served, so no closed-model vendor terms attach.

Sub-processors are named, but in two lists that do not match. The Privacy Statement names SambaNova, Auth0, Stripe, Metronome (US) and TECLIB, while the DPA names SambaNova, Google Ireland, Pipedrive, Stripe and TECLIB. Ask which list governs before signing. SambaNova's own further sub-processors are available on request only.

Data residency & jurisdiction

Pin EU-hosted models to get EU sovereignty, and note the operator caveat. EU-hosted models run on Infercom-owned hardware at Equinix Munich 4 and, under DPA v1.4, are processed exclusively in the EU/EEA with no fallback, overflow or load-balancing routing outside it.

The Global Model Catalog (one model today, MiniMax-M3.1-Flash) is different. The Privacy Statement says prompt content "is routed to SambaNova's global infrastructure outside the EEA, primarily in the United States" under SCCs, and the DPA excludes those models.

The other limit is the operator. The Terms (Sec 2.1) say SambaNova Systems, Inc., a US company, "operates the platform under a managed services agreement", and the DPA (Sec 7a) gives it remote administrative access to account identifiers and request metadata under SCCs Module Three. The Trust Centre FAQ says SambaNova has "operational access to the Munich facility".

The docs and pricing pages claim EU sovereign models have "no US CLOUD Act exposure". No binding document makes that claim, and the US operator relationship leaves it open, so it is marketing. Ask for the Transfer Impact Assessment (DPA Sec 7a(4)), or choose Dedicated Capacity or on-premises if operator access matters.

Compliance & attestations

ISO 27001:2022 is independently certified. The certificate (Proks Certification GmbH, No LU-IS-20250253, scope "AI & Cloud Infrastructure Services (Inference as a Service)", valid 2025-12-16 to 2028-12-15) covers the hosted service. The Cloud Security Alliance listing is STAR for AI Level 1, a self-assessment (AI CAIQ v1.1.0), not an audit.

The Trust Centre says SOC 2 is "Not yet". The SOC 2 and ISO 22301 badges on that page belong to the Equinix MU4 facility, not to Infercom. An Art. 28(3) GDPR DPA is available and incorporated by the Terms on acceptance. ISO 27701 and HIPAA/BAA are not offered.

Security controls

Security rests on the ISO 27001-certified ISMS and the controls binding in DPA v1.4 Annex 1: TLS 1.2 or higher in transit (TLS 1.3 supported), AES-256 at rest per the Privacy Statement, stateless in-memory processing, hardware-level tenant sandboxing, MFA, least privilege, access logging, DDoS protection and automated failover. Breach notification to the customer is within 48 hours.

The controls are solid but not top-rated. No independent penetration-test report or bug-bounty programme is published (vulnerabilities go to dpo@infercom.ai), there is no private connectivity, and physical controls sit with the Equinix facility and the US operator.

Pricing & cost model

Per-token rates are published in EUR, excluding VAT: gpt-oss-120b 0.22 in and 0.59 out, Gemma 4 31B 0.20 and 0.35, Whisper Large v3 0.10, E5-Mistral 7B embeddings 0.13, and the Global-catalog MiniMax M3.1 Flash 0.60 and 2.40 per 1M tokens. There are no minimums or commitment, and new accounts get EUR 5 credit that expires after 30 days. Dedicated Capacity and On-Premises are priced per engagement. The Terms let Infercom change pay-as-you-go prices on posting, so confirm live rates before committing.

Reliability posture

There is a public status page, but no SLA for pay-as-you-go. status.infercom.ai (an Atlassian Statuspage, live since 2025-12-31) shows per-model components and one public incident: a major gemma-4-31B-it problem on 2026-06-19, resolved about 21 hours later.

The Terms (Sec 8.2) give SLAs with uptime commitments only to Reserved Capacity and Dedicated Rack customers under separate agreement, and that text is not public. The speed claims (up to 10x versus GPUs) are vendor figures.

How this scores

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

1

Use and modify freelyCan you use it freely and leave without lock-in?

Strong

OpenAI-compatible API over portable open-weight models; the same checkpoints run on GPU providers or self-hosted, and single-tenant Dedicated Capacity and on-prem / air-gapped BYOC are shipped, so exit cost is low.

How this scores (AOI sub-dimensions)
Transparency & lock-in5/5how portable it is and how easily you can leaveOpenAI-compatible API over portable open-weight models, plus a shipped single-tenant Dedicated Capacity product and on-prem / air-gapped BYOC deployment (ev-onprem).
Cost3/5how the pricing model compares and how predictable it isPer-token EUR rates are published (ev1): gpt-oss-120b 0.22/0.59, Gemma 4 31B 0.20/0.35, MiniMax M3.1 Flash 0.60/2.40 per 1M tokens, with no minimums.
2

TransparencyAre the binding terms published, legible and independently checkable?

Moderate

Terms v2.1, Privacy Statement v2.4 and DPA v1.4 are all published, and sub-processors are named. The level is moderate for four reasons. The Privacy Statement and DPA sub-processor lists do not match. The DPA excludes Non-EU Models. SambaNova's own sub-processors are on request only. The docs claim no US CLOUD Act exposure while the binding texts disclose a US operator.

How this scores
Not a scored AOI dimension. For a hosted provider, transparency is whether the binding terms are published, legible and were actually read - the read/unverified evidence below, not a certification. A strong rating here must trace to a retrieved binding document.
What this means for adoptionYou substantially own EU-sensitive workloads here. Zero content retention, no training, metadata-only logs and a portable open-weight exit with shipped single-tenant and air-gapped options keep your data yours, and the Terms, Privacy Statement and DPA state this contractually. Ownership stops short of full because sovereignty is conditional and oversold. The DPA covers EU-hosted models only, the Global Model Catalogue sends prompts outside the EEA, a US company operates the platform with remote access, and the docs' no-CLOUD-Act claim has no binding text behind it. Pin EU-hosted models, sign the DPA, and use Dedicated Capacity or on-premises if operator access matters.

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.

Vendor announcementread2026-11-19
Pricing page and home page: OpenAI-compatible API on SambaNova RDU hardware in Munich, with per-token EUR rates (gpt-oss-120b 0.22/0.59, Gemma 4 31B 0.20/0.35, Whisper 0.10, E5-Mistral 0.13, MiniMax M3.1 Flash 0.60/2.40 per 1M tokens, excluding VAT) and no minimums.
Vendor announcementread2026-11-19
Trust Centre (first-party surface): no persistent storage of prompts or outputs, and usage logs hold metadata only for 90 days.
Third-party analysisunverified2026-07-25
SambaNova partnership announcement: Infercom as a sovereign AI provider, Luxembourg HQ, EU jurisdiction, Munich deployment, ISO 27001, GDPR-safe/EU-compliant.
Third-party analysisread2026-11-19
SambaNova and Infercom Q&A: SambaNova partners with Infercom to launch a European sovereign inference cloud with all data under European jurisdiction.
Third-party analysisread2026-11-19
Independent gateway partnership page (updated October 2026): Infercom models are routed through the Opper AI gateway, OpenAI-compatible, EU German datacentres by default plus US and JP regions, native BF16.
Vendor announcementread2026-11-19
Zero Data Retention glossary: ZDR means content is not persisted after the request and is not used for training.
Vendor announcementread2026-11-19
EU Sovereign AI page and docs: EU sovereign models run in Munich; "Our US operating partner SambaNova has remote access to run the platform; the DPA names it"; "Luxembourg company, controlled in Europe, no US parent".
Privacy Policyread2026-11-19
Privacy Statement v2.4, last updated 2026-10-30 (binding): "Infercom does not store, log, or retain the content of your prompts or model outputs".
Data Processing Addendumread2026-11-19
Data Processing Agreement v1.4, 24 September 2026 (binding): an Art.
Privacy Policyread2026-11-19
Privacy Statement v2.4 Sec 8 and 8.1 (binding): for Global Model Catalog models not hosted on EU infrastructure, "your API requests (including prompt content) are routed to SambaNova's global infrastructure outside the EEA, primarily in the United States".
Documentationread2026-11-19
On-Premises page, Trust Centre FAQ and Sovereign AI page: shipped today are SambaRack SN40L on-premises racks, "Air-gapped deployment support", "Typically ~90 days from contract to production", BYOC ("fine-tunes of supported architectures load immediately") and one contract with Infercom delivered with SambaNova engineers.
Terms of serviceread2026-11-19
Terms v2.1 and Privacy Statement v2.4 give functional protections only (transient processing and discard, no secondary use, logical isolation, encryption, access controls) and NO express confidentiality clause over customer inputs.
Terms of serviceread2026-11-19
Terms of Service v2.1, 2026-03-09 (binding).
Securityread2026-11-19
ISO/IEC 27001:2022 certificate No LU-IS-20250253 issued by Proks Certification GmbH: certified company INFERCOM SCS, scope "AI & Cloud Infrastructure Services (Inference as a Service) and the systems that support these services", valid 2025-12-16 to 2028-12-15, IAF and DAkkS accreditation marks.
Securityread2026-11-19
CSA STAR registry listing "Infercom Inference-as-a-Service": STAR for AI Level 1, AI CAIQ self-assessment v1.1.0, listed 2026-07-02.
Slaread2026-11-19
Public status page (Atlassian Statuspage JSON API): Infercom Inference Service component since 2025-12-31, per-model components, one public incident (2026-06-19 to 2026-06-20, impact major, gemma-4-31B-it), and a scheduled maintenance notice for 2026-11-20.
Documentationread2026-11-19
Developer docs list the Inference API catalogue (EU-hosted gpt-oss-120b, gemma-4-31B-it, E5-Mistral-7B, Whisper-Large-v3; Global MiniMax-M3.1-Flash).