{"id":6277,"date":"2026-09-16T10:43:11","date_gmt":"2026-09-16T07:43:11","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=6277"},"modified":"2026-09-16T10:43:12","modified_gmt":"2026-09-16T07:43:12","slug":"spanel-package-limits-explained","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/spanel-package-limits-explained\/","title":{"rendered":"The 14 Dials of an SPanel Package: What Each Limit Does and When to Use It"},"content":{"rendered":"\n

An SPanel package is a named hosting plan built from fourteen per-account limits: disk space, inodes, domains, email accounts, databases, hourly email rate, PHP workers, PHP priority, and the kernel-enforced ceilings on CPU, memory, disk throughput, disk IOPS, and processes – plus a feature set.<\/strong> You set each dial once, assign the package to an account, and SPanel holds the line. Every dial is included free on ScalaHosting managed VPS plans.<\/p>\n\n\n\n

Imagine this story.<\/p>\n\n\n\n

Ana runs a 60-account SPanel server out of France. She resells shared hosting to local shops, a dental clinic, and three small design agencies who each park a dozen client sites on her box. The first time she opened the package form in the Admin Interface, she counted fourteen fields and felt the usual question land: which of these actually matter, and what number am I supposed to type<\/em>? <\/p>\n\n\n\n

Most panel documentation explains how<\/em> to save a package. Almost none explains what each limit does when an account pushes against it, or what a sane starting value looks like. This is that field guide – one dial at a time.<\/p>\n\n\n\n

To put it simply, a package is a named bundle of fourteen account limits that SPanel applies in a single move and enforces below the panel – in the kernel, the filesystem, the mail server, and the PHP runtime.<\/p>\n\n\n\n

Hold onto that last point. None of these limits is honor-system validation in a web form. Each one is enforced by the part of the system that owns the resource, so the ceiling holds whether the account is driven through the panel, the SPanel HTTP API<\/a>, an SSH session, or your billing automation.<\/p>\n\n\n\n

The storage pair: disk quota and inodes<\/strong><\/h2>\n\n\n\n

Disk quota (MB)<\/strong> caps how much disk space the account may use. Inodes<\/strong> caps how many files and directories it may create. They go together because they catch two different failures. Quota stops the obvious one: a backup archive or an unpruned upload folder eating the drive. The inodes limit stops the subtle one: millions of tiny files (cache fragments, PHP session files, mail spam) exhausting the filesystem long before the gigabytes run out.<\/p>\n\n\n\n

At the ceiling:<\/em> both are real filesystem quotas, applied through the kernel’s quota machinery on ext4 and XFS. An account at quota gets “disk full” from the operating system itself when it tries to write, not a polite note from a web page. Existing data stays put; only new writes are refused. SPanel emails a warning to the account’s own contact address when usage crosses 95% of quota, so the wall rarely arrives as a surprise.<\/p>\n\n\n\n

A sensible start (plan-design judgment):<\/em> for a small single-site plan, 10 GB of quota paired with roughly 250,000 inodes keeps a normal WordPress or WooCommerce store comfortable. Raise both together as the plan grows; a quota with no inode ceiling is a quota with a back door.<\/p>\n\n\n\n

The creation counts: domains, email accounts, databases<\/strong><\/h2>\n\n\n\n

Maximum domains<\/strong>, maximum email accounts<\/strong>, and maximum databases<\/strong> define the shape<\/em> of a plan rather than its horsepower. A Starter plan might be one site, ten mailboxes, two databases; a Pro plan, unlimited of each.<\/p>\n\n\n\n

At the ceiling:<\/em> these are checked at creation time by the SPanel system scripts. An account at its domain ceiling is told so, clearly, the moment it tries to add another, in the panel and at the system level alike. <\/p>\n\n\n\n

One honest detail worth knowing<\/strong>: lowering an account’s database limit from ten to five does not delete five databases. Creation counts gate new growth; they never reach back and destroy data. The account simply can’t create the eleventh until it’s under the line again.<\/p>\n\n\n\n

A sensible start:<\/em> match the counts to the story you’re selling. If “one website” is the product, set domains to 1 and let mailboxes and databases breathe a little above what a single site needs.<\/p>\n\n\n\n

The email send rate<\/strong><\/h2>\n\n\n\n

Max hourly emails<\/strong> – the per-account outgoing-message cap – is the anti-spam and reputation dial, enforced by the Exim mail server’s own rate-limiting rather than by anything in the panel.<\/p>\n\n\n\n

At the ceiling:<\/em> a hijacked contact form or a compromised plugin hits the hourly cap and stops, instead of pumping thousands of messages from your shared IP and getting it blacklisted. The limit can target a single mailbox or a single domain when one sender is the problem, and a server-wide Email Sending Limit<\/strong>, under Server Settings<\/em> \u2192 Email Settings<\/em>, is available as a backstop. Every day, SPanel scans the previous day’s mail log and emails you a summary of any accounts that went over – the compromise canary you didn’t have to build. We go deeper on this in our piece on catching spam before it torches your server IP<\/a>.<\/p>\n\n\n\n

A sensible start:<\/em> a few hundred messages an hour covers legitimate transactional mail for most small sites. If a client genuinely sends newsletters, route them to a dedicated sending service rather than lifting the cap to thousands.<\/p>\n\n\n\n

The PHP pair: workers and priority<\/strong><\/h2>\n\n\n\n

Maximum PHP-FPM workers<\/strong> sets how many PHP requests an account can process at once. PHP priority<\/strong> – high, medium, or low – decides whose PHP gets the CPU first when the server is contended.<\/p>\n\n\n\n

At the ceiling:<\/em> the worker ceiling is written into the account’s own PHP-FPM pool (and the OpenLiteSpeed equivalent on that stack), so it’s the PHP runtime itself that declines to spawn worker sixteen when the plan says fifteen. Priority is applied as real operating-system process priority, so a high-priority plan’s PHP genuinely runs ahead of a low-priority plan’s under load. There’s also a quick admin action – Change Limits<\/strong> on the account, reached from its row’s Actions menu – to clamp a single account’s workers on the spot, for the account that’s overloading a shared box this minute.<\/p>\n\n\n\n

A sensible start:<\/em> the default worker ceiling is 15 per account, which suits most plans; leave priority at medium and reserve high for premium tiers, so the ladder means something.<\/p>\n\n\n\n

Pull quote:<\/strong> “The panel is where you set a limit. The kernel, the filesystem, the mail server, and the PHP runtime are where it actually holds.”<\/p>\n\n\n\n

Want to follow along on a live panel?<\/strong> Every dial described here ships with SPanel on ScalaHosting’s managed VPS plans – no separate license, no per-account add-on. If you already run a managed VPS, the package form is sitting in your Admin Interface right now, ready to open alongside this guide.<\/p>\n\n\n\n

The performance four: CPU, memory, disk throughput, and IOPS<\/strong><\/h2>\n\n\n\n

These are the kernel-enforced ceilings, and they’re the reason per-account limiting used to mean buying a separate, paid operating-system layer. SPanel enforces them natively with Linux control groups – cgroups v2<\/a>, the same mechanism the entire container world is built on. A small SPanel service called cpm sweeps once per second and places every limited account’s processes into that account’s control group. New process, about a second, contained.<\/p>\n\n\n\n

CPU limit<\/strong> is a percentage where 100 equals one full core, 50 is half a core, and 200 is two cores. It is a share of a core, not a share of the whole server, and that one sentence prevents the most common misreading of this dial. At the ceiling:<\/em> the account is throttled, not killed. Its processes simply receive no more than their share of CPU time; the site slows under its own excess load while every other account keeps full speed. Nothing crashes, nothing is lost.<\/p>\n\n\n\n

Memory limit (MB)<\/strong> caps the account’s RAM. At the ceiling:<\/em> the kernel reclaims memory inside that account’s group only<\/em>, in the worst case ending the account’s own offending process, and the rest of the server never feels it. SPanel’s health monitoring even tells the two apart: a true server-wide out-of-memory event raises an admin alert, while a per-account containment event is recognized as a limit doing its job, not an emergency.<\/p>\n\n\n\n

Disk throughput (MB\/s)<\/strong> and IOPS<\/strong> put each account’s storage traffic in its own lane: throughput is the volume of data moving to and from the disk, IOPS is the count of separate operations. This is storage traffic, not network traffic; ScalaHosting’s managed VPS plans come with unmetered network traffic, and these dials have nothing to do with it. At the ceiling:<\/em> over-limit reads and writes are queued, not failed. The heavy account’s nightly backup takes longer; everyone else’s latency stays flat.<\/p>\n\n\n\n

There’s a server-wide burst mode<\/strong> sitting over all four. With it on, enforcement engages only when server load reaches the core count (genuine pressure), so accounts can use idle capacity on a quiet server and get strict fair shares on a busy one, within about a second of the pressure starting. It’s load-aware generosity with a fairness trigger, and it earns its own article on hosting limits that stand down when the server is idle.<\/p>\n\n\n\n

A sensible start:<\/em> for a standard small-business plan, 100 CPU (one full core), 1 GB of memory, and modest disk throughput and IOPS lanes give a site real headroom without letting any single account monopolize the box. Size memory with care, because too tight a ceiling reclaims the account’s own work mid-task. Pair this dial with honest sizing rather than treating smaller as better.<\/p>\n\n\n\n

The process ceiling<\/strong><\/h2>\n\n\n\n

Maximum Total Processes<\/strong> caps how many simultaneous processes the account may run. It’s fork-bomb insurance and general containment in one number.<\/p>\n\n\n\n

At the ceiling:<\/em> process N+1 simply cannot start. A fork bomb, malicious or a buggy script gone sideways, hits the cap and fizzles instead of exhausting the server’s process table and taking everyone down with it. This is the failure that’s catastrophic without a limit and a complete non-event with one.<\/p>\n\n\n\n

A sensible start:<\/em> a few hundred processes covers a busy site with room to spare; the goal is a ceiling high enough that legitimate traffic never touches it and low enough that a runaway can’t consume the whole server.<\/p>\n\n\n\n

The feature set<\/strong><\/h2>\n\n\n\n

The fourteenth dial isn’t a number. The feature set<\/strong> decides which SPanel User Interface tools accounts on this package can use. The default is everything.<\/p>\n\n\n\n

At the ceiling:<\/em> there isn’t one in the throttling sense. A feature that’s off the set simply isn’t shown to the account. What it buys you is product design. A curated subset turns a budget tier into a genuinely simpler<\/em> product rather than merely a smaller one, and lets a premium tier look visibly richer. Selling “fewer, clearer tools” is a real plan differentiator, not a downgrade.<\/p>\n\n\n\n

The fourteen dials at a glance<\/strong><\/h2>\n\n\n\n

The values below are illustrative plan-design judgment for a small single-site plan, not product defaults – tune them to what you actually sell.<\/p>\n\n\n\n

Dial<\/td>What it limits<\/td>At the ceiling<\/td>A sensible start<\/td><\/tr>
Disk quota<\/td>Disk space (MB)<\/td>“Disk full” on new writes<\/td>10 GB<\/td><\/tr>
Inodes<\/td>File\/directory count<\/td>New files refused<\/td>~250,000<\/td><\/tr>
Max domains<\/td>Sites the account can add<\/td>Creation declined<\/td>1<\/td><\/tr>
Max email accounts<\/td>Mailboxes<\/td>Creation declined<\/td>10<\/td><\/tr>
Max databases<\/td>Databases<\/td>Creation declined<\/td>2<\/td><\/tr>
Hourly email<\/td>Outgoing messages\/hour<\/td>Further sends held by Exim<\/td>a few hundred<\/td><\/tr>
PHP workers<\/td>Simultaneous PHP requests<\/td>Worker not spawned<\/td>15 (default)<\/td><\/tr>
PHP priority<\/td>CPU order under load<\/td>Lower priority waits<\/td>medium<\/td><\/tr>
CPU<\/td>Share of a core (100 = one core)<\/td>Throttled, not killed<\/td>100<\/td><\/tr>
Memory<\/td>RAM (MB)<\/td>Reclaimed inside the account<\/td>1 GB<\/td><\/tr>
Disk throughput<\/td>Storage MB\/s<\/td>Queued, not failed<\/td>modest lane<\/td><\/tr>
IOPS<\/td>Disk operations\/sec<\/td>Queued, not failed<\/td>modest lane<\/td><\/tr>
Processes<\/td>Simultaneous processes<\/td>The fork fails<\/td>a few hundred<\/td><\/tr>
Feature set<\/td>Which UI tools show<\/td>Tool hidden from account<\/td>everything<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Any dial can be left unlimited; a package only enforces what you set. And every dial exists in two forms: as part of a named package, and as a per-account custom value set through Use Custom Limits<\/strong> in the account’s Change Limits<\/strong> action – the clean home for one-off deals that shouldn’t pollute your plan catalog.<\/p>\n\n\n\n

Demo flow: reading the package form, dial by dial<\/strong><\/h2>\n\n\n\n

These steps walk the Admin Interface screens where the fourteen dials live and where you watch them take effect.<\/p>\n\n\n\n

    \n
  1. From the Admin Interface<\/strong>, open Packages<\/strong>. The list shows every package you’ve defined, with its key limits at a glance – the columns run Name, Quota, Domains, CPU, RAM, Max PHP, Priority,<\/em> and Owner<\/em>.<\/li>\n<\/ol>\n\n\n\n
    \"The<\/figure>\n\n\n\n
      \n
    1. Click Create a New Package<\/strong> (or edit an existing one). The Basic Limits<\/strong> tab holds the storage pair and the creation counts – Disk Space Limit, Inodes Limit, Addon Domains Limit, Email Accounts Limit, MySQL Databases Limit – plus Max hourly emails<\/strong>.<\/li>\n<\/ol>\n\n\n\n
      \"The<\/figure>\n\n\n\n
        \n
      1. Open the Advanced Limits<\/strong> tab. Here are the kernel-enforced dials – CPU Limit, Memory Limit, Storage Transfer Rate (disk throughput), IOPS Limit, and Maximum Total Processes – alongside Maximum PHP-FPM Processes (the PHP workers) and the PHP-FPM Priority select.<\/li>\n<\/ol>\n\n\n\n
        \"The<\/figure>\n\n\n\n
          \n
        1. Open Features Access<\/strong> – the feature-set selector – to choose which User Interface tools this package exposes to its accounts.<\/li>\n<\/ol>\n\n\n\n
          \"The<\/figure>\n\n\n\n
            \n
          1. Save, then open Manage Accounts<\/strong> (the List Accounts screen). Each account row shows its Inodes used and its assigned Package; expand a row to see Disk Usage against its Quota ceiling.<\/li>\n<\/ol>\n\n\n\n
            \"The<\/figure>\n\n\n\n

            To watch a runaway account get caught instead of catching it by hand, the same dials drive the containment story in how one bad plugin used to take down twenty good sites, and the full hands-on setup lives in per-account limits without a CloudLinux license.<\/p>\n\n\n\n

            See it on a real server.<\/strong> Every dial in this guide ships on every ScalaHosting managed VPS at no extra cost – no per-account fees, no premium tier. Start a ScalaHosting trial to open the package form yourself, or vote for what we build next on the Cloud Democracy board at features.spanel.io<\/a>.<\/p>\n\n\n\n

            FAQ<\/strong><\/h2>\n\n\n\n

            Q:<\/strong> What resource limits can I set per hosting account on SPanel?<\/strong> <\/p>\n\n\n\n

            A:<\/strong> Disk space and inodes; the number of domains, email accounts, and databases; outgoing emails per hour; PHP workers and priority; and kernel-enforced ceilings on CPU, memory, disk throughput, IOPS, and simultaneous processes. Any of them can be left unlimited.<\/p>\n\n\n\n

            Q:<\/strong> What does a CPU limit of 100 mean?<\/strong> <\/p>\n\n\n\n

            A:<\/strong> One full CPU core. 50 is half a core; 200 is two cores. The percentage is of a core, not of the whole server.<\/p>\n\n\n\n

            Q:<\/strong> Do I need CloudLinux to limit CPU and RAM per account?<\/strong> <\/p>\n\n\n\n

            A:<\/strong> No. SPanel enforces CPU, memory, disk throughput, IOPS, and process limits natively through the Linux kernel’s control groups (cgroups v2), with no separate OS layer or license. To be precise about scope: this is resource limiting, not a claim of CageFS-style per-account filesystem virtualization – account isolation comes from standard Linux users and permissions plus the SShield security stack.<\/p>\n\n\n\n

            Q:<\/strong> What happens when an account hits its memory limit?<\/strong> <\/p>\n\n\n\n

            A:<\/strong> The kernel reclaims memory inside that account’s group only, in the worst case ending the account’s own offending process. The rest of the server keeps running, and SPanel treats a server-wide memory emergency as a separate event with its own alert.<\/p>\n\n\n\n

            Q:<\/strong> Is the disk throughput limit my internet bandwidth?<\/strong> <\/p>\n\n\n\n

            A:<\/strong> No. The MB\/s dial governs storage traffic – how fast the account reads and writes files on disk. It has nothing to do with network traffic, and ScalaHosting’s managed VPS plans come with unmetered network traffic.<\/p>\n\n\n\n

            Q:<\/strong> If I lower an account’s database limit, are databases deleted?<\/strong> <\/p>\n\n\n\n

            A:<\/strong> No. Creation counts gate new creation; they never delete existing data. The account just can’t create more until it’s back under the ceiling.<\/p>\n\n\n\n

            Q:<\/strong> How fast do the limits take effect?<\/strong><\/p>\n\n\n\n

            A:<\/strong> The cpm enforcement service sweeps every second, so a new process is confined within about a second. Plan assignments and limit changes apply immediately and in place, with no migration.<\/p>\n\n\n\n

            Q:<\/strong> Can I sell plans that differ in features, not just size?<\/strong> <\/p>\n\n\n\n

            A:<\/strong> Yes. The feature set decides which User Interface tools a package exposes. The default is everything; a curated subset makes a budget tier a genuinely simpler product.<\/p>\n\n\n\n