Novulo application composition platform

After adding your selected components to the cart you can validate your composition. An AI-assisted algorithm checks if your selection can create a functional application. It will suggest the missing required components for your cart. Of course it also offers you the option to select alternatives, to achieve the best tailored result. Deployment can start when your cart reflects your requirements.

This is where the patented technology of application composition is applied. In a matter of minutes your selection will be automatically woven into a totally-integrated application model. This means integrated UI, business processes and data model. Because all components are mapped on a reference architecture they know how to integrate automatically. They merge without the need for APIs. Your company-specific application model is now transformed in a Microsoft.NET solution including the required database, deployed and pre-configured.

Your composite application is now available for use and can be personalized and configured like a line-of-business application. So access control, workflow configuration and master data can be managed. If the functionality is not meeting the demand, you can go back to composition, replace or add new components and deploy a new version of the application.

When a subset of the required functionality is not available in-store, you can develop what’s missing. Our low-code development tooling enables you to model new components. Each component is mapped on the reference architecture to facilitate the application composition process. If a certain widget, function or action is not available in the modeling environment, a new plug-in can be programmed. This enables the modelling environment to be extended without messing-up models with custom code.

New plugins, components and datasets are validated by Novulo’s quality control before they become available in-store. You are the IP owner and can choose whether you want your components to be proprietary or available to the entire ecosystem. When you choose the latter you will be rewarded for sharing through a payment system that monitors the use of your component. This quality control process ensures that all components in-store are up to par and are related properly to the reference architecture.

One of the unique aspects is that components keep their reference, so they can be updated over time if improvements are made. Components are maintained centrally by their owner and have their own development roadmap. All users of these components can benefit from this maintenance and the improvements that are made. This differentiates fundamentally from templating in traditional low-code platforms. At all times it also possible to go back to composition to add or remove functionality.