Fireworks AI Review: Hosted Open Models, Billed per Token or per GPU Second

Limits and errors

• Variability: Fireworks says serverless users are subject to minor latency and performance variability during high volume periods.
• 429 and 503: When using Serverless, you may experience 429 Too Many Requests or 503 Service Overloaded. To avoid 429s, stay below the adaptive rate limits. To reduce the likelihood of 503s, upgrade to Priority tier.
• Account request limit: All API usage on an account shares one request-throughput envelope: 10 RPM with no payment method or no credits, and 6,000 RPM (maximum) with a payment method and active credits. The 6,000 RPM cap applies account-wide and is a fixed, non-adaptive ceiling.
• Dedicated deployments: The inference error codes page says there are no account-level rate limits on dedicated and on-demand deployments, and that a 429 there indicates the deployment's processing capacity is saturated. The account quotas page says on-demand and dedicated deployments are not limited by adaptive serverless TPM upper bounds, and that their requests still count toward account-wide request limits.

Billing

• Zero balance: If your balance reaches zero and Auto Reload is not enabled, usage pauses until you add credits.
• Spend limit: When usage reaches 100% of the monthly spend limit, all API requests pause automatically across serverless inference, deployments, and training. This suspension does not apply to Enterprise accounts.
• Post-paid: Contracted customers may have the option to move to post-paid billing.

Identity, data and audit

Custom SSO, SCIM and audit logs need an Enterprise account.

• SSO and SCIM: By default, Fireworks supports Google SSO. If you have an enterprise account, Fireworks supports bringing your own identity provider using an OpenID Connect (OIDC) or SAML 2.0 provider. Coordinate with your Fireworks AI representative to enable the integration. SCIM provisioning is available for enterprise accounts and works with supported directory providers, including Okta, Microsoft Entra ID, and Google Workspace. Custom SSO must be configured before you can enable SCIM provisioning. To request SCIM enablement, contact your Fireworks AI representative, and Fireworks will enable Directory Sync for your account. API keys and service accounts are not blocked by SSO enforcement.
• Retention and training: Fireworks has Zero Data Retention by default. Fireworks does not log or store prompt or generation data for any open models, without explicit user opt-in. For the Response API, with store=True (the default), stored conversation data is kept for up to 30 days. Setting store=False prevents any conversation data from being retained. Across every training surface, your training data is never used to train Fireworks-owned or shared models.
• Certifications: Fireworks has achieved all three ISO certifications covering security, privacy, and AI management: ISO 27001, ISO 27701 and ISO 42001. Fireworks lists SOC 2 Type II as certified. Fireworks is HIPAA compliant.
• Audit logs: Audit logs are available for Enterprise accounts. Audit logs include data access logs. All read, write, and delete operations on storage are logged, normalized, and enriched with account context. You can view audit logs with the Fireworks CLI or retrieve them with the List Audit Logs API.

Regions and compatibility

• Regions: By default, Fireworks deployments are multi-region, and Fireworks can move and spread them across regions as needed. Supported multi-regions are GLOBAL, US, CANADA, EUROPE and APAC. New accounts receive GPU quota for the GLOBAL multi-region only. The US, CANADA, EUROPE and APAC multi-regions and all single regions start at zero quota and must be granted by Fireworks. The --region flag pins a deployment to a single region, and a deployment with a --region you have no quota for is rejected at creation.
• Data residency: On Enterprise accounts, data residency restricts inference on the account to a single region. Contact your Fireworks representative if you need this enabled. The listed restriction is US, on us.api.fireworks.ai. For a region that is not listed, contact Fireworks sales.
• Anthropic compatibility: Fireworks Anthropic compatibility serves only POST /v1/messages and does not support Anthropic server side tools.