Limits
What your plan holds, the fair-use limits every workspace shares, and the rate limits.
A workspace has three kinds of limit:
- Your plan: devices a month, members and, on Hobby, passes. The Usage card on the Overview shows them.
- Fair use: far above what a workspace uses. They keep the services every workspace shares up when a script or a loop runs away. The Usage card shows one once 80% of it is spent, and the Wall's staff are told when one is reached.
- Rate limits: requests from one address, one key or one network. They are set to what a person does, not what a script does.
Configure → Plan shows the same, with the fee. The settings of your tools' own plans have ranges too, at the end of this page.
If a limit is in your way, write to hello@toolaby.app. Enterprise raises any of them for one workspace.
Your plan
| Hobby | Pro | |
|---|---|---|
| Devices a month, counted across the workspace's tools | 2,500 | 50,000 |
| Members, counting invitations not yet answered | 3 | 10 |
| Passes live at once: grants, CSV rows, free checkouts | 100 | no limit |
Plans covers the fee, what each plan includes and what counts as a pass.
Fair use
A day's limit is counted over the 24 hours from its first use. Once the Usage card shows it, its ⓘ says when it starts again.
| Each day or hour | Limit |
|---|---|
| Additions: grants, customers added by hand, CSV rows, sales imported | 20,000 a day per workspace, from the dashboard, the API, the command line and Import together; 20,000 a day across all the workspaces of one owner |
| Grants from the API and the command line | 1,000 a day per tool; bring more in with the tool's Import page |
| Customer lookups | 20,000 a day per workspace, all its keys together, and the same across all the workspaces of one owner: Retrieve a customer and List grants together |
| Customer lists read | 300,000 rows a day per workspace, the dashboard's Customers page and the API's list together, and the same across all the workspaces of one owner. A list reads its licences, subscriptions, grants, sign-ins and customers added, and the accounts and devices they name: some 8,000 rows for 2,000 customers, and it sets aside the most it could read before it reads |
| Sign-in links and address confirmations | 5 an hour to one address and 20 an hour to one inbox, from all workspaces together; 300 an hour per workspace, 60 of them from one network |
| Licence keys no payment sent: one resent, a free checkout's, a seat's from a free pass | 5 an hour to one address and 20 an hour to one inbox, as sign-in links; 200 a day per workspace. On Test every licence key counts, a payment there being a test card: 50 a day per workspace and 1,000 across Test |
| Notifications | 2,000 new sales, refunds, cancellations and disputes a day per workspace; a fact reported again counts once |
| Notification mails | 30 an hour to one member, and 1,000 a day from one workspace |
| Webhook events | 5,000 a day per workspace, examples aside; a fact reported again is sent and counted once |
| Example webhook events | 100 a day per workspace, from Send a test event and toolaby webhooks trigger together |
| Invitations | 20 a day per workspace, 40 a day per developer across workspaces; a revoked invitation still counts |
| Workspace exports | 3 a day for each owner, across their workspaces |
| Sizes | Limit |
|---|---|
| Tools per workspace | 50, bundles among them |
| Plans per tool | 40, retired ones among them |
| Features per tool | 40 |
| API keys per workspace | 20 |
| Webhook endpoints | 10 per workspace |
| Origins under Your own pages | 5 |
| Seats per team licence or team subscription | 100 |
| Rows per CSV file | 10,000 |
| Brand images | 512 KB each |
| Customers in a list | the newest 2,000 licences, subscriptions, grants, sign-ins and customers added per tool, in the dashboard and the API alike. A customer beyond them opens by their address |
An addition is counted before it is written, so one the database then refuses still counts. A CSV row or a sale already imported is skipped and counts nothing. Past the day's 20,000, the API and the command line answer 429, the dashboard says so, and an import leaves the rest of the file out with the reason: send it again the next day. The Wall also stops all additions for a while when its database is nearly full, so that signing in, buying and checking licences keep working. The answer says so.
Past a day's customer lookups, Retrieve a customer answers 429. The customer list, and what webhooks tell you, still answer.
A sign-in link or address confirmation over its limit is not sent, and the page still says it was: a page that said no would tell anyone which addresses have accounts. An inbox is its address without a +tag, so test buyers at you+1@example.com and you+2@example.com share one inbox's 20. An invitation over its limit is refused with 429. A resent key over the limit is refused, with the reason. Receipts, and the key a payment bought on Live, have no limit. A key over its day is not mailed until the day starts again: a resend or a seat says so, and a free checkout's key waits for a resend.
A notification over its limit is not mailed; the sale, refund or cancellation is on the dashboard as always. A subscription set to cancel, back, and to cancel again within one day (UTC) is one cancellation, whatever else moves (its end, its period, its trial): one mail and one subscription.cancelled event.
Rate limits
| Limit | |
|---|---|
| API requests | 600 per minute per key; the customer list 30 pages a minute per workspace, all its keys together, up to 500 customers a page |
| Signing an extension in to an account | 60 an hour from one address and 10 an hour from one install |
| A new key's confirmation, asked for from the extension | 1 an hour to one address and 30 an hour from one network, within the same limits as sign-in links |
| Seats given | 30 an hour from one account, 200 a day from one network |
The buyer-facing endpoints (sign-in, licence activation, key resend, checkout) are limited per address and per key, checkout and key resend also per network, and answer 429. So are a signed-in buyer's own requests: what they hold, their devices, their seats, and the billing portal. None is shared by all the buyers of a tool. The command line's toolaby tools is limited per developer. A seat over its limit is refused, with the reason.
Your tools' plans
What you set on a plan under Pricing has a range:
| Range | |
|---|---|
| Devices | 1 to 10 per plan; a subscription plan may leave it open |
| Devices signed in, where nothing sets a limit | 20 per account and tool: on the tool's Free plan, a trial, a grant, or a plan that leaves devices open. The 21st signs the oldest out |
| Free-plan uses per device | up to 1,000 |
| Free trial | up to 365 days, on each subscription plan |