Billing is the same for most resources. However, some resources have a special nature that requires a different billing scheme:

• IP Address
• OpenSRS
• Quota
• Traffic
• MySQL/PGSQL db size quota
• MS SQL db size quota
• Real User

1. IP Address is billed only when it stores a dedicated IP address; shared IP is always free. All prices (setup, recurrent, usage) are set only for dedicated IP.
2. OpenSRS needs only setup fee which is the cost of domain registration for 1 year. If a client signs up for more than a year, the setup fee is multiplied by the number of years. When this period ends, the user is charged again for the same number of years.
   Important: The setup fee must be clearly set for each billing period, so it is not affected by discounts.
   Note: When a user registers a new domain with OpenSRS, the domain resource fees are also charged.
3. Quota (Web Disk Quota, Mail Quota, RealServer Disk Quota):
   Disk space is measured in MB and usage/recurrent fee is calculated as MB of space multiplied by the usage/recurrent price. Every time user changes disk quota, the quota resource is deleted and created anew. Therefore, setup fee is not applied to this type of resource.
4. Traffic (Summary Traffic, HTTP Traffic, User FTP Traffic, Virtual FTP Traffic, Real User Traffic, RealServer Traffic):
   - Setup fee - like in quota resources, every time user changes traffic limit, the traffic resource is deleted and created anew. Therefore, setup fee is not applied to this type of resource.
   - Traffic limit - the amount of traffic that user plans to run up during the billing period. This amount includes Free units. Traffic limit is set in the user control panel. If a user changes its value, the current billing period for traffic limit closes and outstanding amounts get charged.
   - Recurrent fee is charged in advance for the whole billing period for the traffic set as the traffic limit minus free units.
   - Usage fee is charged at the end of each month of the billing period for the prorated amount run up beyond the limit. We recommend setting higher usage fee rates as a punitive measure.
   - When the billing month ends, the traffic is multiplied by months in the billing period, then the limit is subtracted to obtain the excess, and, if the result is positive, it is divided by months in the billing period and is charged as the usage fee. For example, you host a user with the billing period of 6 months, 0 free units, and the traffic limit of 6 GB. During the first month, the user runs up 1.5 GB, which is 0.5 GB higher than the prorated monthly expectation. The payment for 0.5 GB excess traffic is charged as the usage (excess) fee.
   - When a user changes traffic limit, the current billing period for traffic closes, the prorated usage fee is charged, and user's traffic is set to zero. As the result, the billing period for traffic becomes different from the billing period for the account. For example, you host a user with 0 free units, the traffic limit of 6 GB, and the billing period of 6 months starting 1 January. By 15 January, the user runs up 1 GB of traffic, which is 0.5 GB higher than the prorated expectation for 15 days. On 15 January, the user changes the traffic limit. The user is charged for the 0.5 GB excess traffic as the usage fee, and user's traffic details are set to zero.
   - If a user has paid in advance for several months, the usage fee (overlimit) is still charged on monthly basis.
5. MySQL/PGSQL db size quota
   The size of MySQL or PGSQL database is the total size of all files in the database directory. Usage/recurrent fee is calculated as MB of space used beyond Free Units multiplied by the usage/recurrent price in $/Mb.
   - Setup fee - like in Quota and Traffic resources, every time a user changes the quota, the quota resource is deleted and created anew. Therefore, setup fee is not applied to this type of resource.
   - Database size quota - disk space that a user expects to use during the billing period. This amount includes free units. Database size quota is set in the user control panel. If a user changes its value, the current billing period for database size quota closes and outstanding amounts get charged.
   - Recurrent fee is charged in advance for the whole billing period for the disk space set as the database size quota minus free units.
   - Usage fee is charged at the end of each month of the billing period for the prorated amount used in excess of the database size quota. We recommend setting higher usage fee rates as a punitive measure.
   - When the billing month ends, the user is charged for the disk space used in excess of the quota. For example, you host a user with the billing period of 6 months, 0 free units, and the database size quota of 60 MB. By the end of the first month, the size of the database makes 65 MB, and the 5 MB overlimit is charged as the usage (excess) fee.
   - When a user changes database size quota, the current billing period for database disk quota closes, and the usage fee is charged.
6. MS SQL db quota
   The size of MS SQL database is the actual size of all database files and MS SQL logs. MS SQL db quota cannot be exceeded, therefore no usage fee is charged. Recurrent fee is charged once at the beginning of the billing period.
   - When a user changes MS SQL database quota, it is deleted and created anew, which is why setup fee is not applied to this type of resource.
   
7. Real User
   In this resource, users are charged for the maximum simultaneous connections, i.e. how many visitors can simultaneously access user's RealServer account.
   - Setup fee - like in Quota and Traffic resources, every time a user changes the number of connections, the RealServerUser resource is deleted and created anew. Therefore, setup fee is not applied to this type of resource.