Zuplo Platform Limits
This document describes the limits that apply to your Zuplo account.
Managed Dedicated Environments
The limits in this document are primarily for Zuplo's managed edge environment . For managed dedicated environments and enterprise agreements, most limits are fully customizable to meet your specific requirements.
General
Below are general limits that apply to deployments on Zuplo's managed edge environments.
| Feature | Description | Limit |
|---|---|---|
| Environment Variables | The number of environment variables you can create | Free/Builder Plans: 50 variables per environment, Other Plans: 100 per environment |
| Environment Variable size | The size of an environment variable | ~5kb per variable |
| Request Duration | The maximum time a request can take to complete | Free/Builder Plans: 30 seconds, Other Plans: No Limit |
| Memory | The maximum memory available when processing a request | Free/Builder Plans: 128mb, Enterprise Plans: Custom |
| Requests per second | The maximum number of requests per second | Development Environments (Working Copy): 1000 requests per minute. No Limit outside of plan monthly limit |
| Log Size | The size of a log entry | Zuplo Portal live logs are limited to ~10kB. Excess will be truncated. For third-party logging providers, the value depends on the provider. Zuplo imposes no limit. |
| Request Body Size | The maximum size of an incoming request body | 500 MB |
| Response Headers | The total size of all response headers | 128 KB |
| Subrequests | The maximum number of subrequests per request | 1,000 |
| Simultaneous Open Connections | The maximum number of simultaneous open connections per request | 6 |
HTTP connections
In Zuplo's managed edge environment, HTTP connections have timeouts to ensure efficient use of resources. These timeouts apply to both incoming connections from clients to Zuplo and outgoing connections from Zuplo to your origin servers.
Between client and Zuplo
| Type | Limit (seconds) | HTTP status code at limit |
|---|---|---|
| Connection Keep-Alive HTTP/1.1 | 400 | TCP connection closed |
| Connection Idle HTTP/2 | 400 | TCP connection closed |
Between Zuplo and origin server
| Type | Limit (seconds) | HTTP status code at limit |
|---|---|---|
| Complete TCP Connection | 19 | 522 |
| TCP ACK Timeout | 90 | 522 |
| TCP Keep-Alive Interval | 30 | 520 |
| Proxy Idle Timeout | 900 | 520 |
| Proxy Read Timeout | 180 | 524 |
| Proxy Write Timeout | 30 | 524 |
| HTTP/2 Pings to Origin | Off | - |
| HTTP/2 Connection Idle | 900 | No |
API keys
Consumers & keys
Zuplo doesn't impose a hard cap on the number of consumers or keys you can create. However, usage of the service is subject to "fair use" policies meaning if your usage is deemed excessive we may limit usage. If you require specific limits please contact sales to discuss pricing plans.
Our general guidelines for what constitutes fair use are as follows:
- Free Plan: 100 consumers or keys
- Builder Plan: 1,000 consumers or keys
- Enterprise Plan: Custom
Consumer metadata and tags
- Consumer
metadata- The JSON encoded object can't be larger than 1kb. - Consumer
tags- Each consumer is limited to 5 key value pair tags.
API key management operations
Requests to API key management operations on the Zuplo Developer API (dev.zuplo.com) are limited to 100 requests per second.
API key authorizations
One API key authorization can be made per request. Enterprise plans can request custom limits to allow multiple API key authorizations per request.
Cache
The cache API and abstractions on top of it such as ZoneCache have the following limits:
- Maximum size per cached item: 512 MB
- Maximum cache calls per request: 1000