Document quotas for remote generation (#3680)

Co-authored-by: fern-api[bot] <115122769+fern-api[bot]@users.noreply.github.com>
Co-authored-by: Devin Logan <devinannlogan@gmail.com>

Author: 3 people

fern/products/sdks/how-it-works.mdx

@@ -58,4 +58,21 @@ sequenceDiagram
 ![SDK generation architecture diagram](./images/sdk-gen.png)
 </Frame>
 </Accordion>
-</AccordionGroup>
+</AccordionGroup>
+
+## Quotas
+
+Cloud (remote) generation uses a [leaky bucket](https://en.wikipedia.org/wiki/Leaky_bucket) rate-limiting algorithm with the following default limits:
+
+| Parameter | Value |
+| --- | --- |
+| Burst capacity | 10 generations |
+| Refill rate | 5 generations per minute |
+
+You can run up to 10 generations in quick succession. Fern then replenishes your allowance at 5 generations per minute, so if you hit the limit, subsequent requests will be throttled until enough capacity is restored. In practice, this only affects automated workflows that trigger many generations in a tight loop — occasional manual runs won't come close to the limit.
+
+<Note>
+Rate limits apply only to cloud generation. [Local generation](/learn/sdks/deep-dives/self-hosted) using `--local` isn't subject to any quotas.
+</Note>
+
+If your team needs higher quotas, contact support@buildwithfern.com.