Orkes Cloud Support Policy

This Support Policy (this “Policy”) describes the support obligations of Orkes, Inc., a Delaware Corporation (“Orkes”) for each customer (“Customer,” and together with Orkes, the “Parties,” and each, a “Party”) who has entered into and are party to that certain Orkes Cloud Services Agreement (“Cloud Services Agreement”) and who have purchased support services in connection with the Cloud Services Agreement. Capitalized terms not defined in this Policy have the meaning set forth in the Cloud Services Agreement.

Article 1

Support Services

    1. Support Services. Orkes offers the support services (“Support Services”) described in this Policy.

    2. Support Services Channels. Orkes shall provide the Support Services through its online support portal (“Support Portal”). Following submission of a Support Ticket (defined below), Orkes will communicate with Customer using email, the Support Portal, or video conferencing. Any necessary telephone support discussions will be scheduled in advance at a time mutually agreed by the parties and for durations and at a frequency that is commercially reasonable for Confluent. Support Services will be provided in English. For the purposes of this Policy, “Support Ticket” means a technical issue affecting Customer’s ability to utilize or access the Services, as further described in Section 1.3.

    3. Support Ticket Prioritizations.

Support Ticket Classification

Description

Catastrophic Support Ticket (P1)

The Services are unusable or unavailable for a significant number of Customer Users, or mission- critical functionality of the Services are unusable or unavailable. A full Services outage is an example of a Catastrophic Support Ticket.

Critical Support Ticket (P2)

The Services experience a significant malfunction, which materially impacts a portion of the functionality or the population of Customer Users. Intermittent Services outage is an example of a

Critical Support Ticket.

Important Support Ticket (P3)

The Services experience a non-critical malfunction, which does not materially impact the functionality of the Services.

  1. During the submission process, Customer may suggest a Support Ticket Classification for a Support Ticket. Orkes will review Customer’s suggested Support Ticket Classification and respond in accordance with the applicable Support Response Expectation Table (defined below). However, Orkes may re-assign the Support Ticket Classification Level in its sole discretion if it believes another designation is more accurate based on the definitions specified in this Policy. Orkes will notify Customer of such a change in its response to the support request.


    Article 2

    Support Ticket Reporting and Response

  2. Orkes will provide a written notice of receipt of the Support Ticket report by email. Orkes will execute the following in accordance with the Support Response Expectation Table, below:

    • Orkes will notify Customer of a Support Ticket notice and begin collecting any additional information necessary to correct the Support Ticket.

    • Orkes will use reasonable efforts to provide a patch, correction, workaround, or otherwise resolve the Support Ticket.

  3. Orkes will use reasonable efforts to respond to reported Incidents during the response tim`es set forth in the Support Response Expectation Table, below. Customer understands and agrees that resolution of a Support Ticket is not guaranteed and may not occur.


    Support Response Expectation Table

    Support Ticket Classification

    Support Response Plan

    Basic

    Standard

    Premium

    Catastrophic Support Ticket (P1)

    Within 36 business hours

    Within 8 business hours

    Within 4 hours

    Critical Support Ticket (P2)

    Within 5 business days

    Within 1 business day

    Within 8 hours

    Important Support Ticket (P3)

    Within 7 business days

    Within 2 business days

    Within 24 hours

    Article 3

    Customer Responsibilities

  4. Orkes’ obligation to provide Support Services is conditioned upon Customer satisfying the following responsibilities with respect to each Support Ticket: (a) Customer making reasonable efforts to resolve the Support Ticket before reporting the Support Ticket to Orkes, including having the Support Ticket reviewed by the personnel of Customer who submits the Support Ticket; (b) Customer has provided Orkes with sufficient information, including any reproducible test cases requested by Orkes; and (C) (for P1 and P2 Incidents) Customer has designated personnel resources to provide necessary diagnostic information until a fix or workaround is made available.


    Article 4

    Exclusions

  5. Notwithstanding anything to the contrary in this Policy or the Cloud Services Agreement, Orkes is not obligated to address a Support Ticket when: (a) the Support Ticket is caused by Customer’s negligence, hardware malfunction, network latency or causes beyond the reasonable control of Orkes; (b) the Support Ticket is caused by third party software not

    managed by Orkes as part of the Services; (c) the Support Ticket is caused by Customer’s use of the Services with clients or web browsers other than those expressly designated by Orkes in writing; (d) the Support Ticket is caused by the Customer Cloud or any changes to or deviations from the Orkes-Specified Cloud Settings; or (e) Customer has not paid the Services or Support Services fees when due.


    Article 5

    Changes to Support Services

  6. This Policy may be updated from time to time at Orkes’ sole discretion, provided that any such updates will not materially reduce the level of Support Services during the period for which Customer has purchased Support Services