What is a Single-tenant?
As a general rule, companies in Pipefy are hosted in a multi-tenant environment, which could be translated by saying that they all coexist and run their processes, automations, integrations, and so on in a single, unified cloud.
In that scenario, all the available resources in Pipefy are equally distributed among all companies but if one or more happen to make unusually large requests (such as a massive card import that triggers several automation jobs), the other companies may suffer from it since all automation jobs in the multi-tenant environment are added to the same processing queue.
In a single-tenant scenario, a company “purchases” its own cloud and, therefore, will no longer divide resources and processing queues with other companies, ensuring greater stability and lesser risk of slowness or latency caused by other companies in the same environment.
Multi-tenant vs Single tenant
Multi-tenancy means that a single instance of the software and its supporting infrastructure serves multiple customers. Each customer shares the software application and also a single database. Each tenant’s data is isolated and remains invisible to other tenants. The separation of data is logical. Most Pipefy customers use our multi-tenant offering that is accessible through https://app.pipefy.com/
In single-tenancy, a single instance of the software and supporting infrastructure serves a single customer. Each customer has his or her own independent database and instance of the software. Essentially, there is no sharing happening with this option. The separation is physical.
What are the benefits of Single-tenant?
- Lesser risk of instabilities, latency, or slowness;
- Faster API updates;
- Maintenance and/or improvement deploys can be scheduled according to the company’s availability;
- The company can select an AWS, Google Cloud, Azure, or IBM Cloud instance in a country of its choice to abide by local/global regulations;
Who’s it for?
- Companies that use API, integrations, or features such as automation rules heavily;
- Companies seeking a better overall platform performance;
Single Tenant Requirements
Before requesting a quote for a single-tenant environment for your company, there are some information requirements you’ll need to gather. Check them out in the table below:
|Your company information||If you’re already using Pipefy in the multi-tenant environment, company name, ID, members, current plan, etc.||Yes|
|Company location||Based on where your company (or most of your users) is located, our team can define the best location to house your environment to offer you the best response time.||Yes|
|Desired domain||<company-name>.pipefy.com or any other one that fits your needs.||Yes|
|Number of users||The number of users that are going to use your company’s Pipefy single-tenant environment.||Yes|
|IP address restrictions||If your company’s security team follows strict rules that restrict access to one or more IP addresses.||No|
|Maintenance windows dates||When running maintenance in your single-tenant environment, we may need to make it unavailable for a few minutes.||No|
|Data migration||If your company already uses Pipefy’s multi-tenant and you’d like to transfer the data to your new single-tenant environment, we’d need to schedule a date to assess the amount of information to be transferred as well as the data migration.||No|
|SSO integration||Our team needs to know whether your company requires any type of custom integration for authentication.||No|
Single Tenant Deliverables
- Single-tenant Pipefy will provide a network isolated group of apps and data services with a dedicated runtime environment, provisioned in a geographic region you specify.
- This provides enterprise-grade secure network topologies and enables your Pipefy applications to securely connect to on-premise systems on your corporate network and other cloud services.
- Customers can choose an AWS, Google Cloud, Azure, or IBM Cloud location in their preferred country to meet regulatory and compliance requirements.
- Customized deployment plan: Defined deployment dates each month, and visibility of the changes that will be made in the new deployment.