Gold Support Service & SLA

The Gold Support and Service Levels apply to your purchase of JFrog’s Gold Support service, which includes the following:

DEFINITIONS.
1. “Developer Support Engineer”or“DSE”means a support engineer who is certified to handle complex enterprise level environments.
2. “Documentation”means the documentation provided in connection with the Subscription as defined in the governing terms for the Subscription
3. “JFrog Software”means the software provided by JFrog.
4. “Health Check”means a diagnostic scan of your deployment, which is measured against a repository of best practices and reference implications.
5. “Issue”means a failure of the JFrog Software to substantially conform to its Documentation.
6. “Notification”means your initial notification of an issue to JFrog through the Technical Support Process as set forth herein.
7. “Response Time”means the time interval between Notification and JFrog’s response to you acknowledging receipt of the Notification.
8. “Primary ESL”means an Enterprise Solutions Lead Technical advisor assigned to you during the applicable Subscription Term who provides guidance and recommendations as part of Gold Support.
9. “Support Contact”means eight (8) individuals designated by you who are responsible for administration of the JFrog Software.

TECHNICAL SUPPORT

JFrog will provide you with technical support using commercially reasonable efforts to respond to Issues submitted by Support Contacts, which may include:
1. Joint remote technical sessions to gather additional information on Issues;
2. Temporary workarounds, patches, or changes to the JFrog Software in a new release;
3. Diagnosis of JFrog Software Issues in accordance with Section 4; and
4. The monitoring and analysis of the JFrog Software performance.
Technical support will not be provided if the Issue arises from your: (1) use of the JFrog Software in a manner inconsistent with the applicable Documentation, (2) modifications to the JFrog Software which were not provided or authorized in writing by JFrog, or (3) use of the JFrog Software with products or software not provided or authorized in writing by JFrog.

TECHNICAL SUPPORT PROCESS

Support Contacts may initiate Technical Support in the following ways:
1. By Phone:A Support Contact may initiate contact via the Phone Number listed below 24 hours per day, 7 days per week, 365 days per year solely for Critical Issues.
2. By Email:A Support Contact may initiate contact by sending an email to the address listed below 24 hours per day, 7 days per week, 365 days per year, and JFrog shall respond with an acknowledgement email with a Notification reference number.
3. Via Support Portal:A Support Contact may initiate contact and submit a Notification through JFrog’s support portal athttps://support.m.si-fil.com(“Support Portal”). Support Contacts may update and track all open Notifications through the Support Portal. Support tickets are assigned to a DSE.
4. Bi-weekly Meetings.You will be entitled to bi-weekly meetings with your Primary ESL to address support, configuration, and usage inquiries at mutually agreeable times and dates.

Notifications may be reported as follows:

YOUR RESPONSIBILITIES
1. You must provide JFrog with relevant data, process information, supporting analysis, and access to Support Contacts as reasonably required by JFrog to respond to Issues. You are solely responsible for the adequate duplication and documentation of all its files and data for backup purposes. You acknowledge that information and materials provided to JFrog by Support Contacts may be used by JFrog for the purpose of providing Support.

SERVICE LEVELS.
Gold Support includes the following Service Levels:

Severity Level	Description of Severity	Response Times
Severity 1(“Critical Issue”)	(i)A catastrophic problem which renders the JFrog Software inoperative within your production system; or (ii) your production functionality and you cannot continue your essential operations. This Service Level will not apply to your non-production or development systems.	Ninety (90) minutes from Notification.
Severity 2(“High Issue”)	(i) A high-impact problem which significantly degrades the performance of the JFrog Software but does not cause complete inoperability for you; or (ii) an Issue that prevents you from enabling a feature in a production environment that the production system does not currently rely on.	Twelve (12) hours from Notification.
Severity 3(“Medium Issue”)	A lower impact problem on a production or non-production system that involves a partial or limited loss of non-critical functionality, or some other problem involving no loss in functionality but you are able to continue essential operations. All Issues in connection with non-production systems, such as test and development systems.	Twenty-four (24) hours from Notification
Severity 4(“Low Issue”)	Issues with no impact on the quality, performance, or functionality of the JFrog Software in a production or non-production system.	Twenty-four (24) hours from Notification

REPORTS
1. Open/Closed Ticket Reports:JFrog’s Primary ESL will provide you with a quarterly report on open/closed tickets with a summary review of the past quarter activity and Response Times.
2. Jira Reports:Standard quarterly Jira reports will be provided with details on the current status of your Jira items. Jira items may include product enhancements requests, bugs fixes and changes requiring R&D input.
QUARTERLY BUSINESS REVIEWS
You will receive quarterly business reviews from JFrog’s sales, support, R&D, and product management teams, which may include the following:
1. delivery of the quarterly business reviews with early collaboration on presentation and materials
2. Planning sessions
3. A review of last quarter’s support activities (including support tickets, Jira items, projects and special events handling) as well planning of the next quarter’s major activities and milestones
ANNUAL HEALTH CHECKS
JFrog shall perform an annual Health Check of your configuration during the applicable Subscription Term for Gold Support, which includes:
1. Local, remote, and virtual repository configuration and usage;
2. Artifactory Query Language (AQL) usage and performance; and
3. System performance against benchmarks.