fauna · Rate Limits

Fauna Rate Limits

Fauna announced End-of-Service in March 2025 and fully shut down its hosted service on May 30, 2025. Historically Fauna throttled by Transactional Operations (TROs / TWOs / TCOs) on a per-database basis with per-plan ceilings, and exposed standard 429 responses. The service is no longer accepting traffic; this artifact preserves the historical rate-limiting shape for archival purposes.

Fauna Rate Limits is the machine-readable rate-limit profile for fauna on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring operations and GB.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, serverError, and serviceUnavailable.

Tagged areas include Database, Document Database, Serverless, Rate Limiting, and End of Service.

4 Limits Throttle: 429
DatabaseDocument DatabaseServerlessRate LimitingEnd of Service

Limits

Transactional Read Operations (TROs) per database (historical) database
operations
per-plan ceiling; Free included 100K/day; paid plans metered
Historical; service discontinued May 30, 2025.
Transactional Write Operations (TWOs) per database (historical) database
operations
per-plan ceiling; Free included 50K/day; paid plans metered
Historical; service discontinued May 30, 2025.
Transactional Compute Operations (TCOs) per database (historical) database
operations
per-plan ceiling; Free included 50K/day; paid plans metered
Historical; service discontinued May 30, 2025.
Storage per database (historical) database
GB
Free included 5GB; paid plans metered per-GB-month
Historical; service discontinued May 30, 2025.

Policies

End of Service
Fauna service was decommissioned on 2025-05-30. New signups closed in March 2025; existing tenants were given a migration window. This rate-limit artifact is archival.
Historical retry pattern
When operational, Fauna returned 429 with Retry-After on quota exhaustion; clients should have used exponential backoff with jitter.
Historical idempotency
Fauna FQL transactions were ACID and idempotent within a single transaction; retries of the same FQL were safe.

Sources