Service Description and Price List

1.1. This document is an Appendix to the Agreement by and between the Parties. The document describes Metaplay Platform features, pricing, and Support Services.

1.2. Section I covers Metaplay Platform features, plans, and pricing. Section II addresses Support Services features, plans, and pricing.

1.3. The Agreement, including Metaplay General Terms and Conditions 2024, applies to both the Platform and Support Services.

1.4. This is a service description document; actual plans, service levels, and commercial details are established in an Order between parties.

2.1. The Metaplay Platform consists of software used to set up, run and manage Development Environments, Staging Environments and Production Environments (jointly “Environments”).

2.2. The Platform is primarily a software service, though parties may agree the Customer hosts it themselves depending on their plan.

3.1. For software-as-a-service delivery, Metaplay hosts Environments. Setup occurs primarily through Metaplay with Customer assistance. Access credentials are provided, allowing Customer access via portal.metaplay.dev.

3.2. For self-hosted arrangements, the Customer manages setup and hosting. Metaplay provides assistance as specified in the Customer's plan. Software access is available through the Portal for download.

3.3. Subject to the Customer having an appropriate plan and subject to the Metaplay Platform being provided as a software service, service levels may apply per a separate Appendix.

4.1. Various Environment types are available as described below.

Development Environments

4.2. A Development Environment is an environment set up for the purposes of developing and testing Applications. These support internal testing and limited soft launches for testing purposes only. Development Environments have DAU caps defined in Section 6.

4.3. Customers ensure Development Environments suit their application development and testing needs, respecting DAU limits.

Staging and Production Environments

4.4. A Staging Environment is an environment set up for the purposes of simulating the Production Environment. It supports testing in a mirrored production setting but cannot be used for public commercial availability.

4.5. A Production Environment is an environment set up for the purposes of the production use of an Application, including public commercial availability.

4.6. Metaplay will provide daily, weekly and monthly back-up copies of the Customer's data in Production environments hosted by Metaplay. Daily back-up copies shall be retained for 7 calendar days, weekly back-up copies shall be retained for 28 calendar days, and monthly back-up copies shall be retained for 365 calendar days.

4.7. Customers ensure Staging and Production Environments suit their application testing and production purposes.

5.1. Metaplay has reserved a reasonable amount of computing capacity to enable the Metaplay Platform to provide a diligently programmed Application a back-end with a reasonable performance level. Capacity increases proportionally with DAU increases.

5.2. The Parties note, however, that the actual performance of an Application using the capacity provided by Metaplay will be dependent on multiple factors, some outside the control of Metaplay. Inefficient Customer programming may consume disproportionate resources. Customers must develop applications that don't unreasonably burden the Platform.

5.3. Customers are primarily responsible for satisfactory application performance. If capacity proves insufficient, parties discuss and negotiate additional resources for potential additional fees. Professional Services may optimize application code or improve performance.

7.1. A Daily Active User (DAU) is a unique user that has opened the Application during a given single day (24 hours), evidenced by:

• A user logged into Environments (monitored via automatic backend analytics); or
• A user who started the Application (monitored via Customer-provided analytics).

7.2. Test accounts used by Customer in Development and Staging Environments during normal development/testing don't count as DAU for invoicing.

7.3. If parties agree Customer provides DAU details, the Customer shall provide timely, true, precise, and complete reports on the number of DAU to Metaplay on a monthly basis for correct invoicing.