On multi-account servers, quotas cap how much disk space — and how many inodes — each account may use. Without them, one customer’s runaway backups can take every site down by filling the disk.
Quota monitoring is about the margins: accounts at 80–90% of their limit are about to start failing (uploads, mail, databases) and either need a cleanup or a bigger plan. Per-account quota columns make those candidates visible at a glance.
Frequently asked questions
What happens when an account hits its quota?
Writes start failing for that account only: uploads break, mail bounces, the CMS may error — while other accounts continue normally.
Do quotas limit inodes too?
They can. File-count (inode) quotas catch the “million tiny cache files” problem that byte quotas miss.