Software As a Service Agreement
Software as a Service Agreement
IMPORTANT – YOU SHOULD CAREFULLY READ THESE TERMS OF SERVICE (THE “AGREEMENT”) BEFORE USING OR ACCESSING THE PFLB LOAD TESTING PLATFORM SERVICE (THE “SERVICE”) PROVIDED BY PFLB, INC. (“PFLB”), A DELAWARE CORPORATION, AVAILABLE THROUGH PFLB’S WEBSITE LOCATED AT https://pflb.us. BY ACCESSING THE SERVICE FOR PERSONAL USE, THIS AGREEMENT APPLIES TO AND BINDS YOU PERSONALLY. IF YOU ARE ACCESSING THE SERVICE AS PART OF YOUR WORK FOR AN ORGANIZATION, THIS AGREEMENT APPLIES TO AND BINDS SUCH ORGANIZATION AND THE PERSONS ACCESSING THE SERVICE ON BEHALF OF THE ORGANIZATION. AS USED IN THIS AGREEMENT, “CUSTOMER” WILL REFER TO THE PERSON, ORGANIZATION, AND THE PERSONS ACCESSING THE SERVICE ON BEHALF OF THE ORGANIZATION. BY ACCESSING OR USING THE SERVICE, YOU, AND THE ORGANIZATION, AS APPLICABLE, AGREE TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO BE BOUND BY THIS AGREEMENT, THEN YOU SHALL NOT ACCESS OR USE THE SERVICE.
SAAS Listing
This document provides standards and features that apply to the PFLB Software as a Service (the “Service”) provided to the Customer by PFLB, Inc. (“PFLB”) and defines the parameters for the Service that pertain to the following:
The standards and features that apply to the Service, and related terms and conditions, may be updated from time to time by publication on PFLB’s website.
The following is an explanation of the Authorized Use Limitation metrics that may be used in PFLB’s order form:
Feature | Metric | Concurrent Variable Units | Variable Unit Hours |
---|---|---|---|
Performance Test | 1 Virtual User | 1 | 1 |
API Monitoring / API Functional Test | 1,000 API calls (per 24 hour period) | 5 (resets every24 hours | 5 |
Test Data | Per Test, Per Mock Service and Transaction | + 50% * | + 50%* |
For Example:
If the Customer runs a Performance Test with 5,000 Virtual Users (5,000 Variable Units) and uses Test Data with that Performance test, the charge for Test Data is 2,500 Variable Unit Hours for a total charge of 7,500.
Term Subscriptions. Customer may subscribe for a term with set Authorized Use Limitation and pricing as set forth in an applicable order form. Any use in excess of the Authorized Use Limitation shall be invoiced by PFLB for the overage and at the contract rate set forth in such order form. Any overage will be included in the Authorized Use Limitation for the remainder of the Subscription Term. There are no refunds for unused capacity.
Versions: PFLB will provision the Customer with the latest version of the Service that is generally available. PFLB may, from time to time, modify the Service and add, change, or delete features of the Service, without notice to the Customer. Customer’s continued use of the Service after any such changes to the Service constitutes acceptance of such changes. PFLB will make reasonable efforts to provide information to the Customer regarding material changes to the Service.
PFLB commits to the Service Level Availability (“SLA”) as indicated in the table below for the Service during the Subscription Term of the Service. In the event that the SLA committed decreases below the “Threshold for Service Availability Default” as set forth below, Customer may be entitled to take action as outlined herein. PFLB reserves the right to revise the SLA set forth below upon providing thirty (30) days advanced written notice to the Customer. Please note that SLA commitments are not offered for free plans of the Service.
Threshold for “Service Availability Default – Minor” | Threshold for “Service Availability Default – Major” |
99.8% | 98.5% |
PFLB measures SLA targets as described below:
SLA Exclusions: The SLA does not apply to faults originating from the use of any open-source libraries included by Customer. SLA measurement does not include planned outage time periods.
Planned outage time periods are defined as downtime of the solution availability for periodic and required maintenance events where PFLB provides notice to Customer up to 72 hours prior to the planned maintenance window.
PFLB reserves the right to make reasonable changes to this measurement procedure.
Usage of the Service is limited based on the terms set out in the agreement. If this limit is exceeded, PFLB will notify Customer so Customer may reduce its usage. In the event Customer exceeds the Usage Limit, PFLB may suspend, or throttle down, the Service until Customer is in compliance.
The Customer will not (a) use the Service to store or transmit infringing, libelous, or otherwise unlawful or tortious material, or to store or transmit material in violation of third-party privacy rights, (b) use the Service to store or transmit computer instructions that self-replicate without manual intervention, such as viruses, worms or Trojan horses, (c) interfere with or disrupt the integrity or performance of the Service or third-party data contained therein, (d) attempt to gain unauthorized access to the Service or its related systems or networks, (e) permit direct or indirect access to or use of the Service in a way that circumvents a contractual usage limit, or (f) use the Service to cause tests to be executed against endpoints not owned by the customer.
Customer and confirmed by PFLB that the Service has been unavailable below the major default threshold, measured on a monthly basis during three (3) consecutive months, then the
Customer has the right to terminate their subscription to the Service without incurring any additional charges or termination fees. The waiver by PFLB of further fees shall be Customer’s sole and exclusive remedy for termination due to failure to adhere to Service Level Availability and PFLB shall have no further liability to the Customer.
PFLB may, at its sole discretion, suspend service without refund if (1) Customer interferes with or disrupts the integrity of SaaS or the data contained therein, or (2) uses SaaS in order to cause harm such as overload or create multiple agents for the purpose of disrupting SaaS or third-party operations.
All Customers of the Service offering shall have their data backed up on a daily basis. Data loss is limited to less than 26 hours in the event of a primary data center disaster. For the PFLB on premise components PFLB is not responsible for data backup.
The Service uses Multi-Region Replication as its primary Disaster Recovery strategy. Utilizing a high availability architecture for all tiers, including the database, PFLB also provides a standby site in an alternate region, thus providing failover capabilities for disaster recovery.
Recovery Time Objective (RTO) | Recovery Point Objective (RPO) |
24 hours | 26 hours |
“Recovery Time Objective” or “RTO” is defined as the duration of time within which the Service must be restored after a major interruption or incident.
“Recovery Point Objective” or “RPO” is defined as the maximum period in which data might be lost from the Service due to a major interruption or incident.
Unless stated in another agreement, support and maintenance includes the following support:
PFLB Blog and Knowledge Base are community sites that, among other things, allow users to network, work together, share thoughts, and offer suggestions on how PFLB can do more to improve your experience using the Service.
The order form or transaction document identifies the type of Maintenance included as part of the PFLB SaaS Subscription, the duration of such Maintenance (the “Maintenance Term”), and the applicable fees for SaaS Maintenance of the Available Functionality.
Service Level Objectives | |
Severity | Initial Response Time |
1 – Catastrophic | 30 Minutes |
2 – Severe | 30 Minutes |
3 – Non-Critical | 4 Hours |
4 – Minor | 8 Hours |
5 – Information Request | 8 Hours |
6 – Feature Request | 1 Business Day |
Severity Level Definitions | ||
Severity | Definition | Expected Resolution |
1 – Catastrophic | Causing downtime or preventing the complete system from functioning | Subscription Service availability is restored. |
2 – Severe | Causes downtime of significant functionality or significantly affects the major portion of the system’s capacity | A satisfactory workaround is provided, a patch is provided, and a fix is incorporated into future releases. |
3 – Non-Critical | Effects non-critical functionality or causes downtime of a non-critical part of the system capacity | A satisfactory workaround is provided, a patch is provided, and a fix is incorporated into future releases. |
4 – Minor | Minor problem that does not impact the service | A satisfactory workaround is provided, a patch is provided, and a fix is incorporated into future releases. |
5 – Information Request | Routine Questions, general guidance, or configuration inquiries | The answer to the question is provided by Support through an open case |
6 – Feature Request | Request for a new feature or enhancement to the product | The feature is incorporated into future releases: Developer’s Site update |