ūüĒ•Elevate Your Website with Tailored Cloud Hosting!

Resource Usage Policies

Last Updated: Sunday, February 11, 2024

What are Resource Usage Policies?

Resource Usage Policies, particularly in a hosting environment, are critical guidelines set to manage and regulate how individual users consume server resources. These policies are designed to prevent what is known as the “tragedy of the commons” in a server context, where unrestricted use by one or a few users can detrimentally affect the overall server performance for everyone else.

The purpose of these policies is to maintain high service quality and ensure fair resource allocation among all users. By setting these limits, hosting providers like MyProjectHost aim to protect their customers from poor service quality caused by excessive resource consumption by a few users.

Key aspects of MyProjectHost’s Resource Usage Policies include:

  1. General Content & Service Restrictions: These policies dictate what kind of content and services are permissible on their servers. Important restrictions include:

    • Backups: Servers are not meant to be used as a backup/storage system.
    • Reselling: Reselling is not allowed on specific hosting plans like Web Hosting and WordPress Hosting. A separate reseller hosting plan is required for this purpose.
    • Adult Content: Pornography is strictly prohibited. However, adult-oriented content that’s legal in the USA may be permissible.
    • Chat Applications: Interactive chat applications, including those based on PHP, Perl, CGI, Python, Ruby, etc., along with IRC and IRC bots, are prohibited.
    • Web Applications & Scripts: Outdated web applications prone to exploitation are not allowed. Regular updates and security measures, like CAPTCHA for forums and comment systems, are required to prevent spam and abuse.
    • SEO Farms & Other Prohibited Uses: SEO farms, banner rotation services, link exchange networks, file/document/data storage services, off-site media storage, and the operation of public mirror sites are among the activities not allowed.
  2. Prohibition of Resource-Intensive Activities: Activities that create a significant load on servers, such as operating gaming servers, web spiders, indexers, bit torrent applications, and file-sharing/peer-to-peer activities, are forbidden.

  3. Enforcement and Consequences: Violations of these policies can lead to immediate shutdown of the offending service and potentially result in account suspension or termination.

  4. Consultation for Ambiguities: If users are unsure whether their content or activities might violate these policies, they are advised to consult with MyProjectHost’s Abuse Department for clarification.

These policies are put in place not only to protect the hosting service provider’s infrastructure but also to ensure a reliable and consistent hosting experience for all users on the platform. They highlight the balance between offering flexible and powerful hosting capabilities while maintaining a fair and optimal operating environment.

Resource Usage Restrictions

Utilizing the CloudLinux system, MyProjectHost implements resource usage restrictions for shared hosting accounts to maintain optimum performance. Our shared hosting packages are configured with specific CloudLinux resource limits as follows:

  1. CPU Speed Limit: This is relative to a single core’s capacity. Our shared hosting packages offer CPU speed starting from 100% (equivalent to 1 CPU core).

  2. Physical Memory Limit: This encompasses both shared memory and disk cache. The starting memory allocation for our hosting packages is 1024MB.

  3. IO Throughput: This metric covers both read and write operations, with our hosting packages providing a limit of 10MB per second.

  4. IOPS (Input/Output Operations Per Second): This restricts the total number of read/write operations per second. Our shared hosting packages impose a limit of 1024 operations per second.

  5. EP (Entry Processes): This indicates the maximum number of concurrent connections to dynamic scripts, including SSH and cron jobs. Our packages begin with a limit of 10 entry processes.

  6. NPROC (Number of Processes): This is the maximum number of processes within the LVE. Our shared hosting accounts are capped at 100 processes.

For a comprehensive understanding of CloudLinux limits, detailed technical information is available on the CloudLinux Documentation website.

These limits vary based on the chosen hosting package and the recommended resource level. The packages include:

Shared Hosting Plans:

  1. Basic: Maximum 100% CPU resources, 1024 MB memory; IO: 10 MB/s; IOPS: 1024; up to 10 entry processes.
  2. Pro: Maximum 200% CPU resources, 2048 MB memory; IO: 10 MB/s; IOPS: 1024; up to 15 entry processes.
  3. Turbo: Maximum 300% CPU resources, 3072 MB memory; IO: 10 MB/s; IOPS: 1024; up to 30 entry processes.

Cloud Hosting Plans:

  1. Cloud Starter: Same limits as Shared Hosting Starter plan.
  2. Cloud Pro: Same limits as Shared Hosting Pro plan.
  3. Cloud Turbo: Same limits as Shared Hosting Turbo plan.

Resource Usage Enforcement

Adherence to these limits is crucial. Accounts impacting the overall performance of a server will be subject to enforcement policies. Customers using the shared hosting service at MyProjectHost receive detailed, up-to-date statistics for their CPU and Memory usage via the cPanel. It is the customer’s responsibility to maintain their account and installed software efficiently to ensure optimal performance for all users sharing the resource.

Violations of these Resource Usage Policies will be addressed with notices given 48 hours, 5 days, or 10 days in advance, based on the violation’s severity. Accounts exceeding consumption limits 100 times within 24 hours will be contacted by our technical department for website optimization or to transition to a more suitable plan.

MyProjectHost reserves the right, as per our Terms of Service, to modify account resource usage limits in case of severe issues, in compliance with Indian law. For any queries or assistance, please reach out to us at support@myprojecthost.com.


  • ¬†Simultaneous Apache connections may not exceed 50 from one individual source at any given time.
  • ¬†Web processes should not fork or spawn subprocesses.

Email and Mailing Lists

Unsolicited Bulk/Commercial Email / SPAM

The use of myprojecthost.com servers and networks to transmit unsolicited bulk/commercial email (also known as spam) is strictly forbidden. Under no circumstance is the transmission of spam acceptable or tolerated.

The transmission of spam from our servers and networks can cause irreparable monetary and reputation damage. All damages caused by spamming will be prosecuted to the fullest extent of the law.

Any client caught explicitly spamming from our servers or networks will have their account immediately terminated & without notice.

To maintain the integrity and reliability of our email services, we have established the following sending limits:

Hourly limit: Users are limited to sending a maximum of 300 emails per domain per hour.
Daily limit: Users are limited to sending a maximum of 3,000 emails per domain per day.
Weekly limit: Users are limited to sending a maximum of 10,000 emails per domain per week.

 Processes should not send outbound mail to more than 25 recipients at any given time.

 The maximum number of members per mailing list is 1,500.

 POP connections are limited to 60 per hour.

 SMTP connections (outbound email connections) are limited to 500 per hour per server account.

 Mailing lists larger than 1,500 will require a VPS service from us. Dividing one list into smaller parts to get around this limit is not allowed.

Any mailing list must be throttled so that it sends an email every 6 seconds at the very minimum. If the mailing list software you are using doesn’t support throttling you must use something else. We do this as this keeps the server load from going very high and causing problems for other users. If you don’t do this you will be suspended.

 We do not allow you to send to a mailing list you were given or that you bought. This is spamming and we have zero tolerance for this.

 Any mailing list must comply with the rules set forth by the United States of America and can be found at http://business.ftc.gov/documents/bus61-can-spam-act-compliance-guide-business.

 No Direct SMTP mailing system scripts are permitted. Mail should be relayed through the local MTA.

These limits are in place to prevent excessive use of resources and to ensure fair usage across all users. Failure to adhere to these limits may result in temporary suspension of email services.

Cron Jobs

  • ¬†A cron job should not execute more frequently than once every 15 minutes on a shared hosting service. If set for a shorter time, our system will automatically reset it to 15 minutes without prior notice. For execution frequencies lower than 15 minutes, we offer VPS Hosting services.


  • ¬†Our servers should not be used as an SSH bounce point to other servers/networks.
  • You may not use the Unix ‚Äúfind‚ÄĚ command recursively on directories more than 5 levels deep.

Dedicated IP Addresses

  • ¬†Dedicated IP Addresses require valid justification.
  • ¬†MyProjectHost has the right to decline any dedicated IP requests without any explanation.

Failure To Comply With Policy

Failure to fully comply with these terms is grounds for account suspension and/or termination.

We reserve the right to remove any account without prior notice.


The examples listed herein are a guide and may not be an exhaustive list. If you have a question on whether or not your content is in violation, please create a ticket with our Support Department for clarification.

Let us help you grow

Laoreet scelerisque euismod egestas suspendisse aliquet amet ultrices faucibus mauris sit odio. Mattis morbi suspendisse mus ut pellentesque at pulvinar. Interdum justo

Scroll to Top