Guide
Quotas, rate limits & data scrubbing
jentry's billing philosophy: quotas shed, they never bill. A traffic spike costs you dropped events, not money. Around that sit rate limits, spike protection and server-side PII scrubbing.
Plans & quotas
- Free: 5K events/mo · 1 project · 7-day retention. Team ($14): 100K · 10 projects · 30-day. Business ($49): 1M · unlimited projects · 90-day.
- Over quota, ingestion returns standard Retry-After / X-Sentry-Rate-Limits headers — SDKs back off automatically; nothing is billed.
- Retention pruning removes old events per plan; issues and rollup counts survive.
Rate limits & spike protection
- Per-project request-rate limits (plan-scaled burst) at the accept path; per-client-key custom limits are configurable.
- Per-issue spike protection: a flooding fingerprint keeps exact counts but caps stored raw events per minute — the stream stays usable during a retry storm.
PII scrubbing (server-side)
- Default sensitive-key redaction (passwords, tokens, secrets, auth headers) plus credit-card (Luhn-checked), SSN, bearer-token and PEM redaction in free text.
- Project settings add custom scrub fields, safe-list exceptions, and optional IP-address scrubbing.
- Inbound filters drop browser-extension noise, web crawlers, localhost and scanner probes before they count.
Everything above happens server-side on ingest — scrubbed data is never stored, and filters never silently eat real errors (each category is opt-in per project).
Try jentry free
Hosted error tracking & performance monitoring. Works with your Sentry SDKs — send your first event in minutes.