Sanity Content Lake: Transitioning low-traffic workloads to the Free plan

Optimizing costs for low-traffic workloads often involves migrating from a paid subscription to the Sanity Free plan. This transition leverages a shared infrastructure model to eliminate monthly fees, provided the project remains within the documented quotas for document counts, asset storage, and API requests.

While the general quotas are defined, there is uncertainty regarding the behavioral difference between sustained API quotas and burst rate limits. In low-concurrency environments, it is unclear how the system distinguishes between a temporary spike in traffic and a sustained breach of the Free plan limits.

Verification Requirements

To validate this behavior, the following are required:

• Analysis of rate-limit headers in API responses during concurrent request bursts.
• Monitoring the Usage tab in the Sanity Management Console during traffic spikes.

What is the specific triggering mechanism for burst rate limits compared to sustained quotas on the Free plan? How does this behavior differ across current API versions?