MCoins
No edit summary
No edit summary
(One intermediate revision by the same user not shown)
Line 1: Line 1:
===MCoins===
===MCoins===
MCoins can pay for all MDriven services.
MCoins can pay for all MDriven services. You may also pay by a [[Calender based license|calender based license model]].


There are NO free services, only free MCoins
There are NO free services, but free MCoins


MCoins have a nominal value of 1 Euro
MCoins have a nominal value of 1 Euro
Line 55: Line 55:
Regardless of where you run MDriven, you pay per time (minutes, days)
Regardless of where you run MDriven, you pay per time (minutes, days)


You can choose to run on your own hardware (in prem) or hired hardware (cloud) and only pay for usage of MDriven components
You can choose to run on your own hardware (on prem) or hired hardware (cloud) and only pay for usage of MDriven components

Revision as of 11:19, 16 November 2019

MCoins

MCoins can pay for all MDriven services. You may also pay by a calender based license model.

There are NO free services, but free MCoins

MCoins have a nominal value of 1 Euro

An account have MCoins of two flavors

  • Paid MCoins
    • Lifetime of 5 years
  • Free MCoins
    • Varying lifetime
      • Autorefill: once a week
      • Giveaways: 1 year

Free MCoins are used before the Paid ones in an account

Paid MCoins can be

  • sold online (to fill up an account)
  • sold on vouchers of different kinds
    • By resellers (pre use)
    • On an invoice (after use)

Free MCoins are given away

  • Every week to all accounts
  • On recruitment
  • As a giveaway

Using MCoins

  • For used time
  • For calendar time
  • Certain functions in the designer are blocked until you log in - once you log in we track designer day usage ; used this day or not (Play,Generate code, 20 classes limit)

Prices for Used Time

  • Running the designer "ad hoc". 2 MCs / day
  • Running a basic hosted model: 0.2 MCs / day , each Turnkey site has a default weight factor of 1 but this can be overriden by admin to correctly assign cost to heavier sites. This weight factor should be automatically calculated in the future - based on model size and/or transaction amount and/or db usage and/or production status.
  • Running a basic hosted model (MDrivenServer) on own machine: 0.1 MC / day
  • MDrivenServer features can be individually priced, but that's for the future to decide
  • In the future maybe Azure pricing can be used as a basis for MC costs

Prices for Calendar Time

  • Designer: 60 MCs / year
  • MDrivenServer (basic): 500 MCs / year
  • Client: 120 MCs / year

MCoin accounts

Holds Free and Paid MCoins

An account can have a MCoin credit (that is, it can be negative)

  • To avoid stopping an account's services right away when the account reaches 0
  • To corporations who should be invoiced instead of paying upfront

Account workings

License keys are linked to a "price plan". If the license key is a calendar type of license, the price per hour is 0, but has an end date. If the license key is a "Used Time" type of license, it's not limited in calendar time, but has a price.

Arguments for having this MCoin payment system

You can run out of money in the middle of week - pay your way out of the problem or wait

You can use a small amount to test run a global system (for a very short time) to prove a use case

Regardless of where you run MDriven, you pay per time (minutes, days)

You can choose to run on your own hardware (on prem) or hired hardware (cloud) and only pay for usage of MDriven components

This page was edited 2 days ago on 03/26/2024. What links here