Welcome #

Wizzdi Cloud simplifies and accelerates application development by enabling users to deploy products anywhere without code dependencies.

1. You Built It; You Own It: Wizzdi Cloud differs from almost all no-code platforms because it doesn’t restrict users to its ecosystem. After creating an App with Wizzdi Cloud, you can deploy it elsewhere. You can take your code and work on it independently without returning to Wizzdi Cloud. Choose to modify or build upon your project outside of Wizzdi Cloud. You can do so easily. Especially with the Spring Boot runtime, your code will be free from Wizzdi-specific dependencies, ensuring standard coding practices are maintained. Once you choose to develop outside the Wizzdi Cloud while keeping the use of Wizzdi Cloud available, the system automatically integrates any external code, allowing you continuous access to Wizzdi Cloud’s advanced visual tools.
2. Wizzdi Cloud provides a comprehensive, no-code backend development platform; front-end development is coming soon. Here’s what it offers:
   1. Quality Assurance: The backends created are top-notch, aligning with industry standards.
   2. Flexibility: Wizzdi Cloud is feature-rich yet flexible. Backend systems can optionally be refined and extended outside the system.
   3. Tailored Solutions: While the platform caters to a wide range of needs, specific requirements might arise based on an organization’s unique technical background. Wizzdi Cloud is designed to be a starting point, allowing for such external enhancements. However, accessing standard libraries and code is supported in the platform, including a code editor for users preferring to code some parts of the system.
   4. Risk-Free: Choosing Wizzdi Cloud carries no risk. It serves as a robust foundation, ensuring that users have the flexibility to expand and enhance their projects as required.
3. AI integration: Wizzdi Cloud offers seamless integration with ChatGPT, allowing users to transition from problem descriptions to diagrams easily. ChatGPT integration is available in someplace and will be expanded in subsequent versions.
4. Deployment: Users can transition from diagrams to deployment on the Wizzdi customer high-availability cluster without coding. They can also pull their code and deploy it elsewhere using the Docker script.
5. UI Builder: A UI builder tool will be available in H1 2025. Wizzdi Cloud User Interface builder is designed to create Google Flutter-based mobile and web applications.
6. Hosting Options: The backend system can be hosted on-premises, in a user’s cloud, or the Wizzdi Cloud. It includes a one-line Docker boot option for easy deployment of Linux, Windows, and Mac.
7. Repository Integration: The platform integrates with popular repositories like GitHub, GitLab, and Bitbucket.
8. Development Patterns: Wizzdi Cloud supports multiple development strategies: full no-code development, a combination of no-code with traditional development, or using the no-code system as an assistant tool in the development process. This allows Wizzdi Cloud to contribute to the code base like any developer.
9. Reusability: Wizzdi Cloud is intended to facilitate reuse on a broad scale. This encompasses projects created by yourself and others using Wizzdi Cloud and the ability to access available artifacts from private or public repositories such as Maven Central, which houses over one million software artifacts.
10. External Services: Wizzdi Cloud includes extensive support for accessing services such as Google, SendGrid, and others; additionally, it supports importing the definitions for every available external service.
11. MarketPlaces: Wizzdi Cloud supports public and private marketplaces. When apps are published to a marketplace, eligible users can clone or import them into any of their workspaces and use some or all of the app elements in their apps.
12. Runtimes and Multi-tenancy: Wizzdi Cloud has three run-times: Pure Spring Boot, FlexiCore Boot, and FlexiCore. FlexiCore Boot and FlexiCore are extensions of Spring and come with an integrated multi-tenancy system. This system allows role-based access control to both data and API endpoints. Both are open-source and can be found on FlexiCore.The multi-tenancy in FlexiCore enables authorized users to combine data from different tenants and supports hierarchical structures. However, the Pure Spring run-time doesn’t have this multi-tenancy feature. All FlexiCore-based run-times work with standard Spring Boot libraries and development patterns.
13. Security In pure Spring runtime: Role-based access to API endpoints is also supported, and optionally so, users have access to data they have created only. App builders can define the roles and their access to the API endpoints.
14. New features and bug tracking: Use the TODO support to allow stakeholders to describe new features and report bugs in your Apps. The unique backtracing feature tracks all the changes related to a specific TODO.
15. Metrics: Support Spring Metrics. Spring Metrics is a feature of the Spring ecosystem that provides powerful tools for monitoring and managing application performance and behavior. It is often used with tools like Micrometer, Prometheus, and Grafana to collect, store, and visualize application metrics.

Note On Hierarchical Multi-Tenancy: 

Hierarchical multi-tenancy refers to a structured, tree-like organization of tenants within a system. Unlike the traditional flat model, where all tenants are at the same level, the hierarchical approach allows for nested multi-tenancy. In the context of Wizzdi Cloud and its support for hierarchical multi-tenancy, tenant administrators can create additional tenants within their primary tenant. This nesting can occur to any depth, depending on the organization’s needs, application, and system policies. For instance, consider a large organization that operates globally. The top-level tenant could represent the global enterprise. Beneath that, regional tenants could be created for North America, Europe, Asia, etc. Within the Europe tenant, further sub-tenants could be established for individual countries like France, Germany, and the UK. And even within those country-level tenants, you could have more granular tenants representing different departments or offices. Any users granted the correct permissions, such as an administrator of a tenant, can access the data on the tenants created in the tenant he administrates and ‘below’.