Loading the catalogue…
Loading the catalogue…
Compliance posture
Sovereignty ladder · how the level was reached
Stav's assessment · serving-side
Fireworks AI is a US-incorporated operator (Fireworks.ai, Inc.) whose serverless inference is globally routed by default across a multi-cloud footprint of 8+ clouds and 18+ regions, with true EU-only residency available only as a paid, contracted add-on rather than the baseline — this undercuts the catalogue's unqualified 'eu_hosted' framing. The composite lands in elevated-risk territory primarily because of the two highest-weighted sovereignty dimensions: legal exposure is high given confirmed CLOUD Act reach over a US entity with a footprint spanning the US and EEA, and serving residency is weak because EEA-only processing is opt-in, not default. Security posture is the clear strength, backed by SOC 2 Type II and a triple-ISO certification stack (27001/27701/42001) plus HIPAA support and documented encryption/isolation controls. Serving retention is reasonably strong for open models (zero-retention default) but narrows for Fireworks' own proprietary models, and contractual posture is workable — a DPA and subprocessor list exist — but SCC and audit-rights detail could not be independently confirmed in this review. Stav's operational verdict: routed-only by default; sovereign EEA-pinned serving is available but requires an explicit enterprise regional-pinning contract and further verification of its DPA's transfer mechanics before it can be treated as a default-sovereign path.
Serverless inference is globally routed by default across 8+ clouds and 18+ regions; EU-only/regional pinning exists only as a premium add-on, not the baseline posture the catalogue's 'eu_hosted' tag implies.
Certifications & legal documents
Fireworks.ai, Inc. is a US-incorporated entity confirmed CLOUD Act-exposed, with a documented processing footprint spanning the US and EEA countries, placing the operator under US lawful-access authority regardless of where a given request is physically served.
Zero Data Retention is the default for open models with no training without opt-in, but Fireworks' own proprietary models (f1, FireFunction) may log prompts/outputs for bulk analytics, a narrower carve-out not clearly surfaced in marketing copy.
Multiple current, sourced certifications (SOC 2 Type II, ISO 27001/27701/42001, HIPAA) plus documented TLS/AES-256 encryption and logical workload isolation, with no unresolved breach history noted.
A standalone DPA (v3.2) and subprocessor disclosure page are published, but the DPA's SCC/international-transfer clauses were not text-extractable for verification and a service-provider carve-out creates some ambiguity about which privacy terms govern a given customer.
Risk assessment
Fireworks' serverless inference is globally hosted by default across a multi-cloud 'Virtual Cloud' spanning 8 major clouds and 18+ regions; guaranteed regional pinning (including an EU or US-only tier) is a premium add-on rather than the default posture, which is a material gap against a baseline 'EU-hosted' expectation. source ↗
DATA_RESIDENCYThe contracting entity is Fireworks.ai, Inc., a US company, making it subject to US CLOUD Act / lawful-access authority regardless of which physical cloud region serves a given customer's traffic. source ↗
LEGAL_EXPOSUREZero Data Retention applies by default only to open models; for Fireworks' own proprietary models (e.g. f1, FireFunction) prompt and generation data 'may be logged to enable bulk analytics to improve the model,' a narrower guarantee than the general 'no training without opt-in' commitment stated in the privacy notice. source ↗
SERVING_RETENTIONA third-party subprocessor disclosure (GitHub's own subprocessor list, which names Fireworks AI as its AI-inference subprocessor) shows Fireworks' processing footprint spanning United States, Iceland, and Germany — broader and more specific than what is independently verifiable from Fireworks' own public disclosures without a JS-rendered session. source ↗
SUBPROCESSINGIndependent status trackers show generally strong measured uptime (~100% over 30-day windows) but also record periodic transient incidents (e.g., a brief 3-minute outage) and user reports of intermittent 503 Service Unavailable errors on the inference API. source ↗
RESILIENCESafeguards
Zero Data Retention by default: Fireworks does not log or store prompt or generation data for open models without explicit user opt-in; prompt/generation data exists only in volatile memory for the duration of the request. source ↗
Data encrypted in transit (TLS 1.2+) and at rest (AES-256); dedicated workloads run in logically isolated environments preventing cross-customer access. source ↗
Fireworks holds ISO 27001 (information security), ISO 27701 (privacy), and ISO 42001 (AI management) certifications in addition to SOC 2 Type II and HIPAA support, with certificate PDFs published via its Trust Center. source ↗
US-only serverless / data-zone residency option is available for customers who need guaranteed in-region processing, including integration into Azure Foundry's PTU US Data Zone with unified enterprise governance controls. source ↗
Fireworks publishes a standalone Data Processing Addendum (v3.2) alongside its Terms of Service and Privacy Notice for enterprise customers. source ↗
Customers can access, download, or delete their data through the Service, and Fireworks states customer data in active workflows can be permanently deleted with auditable confirmation via secure-wipe processes. source ↗
Privacy-policy issues
Narrower retention guarantee for proprietary models source ↗
The headline 'No AI Training on Your Data' commitment in the Privacy Notice is qualified in the technical docs: prompt/generation data for Fireworks' own proprietary models (e.g. f1, FireFunction) may be logged for bulk analytics to improve the model, a carve-out not obviously flagged in the marketing-facing privacy commitments.
Global-by-default serverless routing source ↗
Serverless inference is globally hosted by default rather than pinned to a customer's region, so EU enterprises must explicitly purchase a regional/EU-only tier to obtain residency guarantees rather than receiving them as standard.
Service-provider carve-out from Privacy Notice source ↗
Fireworks' Privacy Notice states that when it acts as a service provider for other businesses, the Notice does not apply to that processing, directing data subjects instead to the business customer's own privacy notice — this can create ambiguity about which document governs a given end-user's data.