Alpha
Contact
Implement · Groq

Can you run it?

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

This page is a projection of the one entry record, the Reliability 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 + Reliability
  • UseReliability
  • SupportTransparency

API integration

Groq exposes an OpenAI-compatible API, documented in its OpenAI-compatibility docs. Point an existing OpenAI client at base URL https://api.groq.com/openai/v1 with a Groq API key; the /openai/v1/models endpoint lists active models. Open-weight models run on Groq's custom LPU hardware for very low latency, so the integration surface is familiar and the performance profile is different. The docs flag that some advanced OpenAI features are not yet supported.

Region & ZDR configuration

Per the your-data docs, zero data retention is available to all customers via Data Controls, so ZDR is a setting to enable and not an enterprise-gated feature. Enabling ZDR also stops the up-to-30-day troubleshooting and abuse logs.

Region control is less mature. EU capacity exists (Helsinki, launched July 2025, now listed as Vantaa and London), but retained data is stored in US GCP buckets and region pinning is unconfirmed. If EU residency is mandatory, validate the current region-pinning behaviour during onboarding.

Rate limits, tiers & quotas

Groq's models page gives developer-plan quotas: gpt-oss-120B and gpt-oss-20B at 250K TPM / 1K RPM, gpt-oss-safeguard at 150K TPM and Qwen3.8-27B at 250K TPM / 1K RPM. The Llama models and enterprise preview models are contact-sales. Groq does not publish the full paid-tier throughput structure, so confirm the quotas for your account in the Groq console before sizing a production workload.

Portability & exit

At the API level Groq is portable. The OpenAI-compatible endpoint over open-weight models (per the docs and supported-models catalogue) means the same checkpoints run on other providers or self-hosted. The custom LPU hardware and a curated, narrower catalogue (no full DeepSeek / GLM / Mistral or arbitrary fine-tunes) are lock-in and coverage considerations. Moving keeps the API portability but not necessarily every model or the latency profile.

How this scores

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

3

ReliabilityDoes it stay up and stay secure?

Moderate

A public status page shows 100% uptime for the API and production models for Aug to Nov 2026, but no SLA is published (service level commitments are a paid add-on) and the self-serve catalogue turns over quickly.

How this scores (AOI sub-dimensions)
Reliability3/5whether it stays up, with an SLA and status historyA public status page exists (groqstatus.com, incident.io) showing Aug to Nov 2026 uptime of 100% for the API and the six production model components and 99.98% for preview models, with a "fully operational" banner.
Security4/5the controls protecting your traffic and dataSOC 2 Type II controls per the trust-centre claim, DPA Annex II measures (ZTNA, subprocessor assessments, regular security and vulnerability testing), a private HackerOne vulnerability programme (groq.com/security), and ZDR/Data Controls documented in the Services Agreement and docs.
Compliance4/5which independent certifications and attestations it holdsThe DPA covers GDPR, UK and Swiss transfers via deemed-signed SCCs and points to a sub-processor list.
4

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

Strong

The binding Services Agreement states the customer retains IP in Inputs/Outputs, Groq may not train on them, and Inputs/Outputs are not accessed, stored or retained except to provide the service. The your-data docs confirm no default inference retention and ZDR for all via Data Controls. Caveats: up-to-30-day troubleshooting and abuse logs unless ZDR is on, and the opt-in batch (30-day) and fine-tuning features retain data in US GCP storage.

How this scores (AOI sub-dimensions)
Data governance4/5retention, training-on-inputs and data ownershipThe binding Groq Services Agreement (last modified 2026-06-22) and DPA (2025-10-15) state that the customer retains all IP in Inputs/Outputs and that Groq may not use Inputs/Outputs to train or fine-tune models (Sec 4.2, all tiers).
Residency3/5where your data is processed and storedEU capacity exists (Vantaa, Finland, launched as Helsinki in July 2025, plus a London site per the platform page), satisfying the "EU region available" anchor.
What this means for adoptionYou substantially own low-latency inference here. The Groq Services Agreement (last modified 2026-06-22) and the your-data docs confirm you keep all IP in Inputs/Outputs, Groq never trains on your data, inference is not retained by default, and ZDR is available via Data Controls. The OpenAI-compatible API gives a portable exit. The level falls short of full for four reasons. Inference can be logged for up to 30 days for troubleshooting or abuse unless ZDR is on. The opt-in batch and fine-tuning paths retain data in US GCP storage. The SOC 2 report, trust centre and ISO posture are unverified. The US HQ (DPA permits US processing) carries CLOUD Act exposure. Turn on ZDR, keep sensitive data out of the batch and fine-tuning paths, and use an EU-sovereign provider if you need mature EU residency.

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.

Documentationread2026-11-19
Your Data in GroqCloud docs: by default Groq does not retain customer data for inference requests.
Terms of serviceread2026-11-19
Groq Services Agreement (Last Modified 2026-06-22).
Data Processing Addendumread2026-11-19
GroqCloud Data Processing Addendum (Effective 2025-10-15).
Data Processing Addendumread2026-11-19
GroqCloud Business Associate Addendum (Effective 2025-10-15) supplements the Services Agreement.
Securityread2026-07-25
Groq trust centre states SOC 2 Type II is maintained (2025 report) and hosts the GDPR/HIPAA compliance posture and a sub-processor list (updated November 2025).
Securityunverified2026-11-19
trust.groq.com and trust.groq.com/subprocessors return a roughly 7 KB single-page-app shell whose only visible text is 'Groq Trust Center'.
Subprocessorsunverified2026-11-19
Groq publishes its sub-processor list and the nature of services they provide at trust.groq.com/subprocessors (referenced by the DPA, sections 7.2 and 8.2).
Vendor announcementread2026-11-19
Groq announced a European data centre footprint in Helsinki, Finland on 6 July 2025 with Equinix (the newsroom post now returns 404).
Vendor announcementunverified2026-11-19
groq.com/pricing redirects to the Groq home page and shows no prices.
Documentationread2026-11-19
Groq OpenAI-compatibility docs: use the OpenAI client libraries against base URL https://api.groq.com/openai/v1 with a Groq API key.
Documentationread2026-11-19
Groq supported-models docs.
Documentationread2026-11-19
Groq model-deprecation docs: announcement by email and docs, transition phase, optional automatic upgrade, end of life.
Documentationread2026-11-19
Groq models page developer-plan limits: gpt-oss-120B and 20B at 250K TPM / 1K RPM, gpt-oss-safeguard at 150K TPM / 1K RPM, Qwen3.8-27B at 250K TPM / 1K RPM.
Terms of serviceread2026-11-19
Groq Acceptable Use & Responsible AI Policy (Effective 2025-10-15) bars illegal or harmful use, use beyond rate limits, automated high-risk decisions without human supervision, malware and lethal weapon functions without human control.
Slaread2026-11-19
Groq public status page (groqstatus.com, incident.io; status.groq.com redirects), 2026-11-19: 'fully operational'; Aug 2026 to Nov 2026 uptime API 100%, Production 6 components 100%, Preview Models 7 components 99.98%.