Plans & Limits

Plans overview

Every feature — webhook capture, inspection, replay, mock responses, CLI tunneling, SDK, and MCP server — works on both Free and Pro. The only feature exclusive to Pro is Teams (create teams, invite members, share endpoints).

Endpoints created by logged-in users (Free or Pro) never expire. They persist until you explicitly delete them from the dashboard, CLI, SDK, or API. Only ephemeral endpoints -- created without an account or explicitly marked ephemeral -- auto-delete after 12 hours.

How billing periods work

Guest — no account required. Ephemeral endpoints auto-delete after 12 hours along with all captured requests. Each ephemeral endpoint has a 25-request cap.

Free — billing periods activate lazily. Your 24-hour window starts when your first webhook request is captured, not when you sign up. Once the period expires, the counter resets and the next request starts a new 24-hour window.

Pro — 30-day rolling billing periods. The counter resets automatically at the end of each period. Canceled subscriptions remain active until the current period ends, then downgrade to Free.

Request quotas

Quotas limit how many webhook requests your endpoints can capture within a billing period. When your quota is exhausted, the receiver returns 429 Too Many Requests with a Retry-After header indicating when the quota resets.

Quotas are enforced atomically inside a single Postgres stored procedure — no race conditions, even under high concurrency.

Data retention

Captured requests are cleaned up automatically based on your plan:

• Free — requests older than 7 days are deleted daily at 01:30 UTC
• Pro — requests older than 31 days are deleted daily at 01:00 UTC
• Ephemeral — requests are deleted when the endpoint expires (12 hours after creation)

Deleted requests cannot be recovered. Export important requests as JSON or CSV from the dashboard before they expire.

Teams and shared endpoints

When you share an endpoint with a team, incoming webhooks count against your quota — not the team member viewing them. Data retention also follows the endpoint owner's plan.

Every team member must be on the Pro plan to access shared endpoints. If a member downgrades, they lose access to shared endpoints but remain in the team.

Rate limits

API routes enforce per-IP rate limits to prevent abuse. When a limit is exceeded, the API returns 429 Too Many Requests with a Retry-After header.

Other limits