Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 21 additions & 11 deletions chapters/limits-and-specifications/concurrency.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,35 +3,45 @@
description: "Rate limiting and transcriptions concurrency"
---

In order to provide a smooth experience and optimal performance for all users, Gladia accounts can have up to **3** differents limits
for **Free**, **Paid** & **Enterprise** users :

<Note>
Need a higher concurrency limit?

The value listed below are default values. We can provide high concurrencies based on your needs, so feel free to
[contact us](https://www.gladia.io/contact).

</Note>
In order to provide a smooth experience and optimal performance for all users, Gladia provides 3 plans:

Check warning on line 6 in chapters/limits-and-specifications/concurrency.mdx

View check run for this annotation

Mintlify / Mintlify Validation (gladia-95) - vale-spellcheck

chapters/limits-and-specifications/concurrency.mdx#L6

Did you really mean 'Gladia'?

| Plan type | Usage limit <br /> (per month) | Max Transcriptions in concurrency <br />(pre-recorded) | Max Transcriptions in concurrency (Live) |
| -------------- | ------------------------------ | ------------------------------------------------------ | ---------------------------------------- |
| **Enterprise** | Unlimited | On demand | On demand |
| **Paid** | Unlimited | 25 | 30 |
| **Free** | 10 Hours | 3 | 1 |

## Hitting your concurrency limit

When you hit your concurrent session limit, both the **Live** and **Pre-recorded** APIs return a **429** status code.

<Tip>
Prefer the [official SDK](/chapters/how-to-use-gladia/sdk) for Live integrations: it already handles the WebSocket lifecycle (reconnection, session continuity, retries, buffering, and related timing). See the [Live quickstart](/chapters/live-stt/quickstart).
</Tip>

### Default values

| API | Default |
| --------------------- | -------------------------------- |
| Live (WebSocket) | 30 concurrent sessions |
| Pre-recorded (async) | 25 parallel jobs + 300 queued |

<Note>
Any limit above the default requires a capacity check. [Contact the sales team](https://www.gladia.io/contact) to request an increase.
</Note>

- **Usage limit** : (**free-tier** users only)

This determines the number of hours a user can transcribe a given month. This is a limitation for free tier users only.
This determines the number of hours a user can transcribe a given month.

- **Concurrency** : (depending on free/paid tier)

This refers to the maximum number of transcription (pre-recorder or real-time) that a user can process at the same time.
For asynchronous transcriptions, Paid plan users can queue up to 300 requests, but only will still have 25 max processed concurrently.

- **Realtime session duration** : (all plans)

Check warning on line 42 in chapters/limits-and-specifications/concurrency.mdx

View check run for this annotation

Mintlify / Mintlify Validation (gladia-95) - vale-spellcheck

chapters/limits-and-specifications/concurrency.mdx#L42

Did you really mean 'Realtime'?

A single realtime (live) transcription session cannot exceed **3 hours**. After 3 hours, the session will be terminated. For longer events, start a new session when approaching the limit.

Check warning on line 44 in chapters/limits-and-specifications/concurrency.mdx

View check run for this annotation

Mintlify / Mintlify Validation (gladia-95) - vale-spellcheck

chapters/limits-and-specifications/concurrency.mdx#L44

Did you really mean 'realtime'?

- **API level rate limit** : (same for every user)

Expand Down