JFrog Premium Availability (99.99%) Addendum
Last Updated: February 1, 2026
This JFrog Premium Availability Addendum (this “Addendum”) is effective as of the date last signature on the Order Form purchasing JFrog Premium Availability (“Effective Date”), and is hereby incorporated by reference into and made part of the Customer’s agreement with JFrog, and together with Order Form(s), Statement of Work(s) and any other applicable addenda, schedules or amendments constitute the entire agreement by and between JFrog and Customer (collectively, the “Agreement”). JFrog and Customer may be referred to in this Agreement, individually, as a “Party” and collectively, as the “Parties”. Undefined terms will have the meaning set forth in Customer’s agreement with JFrog.
- DEFINITIONS
- “Covered Services” means collectively the following six (6) core services (i) JFrog Artifactory; (ii) JFrog Xray; (iii) JFrog Distribution; (iv) JFrog Curation; (v) JFrog Advanced Security (JAS); and (vi) JFrog AppTrust. Covered Services are measured on a collective basis and on a per instance basis. For customers who have purchased a subset of the available services, ‘Covered Services’ refers specifically to the collective subset of Covered Services purchased.
- “Downtime Minute/s” means the aggregated monthly minutes during which the Covered Services are not available to the Customer, measured by Error Rate. If the Error Rate exceeds 90% for a given minute interval, that minute constitutes a Downtime Minute. Occasional failures or high latency that do not result in a 90% failure rate for a full consecutive minute do not constitute a Downtime Minute. Downtime Minutes do not include (i) periods where the Customer retains external connectivity to the service’s API endpoints, regardless of the performance or latency of specific requests, and (ii) minutes excluded according to Section 2(b) below.
- “5xx Server Error” means any HTTP status code in the 500–599 range based on JFrog’s system of record returned by the Covered Services in response to a Valid Request, indicating that the Covered Service failed to fulfill the request due to an internal error or service unavailability. 5xx Server Error excludes any errors caused by the Customer (known as ‘4xx errors’) or other exclusions included in this Addendum or the Agreement.“
- “Error Rate” means the total number of 5xx Server Errors via API Calls returned by the Covered Services in JFrog’s system of record divided by the total Valid Requests during a measurement interval, expressed as a percentage as follows:
Error Rate = Total 5xx Server Errors x 100 Total Valid Requests - “Monthly Fee” means one-twelfth (1/12th) of the Customer’s annual Subscription fee for the applicable Subscription purchased by the Customer.
- “Monthly Uptime Percentage” means the following calculation:
Monthly Uptime % = Total Minutes in Month – Downtime Minutes x 100 Total Minutes in Month - “Uptime” means the total number of minutes in a calendar month minus the number of Downtime Minutes.
- “Valid Request” means any HTTP request sent to the Covered Services that conforms to the Documentation and is not rejected due to client-side errors such as authentication failures, permissions issues, or malformed syntax (known as ‘4xx errors’).
- UPTIME GUARANTEE.
- Subject to the terms and conditions of the Agreement and this Addendum, and solely during the applicable Subscription Term, JFrog will use commercially reasonable efforts to ensure the Monthly Uptime Percentage will be no less than 99.99% for the Covered Services during any calendar month (“Uptime Guarantee”). The availability of the Covered Service excludes any Covered Services unavailability due to any of the exclusions listed in the Downtime Minutes definition.
- Downtime Exclusions. The following events or conditions will not be considered Downtime Minutes and will be excluded from the calculation of the Monthly Uptime Percentage
- Maintenance & Lifecycle Events. Any unavailability, suspension, or termination of the Covered Services resulting from maintenance activities, including but not limited to: (i) periods of planned maintenance, upgrade, update, transition, migration, emergency maintenance, infrastructure upgrades, or software updates; (ii) the Provisioning Period; (iii) the reverse migration out of the Premium Availability environment.
- Third-Party Technology. Failures, delays, or outages caused by: (i) Third-Party Integrations; (ii) third-party infrastructure or cloud platform providers (including but not limited to AWS, Azure, or Google Cloud), including without limitations, migration between cloud platforms/providers initiated by Customer; or (iii) internet service provider (ISP) failures or general internet congestion.
- Customer Causes. Downtime caused by: (i) Customer’s use of JFrog Cloud or the Cloud Feature in a manner not authorized in the Agreement, this Addendum or not in accordance with the Documentation; (ii) issues resulting from Customer’s equipment, software, or other technology, or from Customer’s use of the service in breach of the Agreement; (iii) Customer-initiated configurations, excessive loads, or usage that exceeds standard quotas or fair use policies. For the sake of clarity, all issues resulting from Customer’s continued use of the service without implementing modifications advised by JFrog will not be considered Downtime Minutes.
- Force Majeure Events and Self-Hosted Features. Failures, delays or outages caused by Force Majeure Events and/or Self-Hosted Features.
- Suspension or termination of access. Any suspension or termination of access to the JFrog Platform by JFrog pursuant to the Agreement.
- CREDITS
- The Customer will be eligible to receive credits for any failure of JFrog to meet the Uptime Guarantee. The credit is an amount equal to a percentage of the applicable Monthly Fee for the Covered Services, in accordance with the following table:
Monthly Uptime Percentage Credits Percentage < 99.99% – ≥ 99.9% 5% of Monthly Fee < 99.9% – ≥ 90.0% 25% of Monthly Fee < 99.0% 100% of Monthly Fee - If Customer’s multiple Instances are affected by Downtime Minutes, the total credits for all affected Instances will be cumulative. Credits will be calculated solely based on the portion of the Monthly Fee attributable to the specific Instance or Instances that failed to meet the Uptime Guarantee. In this regard, the Monthly Fee will be prorated equally among the total number of affected Instances covered by the Customer’s Subscription during the applicable month. The credits for affected Instances are calculated as follows:
Credit = Number of Affected Instances x Monthly Fee X Applicable Credit Percentage Total Number of Instances For the avoidance of doubt, if multiple Instances experience Downtime Minutes, the credits are calculated individually for each affected Instance and then summed. In no event will the total aggregate credits issued to Customer in any single calendar month exceed 100% of the total Monthly Fee paid by Customer for that month.
- Credits are JFrog’s sole obligation and liability and Customer’s sole and exclusive remedy for any failure of JFrog to meet the Uptime Guarantee. Customer will not be entitled to receive credits if (i) Customer is in breach of the Agreement (including payment obligations); or (ii) the Downtime Minutes occurred while Customer’s access to the Covered Services was suspended by JFrog in accordance with the Agreement.
- Claim Procedure. To receive credits, Customer must notify JFrog in writing to service@jfrog.com within thirty (30) days following the end of the calendar month during which JFrog did not meet the Uptime Guarantee. Failure to comply with this requirement will forfeit Customer’s right to receive a credit. JFrog will verify the claim using its standard system logs and monitoring tools. JFrog will be the final authority in determining whether the Uptime Guarantee was met. Credits may only be applied toward a Customer’s future Monthly Commitment and cannot be transferred or applied to any other entity.
- Failure to meet the Uptime Guarantee will not constitute a material breach of this Agreement
- The Customer will be eligible to receive credits for any failure of JFrog to meet the Uptime Guarantee. The credit is an amount equal to a percentage of the applicable Monthly Fee for the Covered Services, in accordance with the following table:
- PREMIUM AVAILABILITY MIGRATION
- Provisioning Period. “Provisioning Period” means a two (2) week period commencing on the first day of the migration of Customer Data and configurations to the Premium Availability environment. The Provisioning Period includes all setup and migration activities. The Parties will mutually agree upon the migration start date within fifteen (15) days of the Effective Date. Customer acknowledges that: (a) the Premium Availability Uptime Guarantee will not apply during the Provisioning Period; (b) Customer’s Instance of the JFrog Platform will be unavailable during the Switch Over to the Premium Availability environment. “Switch Over” means the final operational transition that commences on the conclusion of the Provisioning Period and continues until the migration to the Premium Availability environment has been successfully completed.
- Version Alignment and Upgrades. Customer acknowledges that migration to the Premium Availability environment requires automatic upgrade of the Customer’s JFrog Platform to the most current generally available software version, and accepts the latest version’s features, functionalities, and interface as of the Switch Over period.
- Reverse Migration. Upon termination or expiration of Customer’s use of the Premium Availability service, if the Customer continues to retain a JFrog Subscription without Premium Availability, then JFrog will perform a reverse migration of Customer Data from the dedicated Premium Availability environment to the standard shared environment at a time that is mutually agreed upon by the Parties. Customer acknowledges that the Customer’s Instance of the JFrog Platform will be unavailable during the reverse Switch Over Period.