Performance

Resource limits, isolation, and what happens if you run out

Last updated 14 July 2026

How your guaranteed CPU, memory, processes and disk work, why a neighbour cannot take them, and what happens when you hit the ceiling.

Every 8Deploy account runs in its own enforced slice of the server. That means:

This is enforced, not a promise. Nobody else on the machine can take your CPU or your memory, however busy or badly behaved they are. This is the difference between resources you were told about and resources you actually have.

What your plan gives you

What happens when you hit the ceiling

CPU. You do not get an error. Things simply take longer, because you are being held to your share. If your site is consistently at its CPU ceiling at busy times, that is a signal to move up a plan.

Memory. This one is hard. A process that asks for more memory than your account has will be stopped. In practice you see a failed build, a failed import, or an error page. The fix is either to make the process need less, or to move up a plan.

Storage. When you fill your quota, writes fail. That means uploads fail, and on a database-backed site it can mean the database cannot write either. Watch your storage in the panel, and add +10 GB for $3 a month if you need it, or move up a plan.

Processes. A runaway script cannot spawn processes forever and take the machine down with it. It is stopped at your limit.

Traffic is not a resource limit

Traffic is unmetered. We never charge per visitor and we never throttle you for being popular. A busy day costs you nothing extra.

How to know where you stand

Your dashboard shows your usage against your plan. The AI assistant can see it too, so you can simply ask it whether you are close to any limit.

Still stuck?

The assistant in your control panel can see your actual account and answer about your sites, your plan and your usage. For anything else, email [email protected] and a person will answer.