Comparing MDriven with alternatives
This page was created by Wikiadmin on 2026-07-29. Last edited by Wikiadmin on 2026-07-29.
You can use this guide to compare MDriven with other application-development options when selecting a platform for a business application.
Compare MDriven with alternatives
Compare products against the same business scenario. For example, evaluate how each option supports an invoice-approval application that needs data modeling, approval rules, a web user interface, integrations, and controlled access to invoice data.
MDriven is a model-driven development platform. You define business data, rules, and workflows in a visual model using UML (Unified Modeling Language), then use that model to build and evolve an application. MDriven Designer is the visual modeling tool used to create the model.
Comparison criteria
Use the following criteria for every product under consideration. Record the evidence, edition, deployment assumptions, and any implementation work required for each answer.
| Criterion | What to verify | MDriven information to evaluate |
|---|---|---|
| Business logic and data model | Can you represent business data, rules, and workflows in a shared model? | MDriven uses UML to define data and logic in a visual model. The model represents business operations and supports collaboration between business stakeholders and developers. |
| Application generation | Which application parts are generated or synchronized from the model? | MDriven automates database generation, UI creation, and business-logic enforcement. |
| Change management | What must you change when a business rule changes, and what must be rebuilt or rewritten? | Its executable model also provides documentation that follows system functionality. |
| Collaboration | Can business analysts and domain experts review and contribute to the system definition? | MDriven's visual models are intended to make business logic available for review by both business stakeholders and developers. |
| Integration and deployment | What integration, deployment, and hosting options fit the existing environment? | MDriven is described as working alongside legacy systems and supporting cloud deployment. |
| Access control and information exposure | How are access decisions enforced, and how much implementation detail reaches the client? | A ViewModel sections information for a specific need. AccessGroups and ViewModel-Enable provide managed analysis of expressions that can affect persistent data. |
| Scale and operations | What is included for availability, replication, caching, load balancing, and failover? | Confirm which capabilities are required for the application and included in the selected plan. |
| Pricing and commercial terms | Is pricing free, usage-based, annual, or custom, and what usage or support assumptions apply? | The Free plan has a maximum of 50 classes and runs only on your own device. Pay as You Go uses MCoins, where 1 MCoin equals 1 €, has a minimum monthly commitment of 10 €, and includes 70 free MCoins per month. Business Critical is an annual license with a custom quote; Enterprise is custom. |
Run a like-for-like evaluation
- Define one representative workflow. For example: create an invoice, route it for approval, prevent unauthorized changes, and show each user only the information needed for their role.
- List the data, rules, user interactions, integrations, deployment constraints, and access requirements before building anything.
- Build or request the same proof of concept in each shortlisted option.
- Measure the work needed to define the data model, implement the approval rule, create the user interface, configure access, and deploy the application.
- Record what is model-defined, generated, manually coded, configured, or supplied by external components.
- Compare the resulting operating assumptions, including plan limits, usage costs, support commitments, deployment restrictions, and required specialist skills.
Questions to ask each vendor
- Which parts of the application are generated, and which parts require manual implementation?
- How does the platform keep the data model, user interface, business rules, and documentation aligned after a change?
- Can business stakeholders review the rules that govern the workflow?
- How is authorization applied to data and actions?
- Which deployment options are available for cloud, local-device, and restricted-network environments?
- Which plan includes the required scale, availability, support, and licensing terms?
- What measurable scope can be completed during an evaluation period?