What is a Resource Usage Policy?
In a nutshell, it’s a system we have in place that allows all of our shared hosting clients to get along with one another, while still enjoying the benefits of pooled resources in the form of a shared server. While these limits are not always set in stone, this is generally what we stick to. After years and years of testing and optimization, these are the guidelines that generally work out best for everybody. Please note that it is still entirely possible that some other activity not covered here can be considered resource abuse, and this is decided on at the sole discretion of Certified Hosting.
What is the real purpose of these policies?
These guidelines are in place to protect all our clients from low quality service. Providing a high quality always online server is our goal, but we can’t do that if even one person decides to take advantage of the situation and eat up all the server resources. Generally, only 1 in 200 accounts will ever have an issue and the vast majority of those users are able to get it resolved without much of a problem, but it’s still important to have the policies in place and for our users to be aware of them.
At what point are these policies enforced?
Many of these specific limits are what is considered a “soft” limit, which means that often times you’re able to be at or even go past the limits laid out here. This depends on the situation of course, but as long as any given account is not constantly using more than it’s fair share, there usually isn’t a problem. If it is, we do everything we can to give as much notice about the problem as possible, although we usually require that a user at least respond to any such notice within 48 hours. However, should an account begin to crash the server or otherwise make things so slow that everyone else is affected, we will have no choice but to suspend the account and work with the user to figure out the best way forward with their account.
If you have any questions about any of this, please contact us and we’ll be happy to elaborate or advise you as needed.
General Account Limitations
An account may not do any of the following:
Generally, processes are factored on a whole account basis, and includes things like php scripts, crons, shell commands or any other method your user might use to generate processes. Although there is some flexibility these are the general limitations in place:
Files and Directories Limitations
The total number of inodes in an account may not exceed 250,000. Every singe file, including web pages, images, emails, script files, directories, etc. on your account uses up one inode. Although not part of a specific policy, you’ll want to avoid having more
than 2000 files in a single directory as the FTP server will not list more than this number.
A cron job should not execute more frequently than once every 15 minutes.
We do not allow our shared hosting accounts to be used for the purposes of backups. This means you may not simply upload copies of all your personal photos or music collection or anything like that. All data on your shared account MUST be used for the purposes of an active website, at all times. This means if you upload a photo, you must link to that photo in some way via your website. Same with any file. We also do not allow you to store more than one account backup on the server at a time. We highly encourage you to frequently generate and download backups of your account, but it’s important to remove them from the server when you are done.
Are these all of your policies?
No. We have a few more terms and conditions that must be agreed to before you sign up with us and use our servers or services. We have simply outlined the most important ones and the most common ones that come up for the sake of making sure everyone is aware of the important stuff.
You can (and should) go over our full Terms here:
More info about our unlimited policy here:
And our mail policy here:
The FULL range of all our policies is available here: