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.
API integration
Fireworks exposes an OpenAI-compatible API at base URL https://api.fireworks.ai/inference/v1
(Chat Completions and Completions). A Responses API with MCP support is not documented on the
compatibility page, so do not rely on it.
Authentication & account setup
Public docs confirm API-key-based access via the OpenAI-compatible client libraries. Org/project
key-scoping granularity is not documented, so confirm the exact setup in the Fireworks console.
Region & residency configuration
On-demand deployments default to GLOBAL routing. Pinning to US, Canada, Europe, APAC (or a single
specific region) requires a quota granted by Fireworks and cannot be changed after the deployment
is created, per the on-demand-deployment docs. A separate "US-only serverless" tier and the
enterprise Sovereign / Virtual Cloud option (engine in your own cluster) sit at the two ends of
the residency spectrum. Default serverless in between is not region-pinned.
Rate limits, tiers & quotas
Public docs describe pricing tiers (serverless per-token, on-demand per-GPU-second, batch at 50%
off) in detail but publish no rate-limit/quota table for the serverless API. Confirm current
throughput limits in the console before sizing a production workload.
Portability & exit
DPA Sec 11.2 documents the exit path: on request within 30 days of expiry Fireworks provides a
copy of Covered Data in a commonly used format, or a self-service download, then deletes all
copies (other than Administration Data and Usage Data). An OpenAI-compatible API over a
predominantly open-weight catalogue keeps workloads portable.
The ownership factors this domain covers, drawn from the one entry record.
3
ReliabilityDoes it stay up and stay secure?
ModerateA public status page shows 22 of 23 endpoints at 100 percent and the lowest at 99.50 percent over 90 days with no listed incidents. The standard Terms carry no SLA or credit clause, and the enterprise 99.9 percent uptime terms are not public.
How this scores (AOI sub-dimensions)
Reliability3/5whether it stays up, with an SLA and status historyA public status page (status.fireworks.ai) shows 23 tracked serverless endpoints with 90-day uptime of 100 percent on 22 and 99.50 percent on the lowest (Kimi K3.1 Pro), and no listed incidents.
Security3/5the controls protecting your traffic and dataDedicated workloads run in "logically isolated environments, preventing cross-customer access or data leakage" per the data-security docs, with TLS 1.2+ in transit, AES-256 at rest, least-privilege access controls and customer-managed keys.
Compliance4/5which independent certifications and attestations it holdsFireworks' docs certifications FAQ, pricing page and blogs announce SOC 2 Type II (2023-10-27), HIPAA compliance (BAA on enterprise) and triple ISO certification (27001/27701/42001, 2025-11-19).
4
Doesn't extract your dataDo the binding terms keep your data and IP yours?
StrongThe binding Terms say Fireworks will not use Content to train or improve the Service and runs Zero Data Retention for inference with no human-review logging (Sec 3.6). The customer owns Content (Sec 3.2) and the licence is limited to providing the Service (Sec 3.4). DPA 11.2 gives a 30-day return and then deletion. The contract names exceptions: the Response API, prompt caching, and training, fine-tuning or agent features. Residency is not pinned for serverless and the sub-processor list is unverified.
How this scores (AOI sub-dimensions)
Data governance4/5retention, training-on-inputs and data ownershipToS Sec 3.6 commits that Fireworks "will not use your Content to train our own models or to improve the Service" and runs Zero Data Retention for inference (no human-review logging, no retention beyond generating and delivering Output).
Residency3/5where your data is processed and storedOn-demand/dedicated deployments can be pinned to US, Canada, Europe or APAC, but "Only GLOBAL is available by default" and quota for any pinned region "must be granted by Fireworks", with a 1.5x price for region-restricted deployments.
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-11-19
Terms of Service, Last Updated July 10, 2026 (the page URL redirects with HTTP 308 to a text PDF on cdn.sanity.io).
Privacy Policyread2026-11-19
Fireworks Privacy Notice (states it is not a contract): 'We do not use your prompts, training data, or API inputs to train or improve our AI models without your explicit opt-in'.
Documentationread2026-11-19
Fireworks data-handling docs: ZDR for open models with data held only in volatile memory during the request.
Data Processing Addendumread2026-11-19
Data Processing Addendum v3.4 (the page URL redirects with HTTP 308 to a text PDF).
Subprocessorsunverified2026-11-19
Sub-processor list referenced by DPA 6.2 at trust.fireworks.ai/subprocessors.
Securityread2026-11-19
Fireworks data-security docs: 'Data is encrypted in transit (TLS 1.2+) and at rest (AES-256).' 'Dedicated workloads run in logically isolated environments, preventing cross-customer access or data leakage.' Least-privilege access controls; minimal staff access to production, logged and reviewed.
Vendor announcementread2026-09-20
Fireworks blog post announcing SOC 2 Type II certification and HIPAA compliance (published 2023-10-27, auditor unnamed).
Vendor announcementread2026-09-20
Fireworks blog post announcing triple ISO certification: ISO 27001, ISO 27701, and ISO 42001 (published 2025-11-19, certification body unnamed).
Securityunverified2026-11-19
Fireworks' Trust Center portal at trust.fireworks.ai: a Vanta single-page application that returns HTTP 200 but renders no certificates, reports or sub-processor list without JavaScript.
Documentationread2026-11-19
Fireworks serverless pricing docs and pricing page: per-token pricing (input / cached input / output) with Standard, Priority (1.25x), Fast, Ultra-fast (preview), Batch (50% off) and Spot (30% off select models) modes.
Documentationread2026-11-19
Fireworks on-demand/dedicated-deployment docs: self-serve deployment via firectl/REST/SDKs/console, billed per GPU-second.
Vendor announcementread2026-11-19
Fireworks 'Virtual Cloud' (BYOC) blog post (dated 2025-06-16): the inference engine runs inside the customer's own VPC; access is enterprise, not self-serve.
Vendor announcementread2026-11-19
Fireworks Sovereign product page: 'Fireworks operates the inference engine, and you retain ownership of the environment, cluster, GPUs, and networking.' 'Inference and response handling run inside your cluster.' Offered to Enterprise customers, priced by contract; training is 'coming soon'.
Slaread2026-11-19
Fireworks public status page: 'We're fully operational'; 23 serverless components, 90-day window labelled Aug 2026 to Nov 2026; Kimi K3.1 Pro lowest at 99.50 percent, the other 22 at 100 percent; no incidents listed; no SLA or credit terms.
Documentationread2026-11-19
Fireworks model catalogue page: serverless-tagged families include Kimi K3.1 Pro and K3, DeepSeek V4.1 Flash, GLM 5.3 Flash and GLM-5.3, MiniMax M3.1 Flash and M3, Qwen 3.8 Max, Muse Spark Open, Ember-1, Nemotron Lightning 3.5, Rune 26B-A4B, Ultramarine 1 Flash.
Documentationread2026-11-19
Fireworks OpenAI-compatibility docs: base URL 'https://api.fireworks.ai/inference/v1'; documents Completions and Chat Completions.