| 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: August 10, 2026
ANNEX IV — SINGLE TENANT
This Annex governs access to and use of Single Tenant (“ST”) for data processing within the Pipefy Solution and applies only when such service is purchased. “Single Tenant” consists of isolating the Customer’s database in a private instance, i.e., separate from the Cloud shared with other Customers.
1.1. The Customer will have access to monthly usage monitoring via the Pipefy Solution’s Admin Panel, where it can track, in real time, the number of users and automations. If the Customer exceeds the limits of its contracted Plan, excess amounts will be recorded in the panel and billed retroactively, on a ‘pay-as-you-use’ basis. As set forth in Clause 13.6 of the Terms, the Customer may request, with 30 (thirty) days’ advance notice, access to additional reports. Availability of such reports will be subject to a technical and operational feasibility review, as well as any associated additional costs.
1.2. The Customer’s choice of cloud service provider (“Cloud”) and the region where Pipefy’s infrastructure operates may affect the classification of the contracted plan, due to cost variations associated with these choices. Accordingly, any changes related to the Cloud and/or region may result in adjustments to the plan, in order to properly reflect the additional or reduced costs resulting from such choices.
2. Staging Environment
a) All plans include an intermediate organization where API call volumes and automation jobs will be excluded from billing calculations.
b) The Automation Sub-processor does not include a staging environment, and test usage cannot be excluded from billing calculations, as there is no efficient way to separate it.
3. Resilience
A. The Pipefy architecture is highly available and leverages fault-tolerant architecture across up to 3 availability zones in a region.
B. Pipefy can be configured in any region where Pipefy’s Cloud Sub-processor is available, as chosen by the Customer.
C. Backups are stored in the same designated region.
D. Full database backups (“Code”) are performed once every 24 (twenty-four) hours.
E. Each backup is retained for up to 7 (seven) days in the same designated region.
F. Records: retained for up to 5 years. These logs cannot be restored. The Customer may open a ticket with Pipefy, which can help provide audit-log details of such backups.
G. Any changes made on the Web (such as field deletions) can be safely restored via a support ticket within up to 180 (one hundred eighty) days of the occurrence.
4. Pricing and Availability. ST plans may be purchased on a monthly, annual, or multi-year basis, as set forth in the Order Form, or on a ‘pay-as-you-use’ basis. Under the ‘pay-as-you-use’ model, the amount due will be calculated monthly based on actual infrastructure usage and billed retroactively, together with a fixed monthly administrative fee to keep the environment operating.
5. General Provisions
5.1. Updates. Pipefy may update this Annex or the ST services periodically, due to, among other reasons, changes in law or regulatory requirements, security or protection reasons, circumstances beyond Pipefy’s reasonable control, changes arising from the 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, via email or in-product notification. All other changes will take effect as soon as they are published on our website.
5.2. Updates to Contracted Limits. Pipefy may adjust the operational limits of contracted plans or implement modifications to the Terms of this Annex to meet Customer needs and the ongoing development of the Solution. Such changes will be communicated to the Customer with 30 days’ advance notice.