Platform
Plans & limits
Plans differ by monthly request quota, telemetry retention, and AI analysis budget. The technical ingest limits below apply on every plan.
Plan tiers
For current prices and monthly request quotas, see the pricing section. At a glance:
- Starter - free, single app, short retention. Good for trying Silker.
- Pro - multiple apps, larger quota, AI analysis budget, priority support.
- Business - team features and higher (effectively unlimited) request quota.
- Enterprise - custom limits, indefinite retention, dedicated support.
Telemetry retention
How long requests and threats are kept before automatic cleanup:
| Plan | Retention |
|---|---|
| Starter | 7 days |
| Pro | 30 days |
| Business | 90 days |
| Enterprise | Indefinite |
Ingest limits
These limits keep ingestion fast and abuse-resistant on every plan:
| Limit | Value |
|---|---|
| Rate limit (per API key) | 120 requests / minute (sliding window) |
| Max events per batch | 200 |
| Max payload size | 2 MB per request |
| Field truncation | Short fields capped at 2 KB; bodies/headers/queries at 64 KB |
The SDK batches events and respects these limits automatically. You only hit them when posting to ingest directly - which is not a supported public integration path.
Quota & rate-limit responses
When a limit is reached, ingest returns a 429 with a machine-readable code:
RATE_LIMITED- too many ingest requests; aRetry-Afterheader indicates when to retry.QUOTA_EXCEEDED- monthly request limit reached; upgrade your plan to continue ingesting.PAYLOAD_TOO_LARGE(413) /BATCH_TOO_LARGE- the batch exceeded size limits.
To reduce ingest volume under heavy traffic, lower
telemetry.sampleRate. Threats are always reported at 100%; only normal request events are sampled. See SDK configuration.