Limits

SashiDo doesn't cap the number of requests your app serves: capacity comes from the engine and instances you run. These are the limits that do exist, and what to do when you reach one.

Your app's Parse Server

	Limit	When you reach it
Request duration	60 seconds	Move long work to a background job
File upload	20 MB per file	Resize or compress on the client; split large data
Query results	100 objects unless you set limit	Set limit, and page by createdAt rather than skip
Live Queries	Only the classes enabled in App Settings › Live Queries	Enable the class; for more than one instance, ask for Redis (Live Queries)
Instances	Your plan's scaling limits (engine_scaling_config in GET /users/info); with high availability at least 3	Contact support for higher limits

Management API and access tokens

	Limit
Requests	600 per minute per token; above it 429 with Retry-After
Request body	300 KB of JSON
Tokens	50 active per account; a token can be limited to up to 100 apps
Build log	The last 1,000 lines per request (default 300)
Deployments list	50 per request (default 10)
Activity (audit log)	100 per page (default 50)

The Parse proxy

Calls to your data through /apps/{id}/parse/... with a token:

	Limit
Duration	30 seconds per request
Response	10 MB; narrow it with limit and keys
File upload	10 MB
batch	1 to 50 writes

How long things are kept

	Kept for
Activity (audit log)	1 year; security events 3 years (logins, password changes, tokens, collaborators, deleted apps, revoked sessions, refused access, reads of your users)
Build logs	With the build in Runtime › Builds
Database backups	See Automatic Database Backups › List in the dashboard