Limits and quotas
What the free beta includes, and the hard limits every request runs against.
Beta quotas
suo is a free beta today: no pricing page, no plans — just fair quotas per account, and a button to start. Records, monthly queries and partitions are metered, not charged, and you will hear from us well before that changes.
| Unit | Beta quota |
|---|---|
| Records | 1,000,000 |
| Queries per month | 1,000,000 |
| Partitions | 100,000 |
Exceeding a quota returns quota_exceeded on the request that would cross it (see Errors and limits) — existing data and traffic already within quota keep working. The dashboard's Overview tab shows current usage against each quota, and you will get a notice well before you are close to a limit.
Request limits
These apply regardless of quota, and exist to keep every account's requests fast and fair to everyone sharing the platform:
| Limit | Value |
|---|---|
| Record size | 100,000 bytes |
| Batch operations | 1,000 per write |
| Batch size | 5,000,000 bytes |
objectID length | 512 characters |
| Query length | 512 characters |
hitsPerPage maximum | 100 |
| Indexes per account | No fixed cap in beta; talk to us if you need hundreds |
What v1 does not have
- No index size cap enforcement beyond 1,000,000 records per partition — this is a soft design target for v1, not a hard wall you will hit unannounced.
- No self-hosting. suo runs only as a hosted service.
- No billing yet. A beta account cannot be charged; a future paid plan will be announced well in advance, with its own migration path.
What happens at the beta's end
Beta quotas are not a trial countdown — there is no fixed end date announced yet. When pricing ships, existing beta accounts get advance notice and a clear path to a plan that fits their usage, not a surprise cutoff.