Every plan captures every byte and checks every signature. What you buy going up is room: how long the record lives, how much of it you can pin and how many people and agents work against it.

Free.
1 project, 2 endpoints, a three-day capture window, 64KB payloads.
Your first pipe and your first receipt.

$9 a month.
A seven-day capture window, 256KB payloads.
One developer who wants the record to outlive the week.

$29 a month or $290 a year.
A 20-day capture window, 1MB payloads.
A team running several pipes against shared endpoints.

$99 a month or $990 a year.
A 45-day capture window plus capture locks, 10MB payloads.
For records that have to survive retention outright.
The record aged out.
Three days is enough to test a pipe. It is not enough to answer what the agent did last Tuesday.
A room outgrew its window.
More people joined.
Each collaborator your account counts is an envoy. Each place they sit in a room, with its own end date, is a seat. You pay for the first, not the second.
One pipe became several.
You needed the whole answer.
Bigger payloads, response bodies kept intact.
Something had to be permanent.
Captain locks.
Recipes consume plan resources when installed. This example evaluates the Slack posting recipe against every plan, live. Each resource links to the glossary.
The calculator tells you whether a recipe runs on a plan. For anything that accumulates, ask the second question: whether the plan sustains it. A team room runs free on Deckhand. It will not hold a three-week conversation; the window closes first. Runs free for a short-lived room. Upgrade to keep the log.
For a worked example, project tracking is the deepest shelf in the catalog.
Recipes install through your AI agent. Point it at the FlurryPORT MCP server (npx flurryport mcp) and ask for the ones you picked.
New words? The glossary defines every term on this page.
Every plan includes the full capture and replay engine with AES-256-GCM envelope encryption and automatic key rotation, the free one included.
Does my agent's credential ever reach the model?
No. It lives in the secret store, goes on server-side at delivery and gets scrubbed from the stored response if a destination echoes it back. Every plan works this way, Deckhand included. More in endpoint security.
What do paid plans unlock?
Room, mostly. A longer window, more endpoints and targets, more transformations and project secrets. On Captain, capture locks. Signature validation and encryption at rest are on every plan, free ones included.
Can I keep a capture past its window?
Save it to a collection and it outlives retention; lock it on Captain and cleanup cannot remove it at all. A capture's content is never modified once it lands, on any plan. What you are buying is persistence.