Access is invite-only during beta. Once invited, create a key to personalize these examples. Production sending requires a separate review.
How do capacity boosts work?
A 24-hour outbound allowance on top of the monthly plan.
A capacity boost raises a cluster's outbound hourly throttle and 24-hour cap for exactly 24 elapsed hours. The monthly plan, Stripe subscription, and cluster.plan stay the same.
base_emails_per_hour and base_emails_per_day are the plan. emails_per_hour and emails_per_day are the effective outbound caps: the greater of the plan and any boost whose starts_at has arrived and whose ends_at has not. Inbound receiving stays on the sum of live cluster plans.
Boosts do not add email credits. There is no per-email overage. When either effective cap is exhausted, REST still returns 429 {error: throttled}. SMTP delays further mail in the same hourly or 24-hour window. Already accepted mail is not deleted when a boost ends.
If the cluster sent more than the restored plan during the boost, further sends stay blocked until that hourly throttle or 24-hour cap has room again. Activating, expiring, or extending a boost does not reset usage.
A boost does not guarantee inbox placement or receiving-provider throughput. It only raises the purchased PostShiba hourly throttle and 24-hour allowance.
Expiry is a timestamp. A late background job cannot leave boosted capacity in place. Nodes also receive boost_starts_at and boost_ends_at, so a stale config still falls back to the plan when the window ends.
v1 SKUs:
| From | To | Price / 24 hours |
|---|---|---|
| Micro | Small | $2 |
| Small | Medium | $2 |
| Small | Large | $9 |
| Medium | Large | $7 |
Nano, XL, and Burst have no boost SKU. The server chooses the target, duration, and price from the SKU. The purchased rate and amount are stored on the boost so later catalog changes do not rewrite history.
You can start now or schedule a start between five minutes and 30 days from now. A cluster can have only one open boost. An active boost can be extended by another 24 hours at the same one-day price. Scheduled boosts can be cancelled and refunded before they start. Plan changes are blocked while a boost is pending, scheduled, or active.
Purchase is off until CAPACITY_BOOSTS_ENABLED=1. Set CAPACITY_BOOST_EXTENSIONS_ENABLED=0 to hide extensions. Operators can reject new purchases with CAPACITY_BOOSTS_INFRA_AVAILABLE=0 or cap targets with CAPACITY_BOOST_MAX_EMAILS_PER_HOUR (default 200,000).
Buying a boost does not change KYC, team suspension, sending suspension, domain verification, or abuse controls. Those gates still apply to every send.