| Single Tenant Plans | |
| Plan | Plan Coverage |
| Starter | Up to 320,000 requests per day of a set of routines and programming standards for accessing a web-based software application or platform (“API”) received in Pipefy’s central infrastructure, limited to a maximum transaction per second (“TPS”) of 160 requests. This includes requests from external .NET solutions calling the Pipefy API or requests to the Automation Subprocessor calling the Pipefy API, both of which count towards the daily quota;Up to 4 million (4,000,000) automation jobs, defined as automation configurations executed in Pipefy’s infrastructure within a month;Up to 500 GB of storage for saving attachments from electronic forms or cards. |
| Corporate | Up to 500,000 requests per day of a set of routines and programming standards for accessing a web-based software application or platform (“API”) received in Pipefy’s central infrastructure, limited to a maximum transaction per second (“TPS”) of 250 requests. This includes requests from external .NET solutions calling the Pipefy API or Automation Subprocessor requests calling the Pipefy API, both counted towards the daily quota;Up to 6.5 million (6,500,000) automation jobs, defined as automation configurations executed in Pipefy’s infrastructure within a month;Up to 750 GB of storage for saving attachments from electronic forms or cards. |
| Enterprise | Up to 750,000 API requests received per day in Pipefy’s central infrastructure, limited to a maximum transaction per second (TPS) of 375 requests. This includes requests from external .NET solutions calling the Pipefy API or Automation Subprocessor requests calling the Pipefy API, both counted towards the daily quota;Up to 9 million (9,000,000) automation jobs, defined as automation configurations executed in Pipefy’s infrastructure within a month;Up to 1,024 GB of storage for saving attachments from electronic forms or cards. |
| No plan contemplates quotas for inbound or outbound traffic based on Automation Subprocessor Integrations. | |
Last updated: 12 de January de 2026
ANNEX VI – SINGLE TENANT
This Annex is an integral and inseparable part of the Pipefy Solution Terms and Conditions of Use License (“Contract”). This Annex regulates the access and use of Single Tenant (“ST”) for data processing in the Pipefy Solution and is applicable only when such service is contracted. “Single Tenant” consists of isolating the Customer’s database in a private instance, i.e., different from the Cloud shared with other Customers.
- ST Plans:
1.1. The Client will have access to monthly usage monitoring through the Pipefy Solution Administration Panel, where real-time tracking of users, and automation usage. If the Client exceeds the limits of the contracted Plan, the excess amounts will be recorded in the panel and charged retroactively under the “pay-as-you-use” model. As provided in Clause 15.6 of the Terms, the Customer may request, with 30 (thirty) days’ notice, access to additional reports. The availability of these reports will be subject to an analysis of technical and operational feasibility, as well as the application of any associated additional costs.
1.2. The Customer’s choice of cloud service provider (“Cloud”) and the operating region of Pipefy’s infrastructure may impact the classification of the contracted plan due to cost variations associated with these options. Therefore, any changes related to the Cloud and/or region may result in adjustments to the plan to appropriately reflect the additional or reduced costs arising from these choices.
2. Preparation Environment
- All plans include an intermediate organization where API call volumes and automation job counts will be excluded from billing calculations.
- Automation Subprocessor does not include a staging environment and usage for testing cannot be excluded from billing calculations as there is no efficient way to separate it.
3. Resilience
- The Pipefy architecture is highly available and leverages fault-tolerant architecture across up to 3 availability zones in a region.
- Pipefy can be configured in any region where Pipefy’s Cloud Subprocessor is available, according to the Customer’s choice.
- Backups are stored in the same defined region.
- Full backups (“Code”) of the database are performed once every twenty-four (24) hours.
- Each backup is retained for up to seven (7) days in the same defined region.
- Logs: Retained for 5 years. These logs cannot be restored. The Customer can open a ticket with Pipefy to request audit log details for these backups.
- Any changes made on the Web (such as deleting fields) can be safely restored via a support ticket within one hundred and eighty (180) days.
4. Price and Availability. The ST plans may be contracted on a monthly, annual, or multi-year basis, as specified in the Purchase Order. They may also be available in a “pay-as-you-use”. In the “pay-as-you-use” model, the amount due will be calculated monthly based on the actual infrastructure usage and charged retroactively, accompanied by a fixed monthly administrative fee to maintain the environment operational.
5. General Provisions.
5.1. Updates. Pipefy may update this Appendix or the FTS Services from time to time due to, but not limited to, changes in legislation or regulatory requirements, safety or security reasons, circumstances beyond Pipefy’s reasonable control, ongoing development of the Services, and/or to adapt to new technologies. The Customer will be notified at least 30 days in advance of any changes to these Terms that have a negative impact, either by email or by in-product notification. All other changes will take effect as soon as they are posted on our website.
5.2 Updates to Contracted Limits:
Pipefy reserves the right to adjust the operational limits of the contracted plans or amend the Terms of this Annex as necessary to address the Client’s requirements or to accommodate the ongoing development of the Solution. Any such changes will be communicated to the Client with no less than 30 days’ prior notice.