The number of Applications available for editing.
You can delete an App and create another one.
Entities represent the types of objects that the app can store in the database when designing on WIzzdi Cloud. The number of instances of each type is only limited by the available storage at runtime.
You can always define more entities outside of Wizzdi Cloud.
Wizzdi Cloud lets you arrange entities and their relationships in diagrams; for convenience, multiple diagrams are supported.
Number of custom consumed API endpoints for accessing services such as Gmail, GDrive, and PayPal.
To add a new service, you only need to import an OpenAPI file (unless it is already integrated into Wizzdi Cloud). See the walkthrough for an example.
Current Integrations include:
The number of additional Exposed API endpoints on top of the automatically created ones.
Wizzdi Cloud generates four API endpoints for each entity: Create, Read, Update, and Delete (CRUD). These endpoints are not counted against this limit.
Custom queries can retrieve data from the database using custom joins, conditions, sorting, and grouping.
A drag-and-drop visual designer (QBE) is provided.
Flows enable custom logic within applications and can be called from other flows, triggered by events, or connected to custom exposed API endpoints.
A flow consists of connected Activities that determine the sequence of actions the flow executes, including conditional branching, triggers, and more.
You can arrange multiple apps within each workspace, share workspace access with other users, and set invitee permissions.
Invitees must be Wizzdi Cloud users. They can be registered for the free plan for viewing.
New apps can clone a published app from a marketplace as a starting point. They can also import multiple apps from a marketplace and integrate entities, flows, APIs, and more into their app.
Wizzdi Marketplace has a continuously expanding selection of published solutions.
New apps can clone a published app from a marketplace as a starting point. They can also import multiple apps from a marketplace and integrate entities, flows, APIs, and more into their app.
Private marketplaces are used to control access to the apps you publish.
These are binary dependencies obtained from repositories such as Maven Central. Such external libraries can be called from flows or your externally added code.
Using systems like Artifactory, binary dependencies can be fetched from a private repository..
In Wizzdi Cloud, you can use a standard IDE to add code. The Import and Scan tool adds elements to the appropriate diagram for some element types, like Domain Model entities.
SSO providers allow your app users to register using Google, Apple, or others.
The number of Active Deployments on the Wizzdi Cloud Customers' cluster.
You can use the Docker and Kubernetes support in the code to deploy elsewhere.
If you keep your deployments active on Wizzdi Cloud, you will be charged based on your usage when you exceed the allocated resources for your plan.
Multi-tenancy is often required in SaaS (Software as a service) and other cases.
See:https://en.wikipedia.org/wiki/Multitenancy
In Wizzdi Cloud, it is available through the open-source FlexiCore Spring extension.
See: https://flexicore.io/home/service-multiple-organizations/
The limitation here refers to the number of tenants one can define in Wizzdi Cloud. When the system is deployed, there is no such limitation when using the provided APIs, services, and Wizzdi User Management front end.
FlexiCore is a Wizzdi Open-Source Spring Boot extension (https://flexicore.io).
It controls dynamic run-time access to data and API endpoints through Tenant, Role, and User management.
In addition, it includes support for run-time plugins.
Wizzdi Cloud itself is based on FlexiCore.
The limitation refers to the number of roles defined in Wizzdi Cloud
One can add any quantity of Roles using external changes to the code.
The number of virtual CPUs allocated if deployed on Wizzdi Cloud.
The number of GB available for storage. This includes the database and the size of the object storage (MinIO)
The number of Terabytes transferred into and from the App.
