Limits & status
Know the boundaries
Section titled “Know the boundaries”| Area | Current boundary |
|---|---|
| Workspace throughput | Each workspace has one writer: its Durable Object. |
| Retry deduplication | Bounded after recovery. A retry outside the retained horizon is refused rather than reapplied. |
| Reads | No fixed row cap; wide reads stream in keyset chunks of 1,000 rows. |
| Bulk writes | Up to 1,000 rows per transaction; larger sets commit in batches of 1,000. Not optimistic or queued offline. |
| Relations | Types follow one level for relation filters and nested creates; deeper structures are validated by the engine. |
| Live windows | No fixed row cap; every loaded page stays live and streams in keyset chunks of 1,000 rows. |
| File uploads | 25 MB cap. File bytes live in a separate R2 bucket. |
| Presence and broadcast | Ephemeral, over the workspace socket. Broadcast messages are not stored or replayed. |
| Release status | Pre-1.0, with deployment and recovery validation still in progress. |
Setup, migrations and deployment are documented in Setup and Migrations. The API is pre-1.0.
The landing-page panel
Section titled “The landing-page panel”The interactive panel on the landing page is a client-side demo. It does not connect to a TapeDB database or measure performance.