Support Policy

Scope of support

Technical support services for the Scalr TACO software, scalr.io, and on-prem deployments of Scalr.

Support levels

Scalr provides the following levels of support for the Scalr TACO offering.

Feature	Free Tier	Business
Support Response	Best efforts (1)	Priority based - 24x7
Ticket based support	✅	✅
Real time support (video conf) (2)	❌	✅
Scalr community Slack channel	❌	✅
Priority 0 Response Time	❌	2 hours
Priority 1 Response Time	❌	4 hours
Priority 2 Response Time	❌	12 hours
Priority 3 Response Time	❌	1 business day
Priority 4 Response Time	Best effort	2 business days

(1) Best efforts support - Scalr support will endeavour to respond within the same business day but cannot guarantee this. (2) Real time support for priority 0-3 issues only, if required by Scalr Support.

Priority Definitions and Response times

Response times are the maximum. In general Scalr will respond to tickets in priority order as they are logged. Tickets priorities must be set correctly and Scalr reserves the right to alter ticket priorities, up and down, if they do not match the actual impact and urgency of the issues.

Priority	Description
0 (Blocker)	Production use of the Software is stopped or so severely impacted that it cannot continue to operate, and the operation is mission critical to the business.
1 (Critical)	Experiencing a significant disruption in business critical usage of the Software. Important features are unavailable with no acceptable workaround; however, operations can continue in a restricted fashion.
2 (Major)	A major fault with the software causing non-production usage to be severely impacted. Workarounds may exist but are time consuming/costly.
3 (Minor)	A minor fault with the software / service. The impact is an inconvenience, which may require a workaround to restore functionality.
4 (Trivial)	Requesting information, a product enhancement, or other clarification regarding the Software.

Support Process

All support requests must be created by opening a support ticket via Scalr's web-based support portal via the following URLs: scalr.io (SaaS system) & On-prem Scalr

Responses will be through the support portal and customers will receive email notifications. These emails can be replied to in order to add additional comments to the support ticket.

Real time collaboration via video conferencing will be requested by Scalr to progress priority 0-3 issues only if required. Scalr will use the Zoom system but can use customers' own video conferencing system if required.

Upgrades and Maintenance

There will be regular updates to the Scalr software to implement new features, enhancements and bug fixes. These schedule for these maintenance updates is as follows.

NOTE: Maintenance of Scalr does not affect the infrastructure that is already deployed with Terraform through Scalr. Maintenance only affects the ability to perform new runs through Scalr.

Maintenance Schedule

Every Tuesday and Thursday

• UK: 08:00
• US ET: 03:00
• US PT: 00:00

Maintenance Impact

Customers should assume that Scalr will perform maintenance on every occasion in the schedule. Maintenance typically lasts no more than 30 minutes during which customers experience the following.

• System may show as unavailable for brief periods of time
• UI and API maybe slow or unresponsive
• Unexpected error messages may appear
• Terraform runs may be delayed/queued
• You may be logged out and have to log back in again

Maintenance Notifications

Scalr will post messages in the #announcements channel at scalr-community.slack.com at the start and end of each maintenance.

Exclusions

No support for:

• third-party software used in conjunction with the Software,
• altered, customized or modified software or any portion of the Software incorporated with or into other software,
• Terraform™
• Open Policy Agent

In respect of Terraform and Open Policy Agent, Scalr support will use best endeavors to provide advice and guidance on using this software with Scalr, including examples, best practices etc. However bugs/issues with Terraform and Open Policy Agent should be raised in the relevant support channels/communities.

Upgrade Support Policy (on-prem customers)

Regular Updates. Scalr encourages all customers to regularly update their deployments to the latest version of the Software.

Scalr will patch and upgrade support to older versions as follows:

• Versions released within the previous 12 months. The current version of Scalr, and any version released in the previous 12 months (however, maintenance releases and fixes will only be available in the latest release of Scalr, therefore, Customers may be required to update to the latest version in order to obtain a maintenance release or fix).
• Versions released more than 12 Months. Scalr will provide consultative support (e.g. answer questions, provide known solutions, etc.); however, Scalr is unable to provide any fixes, maintenance releases, product updates, etc. Scalr is unable to provide any kind of support or consultancy to migrate Scalr to new hardware (physical or virtual) for versions more than 12 months old.

Scalr Self-Hosted Support Policy & Services

Support Services Policy

As referenced in the agreement under which you obtain and are granted the right to use the Scalr Software and (if applicable) the Order Form under which you ordered Support Services, this Support Services Policy document is the primary document used to communicate Scalr's support policies. This Support Services Policy includes Scalr's support terms and conditions as well as provides a description of Scalr's technical support levels.

Scope of support

Support services include technical support services, bug fixes, maintenance releases, product updates and upgrades that Scalr provides to all other customers under support for no additional fee.

Support Process

When requesting technical support, Customers are asked to open a support ticket via Scalr's web-based support portal.

Technical Contacts

Technical contacts are the liaisons between Customer and Scalr for the technical support for the Scalr software. Technical contacts should have, at a minimum, Scalr's introductory product training, to ensure that they are knowledgeable about the Scalr Software, and its operating environment in order to help resolve product issues and to assist Scalr in analyzing and support problems.

Customer is expected to establish and maintain the organization and process to provide support directly to its internal end-users in their use of the Software.

Upgrade Support Policy

In order to realize the full benefit of the Software, Scalr encourages all customers to regularly update their deployments to the latest version of the Software. Scalr will provide comprehensive support services for the current major release version of Scalr, and the preceding major release version for up to 12 months following the date of the most current major release version.

Priority Definitions

Priority	Description
0 (Blocker)	Production use of the Software is stopped or so severely impacted that it cannot continue to operate, and the operation is mission critical to the business.
1 (Critical)	Experiencing a significant disruption in business critical usage of the Software. Important features are unavailable with no acceptable workaround; however, operations can continue in a restricted fashion.
2 (Major)	A major fault with the software causing non-production usage to be severely impacted. Workarounds may exist but are time consuming/costly.
3 (Minor)	A minor fault with the software / service. The impact is an inconvenience, which may require a workaround to restore functionality.
4 (Trivial)	Requesting information, a product enhancement, or other clarification regarding the Software.

Exclusions

Scalr has no obligation to support: (i) third-party software used in conjunction with the Software, (ii) altered, customized or modified software or any portion of the software incorporated with or into other software, (iii) Software that is outside the scope of General Availability as specified in the Scalr Support Lifecycle section above, (iv) software installed on any hardware and/or operating system that is not supported by Scalr, and (v) the use of the Software in conjunction with unsupported cloud services.

Scalr will provide technical support services to assist in troubleshooting the Software's interaction with supported cloud services; however, Scalr has no obligation to provide support for the cloud services themselves.