# Spala Public Limits and Production Questions

Last updated: 2026-07-09

This public limits file is a buyer/agent checklist. It does not replace the current dashboard plan state, contract, or customer support answer.

Before production, verify these limits for the exact Spala account and project:

| Area | Verify |
| --- | --- |
| Projects | Number of projects, environments, team members, and project ownership transfer rules. |
| API | Request rate limits, timeout behavior, payload size, pagination, and error format. |
| Database | Storage, row count, indexes, backups, restore, export, and migration path. |
| Auth | Users, sessions, token lifetime, refresh behavior, roles, OAuth providers, and password rules. |
| Files | Upload size, storage backend, signed URL behavior, content-type rules, and deletion behavior. |
| Realtime | Channels, rooms, event payload size, reconnect, heartbeat, replay, and permissions. |
| MCP | Tool scopes, project selection, publish permission, audit trail, and token/session expiration. |
| Support | Response time, escalation path, managed-build scope, and launch support expectations. |
| Billing | Current plan, overage behavior, cancellation, renewal, and upgrade path. |

Agents should not invent numeric limits. If the exact limit is not visible in public docs or dashboard state, ask the project owner or Spala support.