Limits per plan
- boat counts starts over the last 60 seconds, 60 minutes and 24 hours. There is no reset date.
- A stopped sandbox does not count against “at once”.
- For organizations, read Seats, limits and caps.
- To see what you have left, run
boat limits.
Extra starts
A start above your included number is an extra start. It needs a first payment.- The prices apply per minute, hour and day. A start pays the highest of the three.
- The maximum per minute is 3 times, not 6.
nextStartAt. Only runs-on: boat jobs can wait.
Extra starts on your invoice
- It is off by default. A trial, a past-due account, or a plan set to end cannot use it.
- The cap per seat per month is $80 on the $20 plan, $400 on the $100 plan, and $1,500 above.
- If your plan ends first, your wallet pays what is left and can go negative.
- In a script, add
--yesto accept the terms.
In the API
GET /limits returns:
Other limits
For the command limits, read Background commands and Command history and logs.
Errors and what to do
Retry rules
- Every
429sends aRetry-Afterheader: the wait in seconds. The body also has the wait:retryAfterSecondsonrate_limited,retryAfteron an IP limit. A503hasretryAfterSeconds. - Every API answer carries your IP limit in two headers (IETF RateLimit fields).
ris the number of requests you have left.tis the seconds until the window resets:
- Create, resume and fork answers also carry your start limits, one policy per window:
starts-minute(w=60),starts-hour(w=3600) andstarts-day(w=86400).RateLimitreports the start window with the fewest starts left:"<policy>";r=<starts left>;t=<seconds>. An account with no start limit gets no start policies. - A start that fails with
rate_limiteddoes not count as a start. - Send an
Idempotency-Keyheader on create and fork. A retry with the same key never makes a second sandbox or spends a second start. - The CLI does not retry. It prints the limit message and exits with an error.