Service limits

Oso Cloud enforces operational limits to provide consistent latency for authorization decisions and a predictable experience for all interactions.

Limits

Startup and Growth Plans

All requests

Description	Threshold	Behavior
Concurrency limit	Unlimited	Not applicable

Read (Authorization) Requests

Description	Threshold	Behavior
Rate limit	Unlimited	Not applicable
Size limit	10 MiB	`413 Content Too Large`
Context facts per request	100 facts	`413 Content Too Large`
Query execution time	20 seconds	`400 Bad Request`

Write Requests

Description	Threshold	Behavior
Rate limit	30,000 fact updates per minute	`429 Too Many Requests`
Size limit	960 KiB	`413 Content Too Large`
Entries per batch request	1,000 entries	`413 Content Too Large`
Facts updated per wildcard delete	10,000 facts	`413 Content Too Large`

Oso Sync

Description	Threshold	Behavior
Concurrency limit	1 per environment	`429 Too Many Requests`
Size limit	10 GiB per fact type	`413 Content Too Large`

Free Plans

All requests

Description	Threshold	Behavior
Concurrency limit	4	`429 Too Many Requests`

Read (Authorization) Requests

Description	Threshold	Behavior
Rate limit	1,000 requests per second	`429 Too Many Requests`
Size limit	10 MiB	`413 Content Too Large`
Context facts per request	20 facts	`413 Content Too Large`
Query execution time	20 seconds	`400 Bad Request`

Write Requests

Description	Threshold	Behavior
Rate limit	1,000 fact updates per minute	`429 Too Many Requests`
Size limit	960 KiB	`413 Content Too Large`
Entries per batch request	20 entries	`413 Content Too Large`
Facts updated per wildcard delete	10,000 facts	`413 Content Too Large`

Oso Sync

Description	Threshold	Behavior
Concurrency limit	Not applicable	Not applicable
Size limit	Not applicable	Not applicable

How write request rate limiting works

Oso Cloud tracks fact additions and deletions per request. While an addition affects at most 1 fact, a deletion may affect multiple facts in the presence of wildcards. If the number of fact updates exceeds the threshold in a sliding 1-minute window, Oso Cloud starts throttling additional write requests, holding them until the threshold is no longer exceeded. If the threshold remains exceeded after 30 seconds, throttled requests are rejected with 429 Too Many Requests.

Syncing fact types that exceed the size limit

To synchronize larger datasets, shard a single fact type across multiple definitions in your YAML configuration by substituting a concrete value for one or more arguments:

# Before
has_relation(Repository:_, String:_, Organization:_): ...

# After
has_relation(Repository:_, String:parent, Organization:_): ...
has_relation(Repository:_, String:child, Organization:_): ...

Get Started

Develop

Deploy and Manage

Limits

Startup and Growth Plans

Free Plans

How write request rate limiting works

Syncing fact types that exceed the size limit

​Limits

​Startup and Growth Plans

​Free Plans

​How write request rate limiting works

​Syncing fact types that exceed the size limit

Limits

Startup and Growth Plans

Free Plans

How write request rate limiting works

Syncing fact types that exceed the size limit