Limits and quotas

Trestle bounds individual uploads, total local usage, multipart overhead, provider reads and response ranges before allocating unbounded work.

Discover current limits

curl "$TRESTLE_URL/api/v1/capabilities" \
  -H "Authorization: Bearer $TRESTLE_TOKEN"

The capability response exposes upload and request-body ceilings. The Files dashboard reports the configured storage provider, quota and current accounted usage.

Rejection behavior

{"error":{"code":"quota_exceeded","message":"The storage quota would be exceeded."}}

An oversized or over-quota upload is rejected before publication. A failed staged write does not become downloadable metadata. Range requests are validated and restricted to one bounded interval.

Capacity planning

• Leave headroom for staged writes and backups when using local storage.
• Monitor both database metadata growth and provider object usage.
• Use S3 lifecycle/versioning according to your recovery policy.
• Do not treat application quotas as a substitute for host filesystem limits and alerts.