You can use this page to choose a MDriven licensing approach, understand what MCoins pay for, and estimate how hosting and model usage affect your cost.
Choose a pricing approach
MDriven offers a free option for local evaluation, usage-based payment with MCoins, and annual or custom arrangements for business-critical and enterprise use. Check the current plans and plan terms on the MDriven pricing page.
| Approach | Use it when | What it includes or requires |
|---|---|---|
| Free | You are learning, prototyping, or running everything on your own device. | You can use MDriven Designer, Turnkey Server, and a local MDrivenServer. The model is limited to 50 classes. No credit card is required. |
| Pay as You Go | You want to run in the cloud, scale usage up or down, or use a model with more than 50 classes. | Register an account and pay with MCoins. The current pricing page states that this plan includes 70 free MCoins per month and allows an unlimited number of classes. |
| Annual license | Your system is business-critical and you need an agreed annual arrangement, support commitments, or source-code-related terms. | This is billed annually and is provided by custom quote. The current pricing page lists priority support, priority bug fixing, direct developer access, guaranteed response times, and a strong SLA among its benefits. |
| Enterprise | You need an architecture or deployment arrangement beyond the standard plans. | This is tailored by custom quote. The current pricing page lists capabilities such as unlimited cores, global replication and cache servers, advanced history management, multi-database environments, load balancing and failover setup, offline license mode, complex firewall scenarios, and restricted-network deployments. |
Pay with MCoins
An MCoin is MDriven's internal payment unit; its nominal value is 1 Euro. MCoins can pay for MDriven services, including usage over time. See Documentation:MCoins for the account types, expiry rules, free-MCoin allocation, payment methods, and calendar-time alternatives.
The key effect for MDriven Designer users is model size:
- The free option has a 50-class limit.
- When you use MCoins to pay for services, the 50-class limit is removed.
- Designer usage is measured by day. A day in which you use a larger model can consume more MCoins than a day with a smaller model because class and view counts are part of the usage calculation.
For example, a developer who evaluates a 40-class model locally can remain within the free limit. If that developer expands the model to 80 classes and uses MCoins, the model is no longer constrained by the 50-class limit; the Designer charge is instead based on the measured model usage for that day.
Understand what affects usage-based cost
The current pricing page describes Pay as You Go consumption in terms of active users and CPU/memory usage. The detailed billing calculation also records model size, views, data use, site use, and end-user volume. Treat the current pricing page as the authoritative place for current rates and included services.
In practical terms, review these factors when estimating a solution:
| Factor | Meaning | Example effect |
|---|---|---|
| Sites | A site is an independently executed Turnkey application. | A SaaS solution with 50 customer-specific sites has execution cost for 50 sites. |
| Classes and views | Classes represent the size of the domain model; views represent the application views recorded by MDriven. | A larger model with more classes and views increases the measured Designer usage and can also affect site execution usage. |
| End users | The billing calculation includes an end-user-volume price component when applicable. | A site with a higher end-user count may enter a higher volume component than a small internal application. |
| Data use | The execution calculation includes used data. Data transferred from the site to clients is also relevant to hosting cost; data uploaded to the site was described as free in the original pricing explanation. | Large documents stored outside the main database can still contribute when they are transferred out from the site. |
| CPU and memory capacity | Hosted applications can require a better or less crowded tier when they need more CPU or RAM. | Moving a busy production application to more capacity can improve its resource situation and changes the hosting arrangement. |
Estimate a multi-tenant SaaS
If each tenant has its own database and runs as its own site, separate development cost from execution cost:
- Count the tenant sites. For example, 50 customers with one site each means 50 sites.
- Multiply the applicable execution price, including applicable add-ons, by the number of sites.
- Count the shared development once. If the same model is developed for all 50 customers, multiply the development price by 1, not 50.
This estimate assumes that each tenant is a separate site. Confirm the intended deployment architecture before using the estimate for a contract or budget.
Hosted service options
The following terms have been used in MDriven pricing discussions to describe hosted-service choices. Their availability and price depend on the current offer.
| Option | What it means | When it matters |
|---|---|---|
| Inclusive add-ons | Add-ons contribute to the total price. For an on-premises license calculation, the earlier pricing guidance assumed all add-ons because you control the environment and may use the additional services. | Use this as a planning assumption only; verify the current add-ons and terms in the pricing portal. |
| Better CPU and RAM | Your web application is placed in a better and/or less crowded tier. | Consider this when response time or workload requires more available resources. |
| Data out from site | Data sent down from the site to clients is included in the hosting logic. This can include large cross-referenced documents stored in a file system outside the main database. | Consider this for document-heavy applications where users download substantial files. |
| Priority support | Support requests from priority-support holders are handled before other requests. | Choose this when response priority is required for a production system. |
| Control core deployment | MDriven coordinates the time for server-software upgrades with you instead of choosing the upgrade time independently. | Choose this when you need to plan a maintenance window. |
| Region placement | Your service is placed in a data center selected for the service rather than wherever capacity is available. | Consider this when the location of your users or customers makes regional placement important. |
| Always On | The site remains running instead of being spun down when inactive. | Use this for production applications. A spun-down site can take approximately 50–60 seconds to wake up. |
| MDriven Framework option | MDriven Framework is a Visual Studio plugin that provides the model as C# code, where you can implement methods in standard C#. | Use it when your solution needs behavior beyond what MDriven has already provided. |
| History Server option | A HistoryServer keeps writes in a separate database so that writes are retained with timestamps rather than overwritten. In MDriven, versioning can be set class by class with IsVersioned; HistoryServer treats every class as versioned and evolves with the current model.
|
Consider this when you need a complete recorded history of writes. |
Hosting on your own infrastructure
Running on your own cloud account does not necessarily reduce your total cost. It gives you more control over scaling and moving the solution, while you pay your cloud provider for the infrastructure resources and pay MDriven for tool usage, licensing, and support.
For example, if you operate Turnkey on your own Azure account, Azure charges for the resources you consume. The MDriven charge covers the applicable MDriven tools, license, and support arrangement; it is not a substitute for your cloud-provider bill.
You can also run MDriven on your own hardware or on hired cloud hardware. MCoins are designed to support payment for MDriven component usage regardless of where you run it.
How billing is calculated
Usage billing is described as two daily passes:
- Execution pass. For each payer and site, the calculation identifies the most recently seen MDrivenServer and charges the applicable daily amounts for site, classes, views, used data, and end-user volume.
- Developer-tool pass. For each developer, the calculation uses the latest reported MDriven Designer or MDriven Framework class and view counts and charges the applicable daily per-class and per-view amounts.
The calculation therefore separates the cost of running an application from the cost of using the development tools. In the multi-tenant example above, the shared model's development usage belongs to the developer side, while each tenant site contributes to the execution side.
Get current pricing and help
Use the MDriven pricing page for current plan details, MCoins allowances, and contact options. For a calendar-based or negotiated arrangement, including requirements such as offline operation or restricted reporting, contact MDriven sales.
See also
Pricing options at a glance
Pricing options at a glance
MDriven offers a free option, usage-based pricing, annual licensing, and custom enterprise arrangements.
| Option | Intended use | Price and commitment | Published capabilities |
|---|---|---|---|
| Free | Personal projects and exploration | Free; no credit card required | Use MDriven Designer, Turnkey Server, and Local MDriven Server only on your own device. The model is limited to 50 classes. There is no time limit, and the published demo examples fit within this limit. |
| Pay as You Go | Cloud use and changing demand | Usage-based; minimum monthly commitment of 10 EUR | Registration is required. The plan includes 70 free MCoins per month, unlimited classes, cloud operation, demo-website deployment, online startup of Designer and servers, and use of Turnkey Server and MDriven Server. |
| Business Critical | Production systems requiring support commitments | Annual license; custom quote; billed annually | Includes the Pay as You Go capabilities plus priority support, priority bug fixing, direct developer access, guaranteed response times, a full source-code backup license, the ability to request custom features, and a service-level agreement (SLA). |
| Enterprise | Large-scale, offline, or restricted-network deployments | Custom quote | Includes the Business Critical capabilities plus unlimited cores, global replication and cache servers, advanced history management, multi-database environments, load balancing and failover setup, offline license mode, support for complex firewalls and restricted networks, and dedicated technical architecture support. |
Understand MCoins
For Pay as You Go pricing, 1 MCoin equals 1 EUR. The published pricing page states that storage, backups, and shared cloud hosting are included in MCoin consumption.
The technical billing description identifies execution-cost inputs including classes, views, data usage, sites, and end-user count. It separately describes Designer or Framework billing based on the number of views and classes.
Estimate a SaaS deployment
For a SaaS solution in which each tenant has its own database, multiply the execution price, including add-ons, by the number of sites. Calculate the development price once when development is shared.
For example, for 50 customer sites, calculate execution pricing for 50 sites and development pricing once.
Calendar-based licensing
MDriven also offers a traditional calendar-based license. License periods are yearly unless another period is specified. This option may suit organizations that need a fixed fiscal-period budget, operate offline, or cannot allow usage reporting through a firewall.
MDrivenTurnkey and MDrivenServer licenses are available through sales@mdriven.net. The calendar-based pricing description says production pricing is calculated from model size and the number of frontends for scale-up and slave servers for scale-out. It also states that the minimum MDrivenServer and MDriven Turnkey setup for production, development, and test is freely usable, and that pricing can be negotiated.
For MDrivenServer operations, the calendar-based license requires a report of model size, measured as classes plus views, and user base.
Get a quote
MDriven Turnkey pricing is available through portal.mdriven.net. Contact sales@mdriven.net for calendar-based licensing or to discuss pricing. Businesses with fewer than 50 employees may be eligible for startup, ISV, or service-provider discounts.
Pricing and licensing
This page explains MDriven's documented pricing and licensing approaches. For current prices and purchase options, see portal.mdriven.net.
Pricing and licensing approaches
MDriven offers consumption-based payment using MCoins and a traditional calendar-based license model.
MCoins are described as the easiest way to pay for MDriven services. A calendar-based license may be appropriate when a fixed licensing period is required, when usage reporting is not acceptable, or when tools operate offline or behind a firewall that prevents reporting.
Calendar-based license periods are yearly unless another period is specified. MDriven Turnkey and MDriven Server licenses are acquired through sales@mdriven.net.
What MCoin billing measures
The billing process has two parts:
- Site and MDriven Server usage: the calculation includes the number of classes, the number of views, used data, a per-site charge, and applicable end-user-volume pricing.
- Designer or Framework usage: the calculation includes the number of views and classes in the model used on the previous day.
The applicable rates are defined by MDriven's current price configuration. Consult the pricing portal for current rates.
Model-size limit and MCoins
The free MDriven Designer version allows up to 50 classes. When MCoins are used to pay for services, this 50-class limit is removed. Designer usage with a larger model consumes more MCoins than usage with a smaller model.
Calendar-based licensing
Calendar-based licensing can be used when:
- a fixed budget is needed for a fiscal period;
- online usage reporting is unacceptable;
- a firewall prevents the software from reporting usage; or
- the tools will operate offline.
MDriven Framework is calendar-based and may be included in agreements with MDriven Turnkey. The calendar-based license page states that shop prices are list prices for corporate professional production use and include MDriven's "keep it working" guarantee. Contact sales for additional service-level agreements.
Self-hosting and SaaS tenants
You can use your own cloud provider, such as Azure or AWS, if it can run Turnkey; the documentation currently identifies IIS as the Turnkey runtime requirement. In this arrangement, you pay the cloud provider for its resources and pay MDriven for tool usage, licensing, and support.
For a SaaS application in which every tenant has a separate database, calculate the execution price for each site and multiply it by the number of sites. Development is shared, so the development price is applied once. For example, 50 customers with 50 sites use the execution price 50 times and the development price once.
Current pricing
Current MDriven Turnkey pricing is available through portal.mdriven.net. For MDriven Turnkey, MDriven Server, calendar-based licensing, or negotiated arrangements, contact sales@mdriven.net.
Pricing plans
Pricing plans
MDriven publishes four pricing options: Free, Pay as You Go, Business Critical, and Enterprise. For current prices, quotes, and plan terms, see the Pricing page.
| Plan | Cost and commitment | Intended use | Published inclusions |
|---|---|---|---|
| Free | Free; no credit card required | Personal projects and exploration | MDriven Designer, Turnkey Server, and Local MDriven Server for use only on your own device; a maximum of 50 classes; no time limit. The Pricing page states that all demo examples fit within this limit. |
| Pay as You Go | 1 MCoin = 1 €; minimum monthly commitment: 10 € | Usage-based growth and cloud operation | Everything in Free, plus registration, 70 free MCoins per month, an unlimited number of classes, the ability to run in the cloud, demo website deployment, starting Designer and servers online, and running Turnkey Server and MDriven Server. |
| Business Critical | Annual license; custom quote; billed annually | High availability and production requirements | Everything in Pay as You Go, plus priority support, priority bug fixing, direct developer access, guaranteed response times, a full source-code backup license, custom-feature requests, a service-level agreement (SLA), and ownership of the full source code. |
| Enterprise | Custom | Large-scale or specialized infrastructure requirements | Everything in the annual-license offering, plus unlimited cores, global replication and global cache servers, advanced history management, multi-database environments, load balancing and failover setup, offline license mode, complex-firewall and restricted-network deployments, and dedicated technical architecture support. |
Consumption and hosting
The Pricing page describes Pay as You Go as consumption-based pricing. It states that storage, backups, and shared cloud hosting are bundled into MCoin consumption.
Quotes and assistance
Business Critical is offered as a custom annual quote, and Enterprise pricing is tailored to the customer. The Pricing page also lists Solutions Architects and Professional Services as assistance options.