Plans and limits
Four plans: Deckhand is free, and Bosun, First Mate and Captain add capacity above it. This page is the single source for what each one includes. Anywhere else a limit comes up, it links here. The table is generated from the same plan definitions the app enforces, so it cannot drift from them.
The table
 Deckhand |  Bosun |  First Mate |  Captain | |
|---|---|---|---|---|
| Price | Free | $9 a month, billed monthly only | $29 a month, or $290 a year | $99 a month, or $990 a year |
| Projects | 1 | 2 | 5 | 10 |
| Endpoints per project | 2 | 3 | 5 | 15 |
| Captures per month | 3,000 (about 100 a day) | 5,000 (about 167 a day) | 25,000 (about 834 a day) | 250,000 (about 8,334 a day) |
| Burst limit per endpoint | 20 a minute | 30 a minute | 60 a minute | 120 a minute |
| Retention | 3 days | 7 days | 20 days | 45 days |
| Maximum payload | 64 KB | 256 KB | 1 MB | 10 MB |
| Replay response body | First 4 KB stored | Full body stored | Full body stored | Full body stored |
| Secrets per project | 2 | 3 | 6 | 30 |
| Replay targets per project | 1 | 2 | 3 | 10 |
| Collections | Not included | 2 | 3 | 10 |
| Captures per collection | Not included | 5 | 10 | 50 |
| Transformations | 1 | 2 | 3 | 10 |
| Bindings | 1 | 2 | 3 | 10 |
| Steps per transformation | 1 | 1 | 1 | 5 |
| Watches per endpoint | 3 | 3 | 5 | 10 |
| Envoys | 5 | 10 | 15 | 20 |
Deckhand
Bosun
First Mate
CaptainThe daily figure is derived from the monthly allowance, not set separately: one thirtieth of the month, rounded up. Watches are the one limit that stays bounded on every plan, because a watch is evaluated on every capture that arrives.
Features that start at a plan
Most of the ladder is counted, not switched: every plan has the same features with bigger numbers. Four things are switched on at a plan rather than counted.
| Feature | From |
|---|---|
| Batch replay (many captures to many targets in one action) | Bosun |
| Running a collection or a sequential replay | Bosun |
| Run until 200 (retry a collection until every item succeeds) | First Mate |
| Locking a capture so retention never removes it | Captain |
What the plan names mean
The ladder is a crew rather than a set of tiers, and the names carry the shape: a Deckhand is learning the ship, a Bosun keeps the working gear in order, a First Mate runs a watch, and a Captain answers for the whole vessel. Which plan you want follows from how much of the ship you are responsible for, not from a feature checklist.
What happens at a limit
- Captures. When a project reaches its daily cap, the next ten percent of requests are stored as rejected captures, so you can see in the dashboard that you hit it, and the sender gets a 404. Past that, and once the monthly allowance is spent, the capture URL answers 404 and stores nothing until the window resets. Most providers treat a 404 as a failed delivery and retry on their own schedule.
- Bursts. When an endpoint receives more than its burst limit in one minute, the excess is stored as rejected captures and the sender gets a 429. Providers back off on 429 and retry once the minute passes.
- Retention. Captures older than the retention window are deleted by a background job that runs hourly. A capture that belongs to a collection is exempt, so a regression scenario outlives the window, and so is a capture you have locked on Captain.
- Everything else. Creating a project, endpoint, secret, target, collection, transformation, binding or watch past its limit is refused with a plan-limit error that names the limit. Nothing you already have is removed.
Changing plan
Plans are managed on the pricing page and in the app under Billing. The pricing page also carries a plan-fit calculator that shows which plans hold a given set of recipes, resource by resource.