UPSUN - Service Specific Terms

Last updated 23.05.2025

Capitalized terms not defined in these UPSUN Service Specific Terms have the meaning given to them in the Terms of Services.

These UPSUN Service Specific Terms apply to Customers subscribing to or using the services or features listed below.

1. Uptime:

1.1. Uptime available to all Customers 

Platform.sh will make commercially reasonable efforts to make sure the uptime of the hosting infrastructure of Customer’s Projects on production environment reaches or exceeds 99.5% monthly. The best efforts uptime commitment mentioned above does not apply to development and test environments and is exclusive of all interruptions for maintenance purposes and incidents caused by Customer Projects (e.g. Project that exceeds the allocated resources, contains a programming error, failure to apply updates) and/or caused by failure of TLS certificates provided by Customer.  

1.2. Premium or Advanced Uptime add-ons

1.2.1.  Definitions 

“Monthly Uptime Percentage” means the percentage derived by subtracting from 100 the percentage of Service Unavailability minutes during the month. 

“Service Credit” means a percentage of the Subscription Fee to be credited to Customer if Platform.sh fails to meet the Service Level agreed in 1.2.2 below. Service Credit is calculated based on the monthly Subscription Fee due for the environment in production suffering from the Service Unavailability status, as defined below. 

“Service Levels” means the service levels set out in 1.2.2 below.

“Service Unavailability” means the unavailability of the hosting infrastructure of Customer’s Projects on production environment, due either to errors or failures in the hosting stack or lack of network connectivity to the Internet. 

1.2.2.  Premium or Advanced Uptime and Service Credits 

1.2.2.1. Premium or Advanced Uptime require the subscription to “Premium” or “Advanced“ Support

1.2.2.2. Premium or Advanced Uptimes are contracted at Project level. Minimum subscription term is twelve (12) months. 

1.2.2.3. Platform.sh will provide the following service level agreements:

1.2.3.  Service Level  exclusions

1.2.3.1.  The Service Levels identified above do not apply to any Service Unavailability, suspension or termination of the Services caused by any of the following: 

1.2.3.1.1. Factors outside of the reasonable control of or not directly imputable to Platform.sh, including but not limited to any force majeure event listed in this Agreement, internet access, or related problems beyond the software and server instances directly maintained by Platform.sh; 

1.2.3.1.2. Problems resulting from any act or omission of Customer, including errant or problematic application code deployed into an environment; 

1.2.3.1.3. Issues resulting from Customer’s equipment, software or other technology and/or third party equipment, software or other technology (other than third-party equipment directly maintained by Platform.sh); 

1.2.3.1.4. Issues that affect non production environments (e.g.development and/or staging environments, etc);.

1.2.3.1.5   Services that are not essential to the uptime of the hosting infrastructure of the Project in production environment (e.g. Console, CLI, APIs for the control plane, user authentication, etc);

1.2.3.1.6. Issues that result from any act or omission of the Platform.sh support team at the request of Customer (e.g. downtime caused by the refusal of Customer to increase the resources allocation on a Customer Project);

1.2.3.1.7. Issues arising from suspension and/or termination of Customer’s right to use the Services in accordance with this Agreement;

1.2.3.1.8. Customer-caused unavailability such as missing content, errors caused by Customer code or application configuration errors, or usage capacity in excess of the Customer purchased amount;

1.2.3.1.9. Service Unavailability due to maintenance operations. Platform.sh reserves the right to interrupt part or all of the Services to perform a technical intervention for the purpose of ensuring the proper operation of the Services, and the safety and stability of the infrastructure behind the Services. Platform.sh will make commercially reasonable efforts to limit the occurrence and duration of the interruption and, where feasible, will publish notifications of upcoming scheduled maintenance operations on https://status.platform.sh/ at least 5 calendar days ahead of the maintenance date. Customer can also subscribe to updates and be notified by email on upcoming and ongoing maintenance operations.

1.2.3.2. When factors causing the Service Unavailability status cannot be clearly imputed to Platform.sh, Platform.sh may, on a case-by-case basis and in its sole discretion, grant Service Credits. 

1.2.3.3. Unavailability of some specific features or functions within a Project in production, while others remain available, will not constitute Service Unavailable status, so long as the affected features or functions are not, in the aggregate, material to the Project or the Services as a whole. 

1.2.4.  Service Credits

1.2.4.1. Customer’s sole and exclusive remedy for any Service Unavailability, non-performance, or other failure by Platform.sh to provide Services is the receipt of a Service Credit. 

1.2.4.2. Service Credits will only be applied against outstanding invoice or future Subscription Fees due and will not entitle Customer to a refund or other payment; except that in the event that Customer is entitled to a Service Credit on termination of the Agreement, Platform.sh will refund Customer in the amount of the Service Credit within thirty (30) days of a request by the Customer to do so.

1.2.4.3. Should Platform.sh fail to provide Monthly Uptime Percentage of at least 97% for three (3) successive calendar months, Customer may terminate this Agreement immediately on notice to Platform.sh and receive a cash refund in the amount of the current Subscription Term’s prepaid Fees proportionate to the unexpired portion of the Term.

1.2.4.4. To receive a Service Credit, Customer must submit a claim by opening a support ticket prior to the end of the second month after which the incident occurred and must include: 

1.2.4.4.1. The words “Service Credit Request” in the subject line; 

1.2.4.4.2. The dates and times of each Service Unavailable incident being claimed; 

1.2.4.4.3. The affected Service Project ID; 

1.2.4.4.4 The request logs that document the errors and corroborate the claimed outage (any confidential or sensitive information in these logs should be removed or replaced with asterisks). 

1.2.4.5. If the Monthly Uptime Percentage of such a request is confirmed by Platform.sh and is less than the Service Level, Platform.sh will issue the Service Credit within one month following the month in which the request is confirmed. Failure to provide the request and other information as required above will disqualify Service Credit eligibility. 

2. Support 

2.1 Support available to all Customers

2.1.1. Standard support  will be provided through an online service desk and on public forums.

2.1.2. Standard support does not include specific answer time commitment, but Platform.sh will make commercially reasonable efforts to answer Urgent (P1) tickets within 4 hours (24*7*365).

2.2 Premium or Advanced support add-ons

2.2.1.  Premium or Advanced support is contracted at the Organization level. Minimum subscription term is twelve (12) months. 

2.2.2.  Support tickets will be addressed 24/7/365 in order of the priority level and support tier.

2.2.3. Response times: Support tickets will be addressed according to the response times for the relevant support tier as set forth in the table below:

2.2.4. Regular Support Hours are as follows: from 00:00 UTC to 23:59 UTC Monday to Friday. 

2.3.  Procedures 

2.3.1. Login. Users will be granted access to the support ticketing and issue management system (“Support Portal”). 

2.3.2. Initiation of Support Tickets and Ticket Workflows. Tickets are initiated by the Users through the Support Portal and must be submitted separately for each Project and/or issue. They should include: 

2.3.2.1 Description of the issue or request, including identification of Supported Modules;

2.3.2.2. Description of the desired state or outcome;

2.3.2.3. Steps necessary to demonstrate or reproduce the issue;

2.3.2.4. Initial Indication of Priority Level (see descriptions of P1 Urgent, P2 High, P3 Normal in 2.4.1. below) 

2.3.3. Ticket status. Through the Support Portal, Platform.sh will provide updates on investigation progress and any change of status. Statuses include: 

2.3.3.1. New. Tickets not yet reviewed. 

2.3.3.2. Open. Analysis in process. 

2.3.3.3. Pending. Tickets that are awaiting feedback or other progress from Customer based on information required, or recommendations made, by Platform.sh. 

2.3.3.4. Scheduled / On Hold: Events that are requested or scheduled to be executed within the next 72 hours will be marked with this status and will be actioned at the requested time. 

2.3.3.5.Solved. Tickets that have reached a conclusion either through resolution of the issue or determination that no further work is warranted. 

2.4. Priority Level

2.4.1. Priority levels are defined as follows: 

2.4.1.1. Priority 1 Urgent (P1) - P1 is a catastrophic production problem that severely impacts the Customer’s production systems, or because of which Customer’s production systems are down or not functioning, or that results in a loss of production data and no workaround exists. Platform.sh will make continuous efforts, with appropriate escalation to senior management, to provide a resolution. 

2.4.1.2. Priority 2 High (P2) - P2 is a problem in which the Customer’s system is functioning but in a reduced capacity, or the problem is causing significant impact to portions of business operations and productivity, or the software is exposed to potential loss or interruption of service. Platform.sh will make continuous efforts to provide a resolution. 

2.4.1.3. Priority 3 Normal (P3) - P3 is a medium- to low-impact problem that involves partial and/or non-critical loss of functionality, or that impairs some operations but allows the Customer’s operations to continue to function. Problems for which there is limited or no loss of functionality or impact to the Customer’s operation and for which there is an easy workaround qualify as P3. Platform.sh will use reasonable efforts to provide a resolution in time for the next minor release of the software.

2.4.1.4. Blackfire support tickets will be treated as Priority 3 Normal (P3) tickets.

2.4.2. Customer acknowledges that response targets for the relevant support tier as per sections 2.1 and 2.2 above are response targets only and not resolution targets. Platform.sh sets no target and makes no guarantee or representation to the Customer regarding resolution times of support tickets. 

2.5. Included services

2.5.1. Support is available for all Customer environments hosted on Upsun (production, staging and development environments) (see exclusions in Section 2.6, below). P1 Tickets are only applicable to live, production environments. Support is only available for repeat or systemic issues or errors.

2.5.2. Support includes the following: 

2.5.2.1. Response. Platform.sh will respond to and make commercially reasonable efforts towards resolving submitted support tickets. Responses will be addressed within the timeframes and allowances corresponding to the Customer’s purchased support level. 

2.5.2.2. Post-Issue Analysis. For Advanced and Premium support services, Platform.sh will use commercially- reasonable efforts to provide post issue analysis upon request following the conclusion of Platform.sh specified Priority 1 (“P1”) tickets only. Customers must request this within 14 calendar days of the ticket being closed, via an update to the original Priority 1 ticket. Customers will be provided a written summary of no more than 500 words in an attachment to the original ticket. Code samples, when included, are not counted towards such limits. The summary will include, as applicable, an explanation of the circumstances, change, or context that caused the issue, or business practices that resolved the issue, and recommendations for prevention of future instances. Depth of analysis is at the discretion of Platform.sh. No additional efforts on the issue will be undertaken. 

2.6.  Excluded services

2.6.1. Except as expressly agreed in writing by Platform.sh, the following are excluded from Support: 

2.6.1.1 P1 Support excluded for Non-Production, Development or Preview environments, or other functionalities. Staging environments, “sandbox” Projects, and other sites related to the development of a production Project are not eligible for P1 Support. 

2.6.1.2. No support to  end-users of Customer’s application. Support for end-users of Customer’s applications hosted on Upsun will be provided exclusively by Customer. 

2.6.1.3. Training and Consulting. Support related to the application implementation, standard usage, and project consulting is not provided unless specifically ordered by Customer. 

2.6.1.4. Hardware, operating system, third-party software, databases, and networks. No support relating to installation, configuration, use, maintenance, or functionality of non-Service hardware, operating systems, third-party software, databases networks, or other enabling technologies is provided.