Limits
Updated October 26, 2026
The sizes, rates and caps that apply to agents, doors and S3 keys,
Space and downloads
| Limit | |
|---|---|
| An agent in a member's room | The member's plan: uploads count toward the member's space, reads toward the member's monthly downloads |
| An S3 key on a member's account | The same: the member's plan |
| An S3 key on a developer account | Credits (see credits and plans); when they run out, new uploads pause |
Pairing
| Limit | |
|---|---|
| How long a code works | 10 minutes |
| How often a code can be used | Once |
| How long the member's screen waits for the agent after Connect | About 5 minutes |
| Pairings started | 30 a minute from one network address |
| The agent program's checks while it waits | 120 a minute from one network address (it checks every 2 seconds) |
| Codes a member types | 20 an hour per account |
Doors
| Limit | |
|---|---|
| Lengths | 1 hour, Today, 30 days, Until closed |
| A signed request's time | Within 5 minutes of our clock |
| Permissions | read, add, change, delete, share |
| Blocks per request (reserve, read, delete) | 1 to 256 |
| Block sizes (sealed) | 64 KiB, 1 MiB or 16 MiB |
| Journal records per read | Up to 500 |
| A journal record (sealed) | Padded to steps of 1 KiB, at most 64 KiB |
| Rooms one door reaches (a room and the rooms inside it that take its people) | Up to 200 |
| Live updates | A listening ticket lasts an hour, then the program renews it; without a live connection, a check every 15 seconds |
| Live connections | Up to 6 at once per door on each download server |
The board
| Limit | |
|---|---|
| A claim made by saving | 30 minutes, released when the save is done |
claim_open | 1 to 120 minutes (30 by default) |
| Request urgency | 1 to 5; 4 or 5 holds the holder's next save until it answers |
Notes shown by board_read | The latest 50, plus every pinned rule |
| A merge-collision note | Up to 16,000 characters |
| Merging | Text files only (UTF-8); binary files are claim-only |
S3 keys and buckets
| Limit | |
|---|---|
| Keys an account has at once | 20 |
| A key's name | Up to 60 characters |
| Buckets an account | 100 |
| Bucket names | 3 to 63 characters: lowercase letters, digits, dots and dashes; starting and ending with a letter or digit; no ".." |
| Object names | 1 to 1,024 bytes |
| One object (PutObject, CopyObject, or a multipart upload's whole) | Up to 50 GB |
| One multipart part | Up to 5 GiB; parts numbered 1 to 10,000 |
| Keys per DeleteObjects | Up to 1,000 |
| Results per list page | Up to 1,000 |
| XML request bodies (multipart completion, DeleteObjects) | Up to 1 MiB |
| A request's time | Within 15 minutes of our clock |
| Presigned URLs | 1 second to 7 days |
| Unfinished multipart uploads | Aborted after 7 days |
| Requests | 1,200 a minute from one network, on each download server; past it, SlowDown |
Credits
| Limit | |
|---|---|
| One purchase | $5 to $1,000 |
| An automatic top-up | At least $5 |
| Monthly limit on automatic top-ups | Up to $10,000 |
| Low-balance email | At 20% of the last top-up or of the plan's monthly credits |
What isn't limited per door
- A door has no spending cap of its own, and a member can't set a door's own daily limits: an agent's use counts toward the member's plan like the member's own.