Limits

Every account has an allowance. Some parts of it are counted as they stand — how many projects exist right now — and some are metered over the calendar month, like build minutes and traffic. nesly enforces exactly the numbers below, and shows you the same ones.

What each plan allows

Your own numbers

nesly limits          # what your plan allows, and what you have used
nesly usage           # the raw meters: requests, traffic, build time, memory

The console shows the same thing on the account page, with a bar per allowance. Both read one endpoint on the platform, so what you see is what a request would be measured against.

When an allowance runs out

Your site keeps serving visitors. Nothing about a running application is touched by an allowance — not its traffic, not its database, not its custom domains. A site that is up stays up.

What stops is new work: a build is refused while the month's build minutes or traffic are spent, and creating a project, attaching a domain or inviting a person is refused once that count is at its limit. The refusal names the allowance and the number, so you never have to guess which one it was:

the free plan allows 3 projects and you are using 3 — upgrade to the pro plan on the billing page

Metered allowances reset when the calendar month does. Counted ones free up as soon as you delete a project, release a domain or remove a member.

We tell you first

When a metered allowance passes 80%, and again when it runs out, nesly e-mails the account owner and its admins. You will not discover a limit for the first time in a failed deployment. Those messages can be switched off on the account page; see your account.

Need more

Moving to Pro raises every allowance immediately — there is nothing to wait for and nothing to redeploy. If Pro is not enough, write to us: the numbers are configuration, not a law of nature.