SaaS Workflow: Multi-Tenant

Intuitive, Powerful, Embeddable .NET BPMS/Workflow for End Users & OEMs

.NET Multi-Tenant Workflow

FlowWright is the only .NET BPM/Workflow software that is truly SaaS-ready. FlowWright is designed to be fully multi-tenant capable out-of-the-box. FlowWright can be deployed in the cloud, in a private cloud, or on-prem. FlowWright supports Saas with a clear separation of database for each tenant – a requirement for most industry verticals, especially where compliance is important: customers data cannot be stored in the same database.

In a multi-tenant architecture, multiple instances of an application operate in a shared environment or an application domain. In this architecture, each tenant is integrated physically but is logically separated from other tenants: a single instance of the software will run on one server and serve multiple tenants. In this way, a software application in a multi-tenant architecture can share a dedicated instance of configurations, data, user management and other properties such as data types, steps, event handlers, form UI controls, etc. – but each tenant has a separate database with data unique to each end-user.

Multi-tenancy applications can share the same displays, rules, components -- although users and tenants can customize some of these to an extent (e.g., database schemas.)

FlowWright’s Saas/Multi-tenant approach includes the following:

Multi-tenant manager – a separate UI to manage tenants
Tenant host – each tenant is identified by a host
Tenant manager – supports pushing configuration changes to all or specifically selected tenants

FlowWright Saas/Multitenant architecture looks as follows:

FlowWright supports distributed servers tenant loads can be also distributed: Server 1 can process Tenants A, B & C while Server 2 can be configured to process Tenant X & Y. For applications that serve multiple customers, SaaS/Multi-tenant capabilities, as described, are a must-have.

FlowWright’s ability to accommodate OEM SaaS provider and End-User architectures mean that custom items that you may build can be deployed once and then used by every tenant within the SaaS/multi-tenant environment.

FlowWright provides an out-of-the-box API that is specific to management of multi-tenant environments, such as creating tenants, disabling tenants, resetting tenants, etc. And FlowWright includes out-of-the-box workflow steps to enable automation of common SaaS-related actions involving tenants.