Bizagi Platform as a Service (PaaS) provides all the power of the Bizagi Digital Business platform directly in the cloud.
For introductory information about Bizagi PaaS and its benefits, refer to Bizagi PaaS overview.
PaaS architecture and access
Bizagi PaaS provides an isolated private Cloud for each customer, that is not shared with other customers.
Each private cloud contains all of the testing and production environments required, on ready-to-use architecture with no technical or time barriers, that can only be accessed by authorized users. Access control is integrated with the identity management system of the client (AD, LDAP).
Each paid customer is assigned a unique URL with their subscription (companyname.bizagi.com having an additional prefix).
URLs are published for internet access.
A subscription admin accesses, controls and manages the subscription, so that each environment has separate resources which translate into an independent URL, as described below.
•Testing environment URL:
•Production environment URL:
For more information about the service's architecture, refer to Bizagi PaaS architecture.
Bizagi PaaS charges in a pay-for-what-you-use fashion, based on the Performance Level chosen per environment (which can be modified dynamically to match demand).
There are no limits on the number of end users, nor on the amount of deployed applications.
The customer may also request the activation of environments others than those considered by default (for instance, requesting a staging or pre-production environment).
If the customer scales up or adds new environments, Bizagi will then invoice the yearly prorated fee.
An environment is a set of resources provisioned in order to support a given stage of the customer applications' life cycle.
For Bizagi PaaS, default offered environments are Testing environment and Production environment.
The Authoring (development) environment is usually located on-premises.
The product used in the authoring or development environment (Bizagi Studio), can be downloaded at no cost and directly from www.bizagi.com, and installed on local machines.
Authors then use Bizagi Studio in this environment, with all of the functionality it has available, as described in the General product documentation.
To view the general product documentation, refer to http://help.bizagi.com/bpm-suite/en/.
Once applications are built, they can then be deployed by the customer in target Testing or Production environments running in the cloud.
This last part is done with via an easy-to-use and web-based UI that only requires a browser.
In case the customer does not have the necessary infrastructure in place to set up an on-premises Development environment, a subscription to a cloud-based development environment is available as well.
The cloud-based Development environment provides the necessary infrastructure and tools for a team of authors to work on the applications implementation.
All applications are stored in a cloud repository, allowing authors to collaborate and validate how these applications execute (from early development stages, as in a quick-prototyping mode).
The cloud-based Development environment is provisioned with separate access accounts according to the number of authors (e.g. 5, 20, 50 authors).
The Testing environment is used to conduct user-acceptance tests of any number of applications previously built in the development environment.
Customers can request one or more Testing environments for user-acceptance tests.
To request an environment the customer must specify a Performance Level that fits their needs and budget.
Note that the customer is responsible for both developing the applications, and for deploying them in the Testing environment.
Deployment of applications is done by using a web-based UI and it does not represent IT or technical steps for the customer (i.e, only uploading a file packaging the applications from the development environment).
The Production environment is used to run the applications and make them live and available to end users (for production usage).
Note that just as with Testing environments, this Production environment is requested by specifying a Performance Level that matches demand for its specific use.
Recall that the Performance Level can be scaled up or down at any time.
Similarly as with the Testing environments, the customer is responsible for deploying applications into the Production environment after having verified/ensured that applications behave as expected, while using the same web-based UI options for the deployment of applications.
Bizagi PaaS security
Bizagi PaaS has been designed with security as its top-most aspect in consideration.
By parting from the use of the technologies and controls that enable an isolated environment for each customer, Bizagi PaaS delivers a private cloud where customer data is not shared.
Customers choose the data centers where their data will be stored, in order to achieve higher performance and also meet with regulatory and compliance requirements.
This private cloud has further security controls and mechanisms implemented, such as identity and access management, data encryption in transit and at rest, as well as policies and procedures and standards to comply to data privacy (such as rigorous procedures regarding deletion of data upon contract termination, protected access to data both physically in data centers and for logical access as well).
For detailed information about this chapter, refer to Security.
Bizagi PaaS reliability
Bizagi is committed to delivering 99.9% SLA uptime.
To do so, Bizagi PaaS maintains replicas of databases and servers to protect against hardware failures and provide superior reliability.
Disaster Recovery options are available upon request (a separate offering), that meets with demanding RTO and RPO objectives.
For detailed information about this chapter, refer to Reliability.
Bizagi PaaS scalability
Bizagi offers a series of Performance Levels that meet even the most demanding of workloads.
Scaling up or down is done by the customer via a self-service, easy-to-use, web-based UI.
When scaling up an environment, there is no data loss and this task goes on without disrupting the service completely.
For detailed information about this chapter, refer to Scalabilty.
Management. maintenance and monitoring of the service as a whole
Bizagi PaaS is managed and operated by Bizagi.
It is powered by Microsoft Azure and leverages the best techniques and modern technologies that enable a fully qualified and trained Bizagi PaaS personnel to fulfill all the relevant tasks to provision, manage, maintain, and monitor customer environments which run mission critical applications.
Management and maintenance
Bizagi PaaS personnel (Bizagi PaaS Operations team) provision customer environments and similarly performs installation, upgrades, and overall maintenance of all required software, including the Bizagi platform, other services and components. Within management and maintenance, tasks carried out by the Bizagi PaaS Operations team consider applying patches, service packs, fixes, updates or conducting tuning.
The Bizagi PaaS Operations team conducts 24/7 monitoring of all software, services and components in the underlying technology of Bizagi PaaS.
For more information about this chapter, refer to System maintenance and management.
Self-service tasks and support
Bizagi Cloud empowers customers to perform certain tasks as self-service and via an intuitive and secure portal, while also counting on expert teams ready to carry out all the management of environments, and to provide technical support.
The customer designates authorized accounts for an admin on the customer's side, so that he/she access a web-based Management Portal offering self-service tasks (accessed with a browser, via HTTPS).
The following capabilities are offered by the Management Portal, so that the customer may use these at anytime:
•Manage the subscription (e.g, grant or revoke access rights to further users for the subscription).
•Monitor the different environments to watch over resources utilization.
•Scale up or down the Performance Level for each environment to match demand.
•Request new environments, different that those available by default.
•Deploy applications to Testing, Production or other environments (promote/publish applications).
•Upgrade the Bizagi platform version (or downgrade and rollback changes) for each of the environments.
•Use special Cloud applications targeted to extend functionality of reports, explore machine learning (AI), or enhance the experience for users by producing Stakeholder-centric portals.
In addition to the above, note that an admin on the customer's side may rely on other web pages that allow him/her to manage the accounts and roles that act as participants in applications and processes, or manage other environment settings such as: connectivity to an SMTP service, URLs and credentials for external web services integrated to the service, or similarly authentication parameters.
To learn about this portal and its option, refer to Management Portal.
Technical support is available via email, phone, and through an online ticket system.
Basic support is available during business hours, and included within the subscription contract.
In addition, customers may select additional levels of support, especially when identified necessary for requirements of applications (premium packages available to support mission critical applications).
For more information about technical support, refer to Support.