Plans and limits

Stormedo has a Free plan for evaluation and smaller workloads and a fixed-price Pro plan for production workloads. Prices are in USD.

Allowance	Free	Pro
Monthly price	$0	$20
Accepted requests per month	10,000	1,000,000
Recurring schedules, including paused	3	100
Completed request history	7 days	30 days
Maximum delivery payload	256 KiB	256 KiB
Automatic delivery retries	Included	Included
Destination signing	Included	Included

Pro is billed at $20 per month. Stormedo does not automatically bill usage overages.

What counts as a request

One newly accepted request to one destination counts once. This includes:

• An immediate request
• A delayed request
• Each item in a batch
• Each recurring schedule occurrence
• A manual replay

Automatic delivery retries do not consume additional request allowance. Attempts belong to the history of the original accepted request.

The 256 KiB limit applies to each delivered request body. A batch accepts up to 100 items and has a separate 32 MiB limit for the complete incoming HTTP body.

Monthly request limit

The allowance is shared by all projects in the workspace. When the monthly limit has been reached:

• New sends, batches, and replays return 429 with the plan_limit_exceeded error code.
• A recurring occurrence is skipped instead of creating new work.
• The schedule remains active so later occurrences can resume when capacity is available.

Free allowance follows calendar months and resets at 00:00 UTC on the first day of the next month. Pro allowance follows the workspace’s subscription period. If paid access ends partway through a month, the effective Free period starts when paid access ends and runs to the next calendar-month boundary. The dashboard billing summary shows the effective period, usage, and limits; plan-limit errors can include resets_at. Use that actual boundary instead of assuming the workspace resets on your local midnight.

Schedule limit

The schedule allowance is shared across the workspace. Creating another schedule after the plan limit has been reached returns 429 with plan_limit_exceeded.

Delete an unused schedule or change plans before creating another one. Paused schedules remain active resources and still count toward the allowance.

History retention

Completed request and attempt history remains queryable for the plan’s retention window. Requests still in progress are not hidden because they age beyond that window.

Use the request list response to read the effective history_retention_days, cutoff time, and whether older completed history is hidden.

Plan scope

Billing and allowances belong to the workspace, not an individual user, project, or API key. All projects in one workspace share the same plan and limits.

History retention describes query visibility, not a promise of physical payload deletion. The public request API omits bodies; schedule detail returns its configured JSON body.