Peerobyte / Documentation / 30-Day Freetest IaaS - Special Trial Policy

30-Day Freetest IaaS - Special Trial Policy

Published

1. Purpose of the document and applicable terms

1.1. This document "30-Day Freetest IaaS - Special Trial Policy" (the "Special Terms") sets the parameters and unique terms of the "30-Day Freetest IaaS" trial programme (the "Programme"), provided by VIRTUAL NETWORK LAB L.L.C-FZ and its affiliates operating under the designation "Peerobyte" (collectively, "Peerobyte").

1.2. The Programme is a Trial Programme within the meaning of the "Peerobyte Trial Policy" (the "Trial Policy"). These Special Terms set out more specific provisions of the Trial Policy for the Programme.

1.3. These Special Terms apply taking into account the order of contractual priority established by the Trial Policy. In the event of inconsistencies between these Special Terms and the Trial Policy concerning the parameters and procedure for providing the Programme, these Special Terms apply, unless an Individual Trial Programme Agreement, an applicable Contract, or mandatory requirements of applicable law provide otherwise. To the extent not regulated by these Special Terms, the Trial Policy, the Agreement, and other applicable Peerobyte documents apply.

1.4. Descriptions of the Programme in instructions, on the Site, in the interface, in tooltips, banners, the "FAQ" section, advertising and other information materials do not amend these Special Terms, the Trial Policy, or the Agreement and do not constitute an Individual Trial Programme Agreement, unless they expressly show an intention agreed by the Parties to amend the terms of the Programme. In the event of inconsistency, the applicable contractual documents prevail in the order established by the Trial Policy.

1.5. The requirements of the Acceptable Use Policy, No Spam Policy, Intellectual Property Policy, and other applicable Peerobyte documents must be complied with in all cases. If these Special Terms provide requirements that are less strict than those documents, the stricter requirements apply, unless mandatory requirements of applicable law provide otherwise.

2. Main parameters of the Programme

2.1. The Programme is provided at the discretion of Peerobyte and is intended for assessment of the "Cloud Infrastructure" Service.

2.2. Under the Programme, Peerobyte provides the User with Test Access to the "Cloud Infrastructure" Service.

2.3. Test Access is provided for 30 calendar days. The period is calculated from the date and time of actual deployment of the test project, as recorded in the Peerobyte accounting system, and ends after 30 calendar days on the corresponding date and time according to Peerobyte billing time. If a different time is displayed to the User in the Peerobyte interface, the data of the Peerobyte accounting system prevails, unless mandatory requirements of applicable law provide otherwise.

2.4. Within Test Access, the User is provided with:

  1. an individual project in the Peerobyte cloud infrastructure with the quotas established by these Special Terms;
  2. a project control panel in the Peerobyte cloud infrastructure (GUI);
  3. a command-line interface for managing the Peerobyte cloud infrastructure (CLI);
  4. access to the control panel for the Peerobyte "Cloud Infrastructure" Service.

2.5. To implement the purposes of the Programme, Peerobyte records in the Peerobyte accounting system (billing), for the User Account, a promo credit with a nominal value of EUR 222 (the "Bonus"). The Bonus is a conditional accounting value and is used exclusively for accounting coverage of the fixed resource quota configuration under the Programme. Recording or debiting the Bonus does not constitute making a Payment by the User, adding funds to the Account Balance, payment for a Paid Subscription, or a basis for any refund, payout, withdrawal, or compensation. The Bonus cannot be used for other Services, quota expansion, payment for a Paid Subscription after Test Access ends, or withdrawal of funds.

2.6. Withdrawal of the Bonus and any other use of the Bonus not provided for by these Special Terms is prohibited.

2.7. Resource quota configuration for Test Access:

  1. 14 virtual CPUs;
  2. 46 GB of RAM;
  3. 290 GB of hybrid storage (SSD+HDD);
  4. 190 GB of All-Flash Storage (SSD);
  5. backup volume: 290 GB;
  6. floating IP addresses: 2.

2.8. Resource quotas are not increased at the initiative of the User within Test Access. Quota expansion is possible only upon early transition to paid service, if such transition is confirmed by the User and approved by Peerobyte.

2.9. Test Access is provided on condition that at least one Payment Method is linked to the User Account and verified throughout the entire Test Period.

3. Special IaaS use scenarios

3.1. In addition to the general permitted purposes established by the Trial Policy, under the Programme the User may use the Test Resources for the following IaaS scenarios within the allocated quotas:

  1. familiarisation with the Peerobyte cloud infrastructure management interfaces and standard project management operations;
  2. deployment and study of operating system images, standard software stacks, and templates available in the Peerobyte cloud infrastructure;
  3. training in OS administration and configuration in a test environment;
  4. configuring test network parameters, filtering rules, security groups, access policies, logging, and monitoring, if the relevant mechanisms are available in the project;
  5. deployment of test, demonstration, and pilot web interfaces and APIs using floating IP addresses;
  6. integration testing with external test or non-production systems, including webhooks, OAuth/OIDC, external APIs, repositories, and container registries;
  7. basic performance measurements of test and pilot environments owned by the User within the allocated quotas and restrictions established by the Trial Policy.

3.2. Under the Programme, it is prohibited to use the Test Resources for resale, sublicensing, transfer to third parties as an independent paid infrastructure service, managed service, outsourcing service, or any other independent commercial provision of the Test Resources, as well as for processing sensitive or regulated data and for other purposes prohibited by the Trial Policy, the Agreement, and applicable Peerobyte documents.

3.3. In relation to the Programme, full production operation of the Test Resources is permitted within the allocated quotas, the Test Period, and other restrictions established by these Special Terms, the Trial Policy, the Agreement, and other applicable Peerobyte documents. Such use of the Test Resources in the production processes of the User is not considered monetisation of the Test Resources prohibited by clause 3.2.

3.4. Load testing, stress tests, mass generation of network traffic, long-term tests of maximum resource utilisation, and public comparative testing are permitted only with prior written approval from Peerobyte and within the agreed parameters.

4. Participant requirements and activation procedure

4.1. A User may participate in the Programme if the User meets the requirements of the Trial Policy and has not previously received Test Access under this or a similar Peerobyte programme, and has also not previously used the Peerobyte "Cloud Infrastructure" Service on a paid basis through the same Account, the same organisation, or other indicators that Peerobyte may take into account in accordance with the Trial Policy, unless otherwise agreed by Peerobyte.

4.2. To activate the Programme, the User must fulfil the general requirements of the Trial Policy, the steps provided in the "How to Activate the 30-Day Freetest IaaS Program" instruction, and the steps in the Peerobyte interface, including accepting the Agreement, the Trial Policy, these Special Terms, linking and verifying the Payment Method, and giving consent to the automatic transition of the Transitioning Resources to paid use and to the charging of the Payment if the User does not submit an Opt-Out.

4.3. After the activation conditions are met and the Account and the User are approved by Peerobyte, the following consequences arise:

  1. the Peerobyte accounting system records a targeted Bonus in the Account Balance linked to the User Account for use under the Programme;
  2. the Peerobyte accounting system debits the Bonus for accounting coverage of the fixed resource quota configuration under the Programme; such debit does not constitute making a Payment by the User;
  3. an individual project is deployed for the User in the Peerobyte cloud infrastructure with the quotas established by these Special Terms;
  4. in the "Products & Services" section of the Peerobyte services control panel, the User is given access to manage the "Cloud Infrastructure" product;
  5. the User receives the status of participant in the "30-Day Freetest IaaS" programme.

5. Completion of the Programme and paid continuation

5.1. The Programme provides for automatic transition of the Transitioning Resources to paid use after the end of the Test Period, if Peerobyte has not received an Opt-Out before the end of the Test Period in the manner established by the Trial Policy and these Special Terms.

5.2. Transitioning Resources are the project resources created and not deleted at the time of the end of the Test Period, including virtual machines, volumes, floating IP addresses, related configurations and data, as well as the project itself, if retaining it is technically possible. Unused quotas, unused Bonus, and rights to quota expansion are not Transitioning Resources, unless expressly agreed otherwise with Peerobyte. 

5.3. If Peerobyte has not received an Opt-Out before the end of the Test Period, the Transitioning Resources continue to operate on a paid basis under a Paid Subscription to the "Cloud Infrastructure" Service.

5.4. The Paid Subscription is set up with the following parameters:

  1. the amount of paid use is determined by the Transitioning Resources at the time of transition, and the project quotas are set at the level required to retain such Transitioning Resources, unless otherwise agreed by the Parties;
  2. the unit cost of resources and the charging procedure are determined by the current tariffs and the Agreement, unless otherwise agreed by the Parties;
  3. the payment period is set at 1 month, unless otherwise agreed by the Parties;
  4. the project, data, account and authentication credentials for access to the Peerobyte cloud infrastructure are retained in the form in which they existed at the time of transition to paid service, if this is technically possible and does not breach the applicable Peerobyte documents;
  5. funds to pay for the Paid Subscription are debited from the available cash amount in the Account Balance, if such balance exists and can be used to make the Payment; if such balance is insufficient, the Payment is debited from the Payment Method linked to the User Account;
  6. the Bonus received under the Programme is not included in the available cash amount in the Account Balance and cannot be used to pay for the Paid Subscription.

5.5. No later than 2 calendar days before the end of the Test Period, Peerobyte sends the User a notice of the upcoming end of the Test Period, the composition of the Transitioning Resources, the possible consequences of completion, the estimated cost of paid use, and the available ways to opt out of paid continuation. Such notice is sent with the content, through the channels, and with the consequences provided by the Trial Policy.

5.6. Early transition to a Paid Subscription is permitted before the end of the Test Period on the basis of a User ticket submitted through the Peerobyte services control panel and after confirmation by Peerobyte. The transition of the Transitioning Resources to paid service is considered complete from the moment of proper payment for the Paid Subscription, provided that Peerobyte has not refused to set up such Paid Subscription, unless Peerobyte has expressly agreed another procedure. From that moment, Test Access is considered to have ended early, and further use of the resources is governed by the Agreement, applicable appendices, and the terms of the Paid Subscription.

5.7. The consequences of an Opt-Out, non-payment for the Paid Subscription, unlinking of the required Payment Method, late payment, suspension, and termination of participation are determined by the Trial Policy.