Skip to main content
This page lists CollabKit limits and benchmark targets for the latest version.

​
Rate Limits for APIs

When rate limits are exceeded, APIs may return 429 Too Many Requests.
LimitValue
General REST API600 requests/minute per account, burst 120 requests/10 seconds
Create user120 requests/minute per account, burst 30 requests/10 seconds per room
Create room60 requests/minute per account
List endpoints300 requests/minute per account
Storage upload20 uploads/minute per user, 100 uploads/minute per room
Storage delete60 deletes/minute per user
Storage list files60 requests/minute per user
Webhook/workflow CRUD60 requests/minute per account
Auth/login routes10 requests/minute per IP
List users page size100 users per page

​
CollabKit Store Limits

LimitValue
Stores per room10
Writes to store1 write per 250ms
Store sizeTBD
Each named store counts toward the per-room store limit. Store entries, document shape, and payload-size limits are TBD.

​
Comment Limits

LimitValue
Top-level comments per room1,000
Comment payload sizeTBD
Replies are limited to one level of nesting. A top-level comment can have replies, but replies cannot have nested replies.

​
File Storage Limits

LimitValue
File size1 MB per file
Per-room storage quota5 GB
Files per room1,000
Upload rate20 uploads/minute per user, 100 uploads/minute per room
Delete rate60 deletes/minute per user
List files rate60 requests/minute per user
Files are scoped to rooms. Storage rate limits are enforced per Worker isolate for now.

​
Room Limits

Users can join a room with two roles: editor | viewer.
ScenarioLimit or target
Maximum users in one room1,000 users with up to 200 active editors
Maximum users in an all-editor room500 active users, all editors
Concurrent joins and time SLA1.5sec (P50), 3sec (P95)
  • Editors:
    • Allowed to mutate stores, files, add comments and more.
    • Use for users who actively mutate room state, stores, comments, storage, broadcasts, or CRDT documents.
  • Viewers:
    • Allowed to subscribe to all the changes in a room, including presence, stores, comments, files and more.
    • Use for users who need real-time updates but do not need to write collaborative state

​
Webhook/Workflow Delivery SLAs

SystemSLA
WebSocket event delivery5-30 seconds after the event
Analytics availability30 seconds after the event
WebSocket SLAs describe when connected clients should receive room events after the server processes the event. Analytics SLAs describe when event data should be available for querying or display.