Limits and Quotas
Every Kera workspace has limits based on its plan. This page documents all quotas, rate limits, and system constraints.
Plan quotas
Each workspace has resource quotas based on its plan tier. Exceeding a quota returns an error on the next write operation.
| Resource | Free | Team | Enterprise |
|---|---|---|---|
| Members | 5 | 50 | Unlimited |
| Projects | 3 | 25 | Unlimited |
| Open tickets | 100 | 5,000 | Unlimited |
| Documents | 50 | 500 | Unlimited |
| Groups | 5 | 25 | Unlimited |
| Storage | 1 GiB | 10 GiB | 100 GiB |
Archived tickets and documents do not count toward quotas. Storage includes all attachments across tickets and documents.
Rate limits
Rate limits are enforced per workspace and per user using sliding windows. They apply to all API and MCP requests.
| Scope | Free | Team | Enterprise |
|---|---|---|---|
| API requests (per workspace, per minute) | 30 | 120 | 600 |
| API requests (per user, per minute) | 60 | ||
| MCP tool calls (per workspace, per minute) | 120 | ||
When a rate limit is exceeded, the API returns 429 Too Many Requests. Retry after the window resets (1 minute).
Upload and payload limits
| Resource | Limit |
|---|---|
| Attachment upload (per file) | Workspace storage quota |
| Image data from URL (MCP) | 2 MB |
| Comment body | 65,536 characters |
| Webhook payload (inbound) | 5 MiB |
| API request body (general) | 1 MiB |
| SCIM request body | 1 MiB |
Pagination
| Endpoint | Default | Maximum |
|---|---|---|
| List tickets | 50 | 100 |
| Search tickets (MCP) | 50 | 200 |
| Other list endpoints | 50 | 100 |
Use the offset parameter to paginate through results.
MCP session limits
| Constraint | Value |
|---|---|
| Concurrent dispatches per session (SSE) | 8 |
| Session channel buffer | 64 messages |
| Session TTL (SSE) | 2 minutes |
| Keepalive interval | 25 seconds |
| Tool execution timeout | 60 seconds |
The Streamable HTTP transport (recommended) is stateless and has no session limits. SSE session limits only apply to the legacy HTTP+SSE transport used by Claude Code.
Chat and LLM limits
| Constraint | Value |
|---|---|
| Tool execution rounds per chat request | 3 |
| Tool result truncation | 4,000 characters |
Chat uses your own LLM provider (BYO LLM). Token limits depend on your provider and model. Kera does not impose token limits.
Timeouts
| Operation | Timeout |
|---|---|
| MCP tool execution | 60 seconds |
| Audio transcription | 120 seconds |
| Restate handler invocation | 3 minutes |
| HTTP read timeout | 30 seconds |
| HTTP idle timeout | 120 seconds |
Naming and validation rules
Workspace slug
- 3 to 48 characters
- Lowercase letters (a-z), numbers (0-9), and hyphens (-)
- Cannot start or end with a hyphen
- Reserved names: www, api, auth, admin, app, mail, static, cdn, status, help, docs, blog, support, billing, login, signup, dashboard, dev, staging, prod
Project key
- Short uppercase identifier (e.g. KERA, PROJ)
- Used in ticket IDs:
KERA-1,PROJ-42 - Must be unique within the workspace
Cycle dates
- ISO 8601 format:
YYYY-MM-DD - End date must be after start date