MCoins
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
===MCoins=== | ===MCoins=== | ||
MCoins can pay for all MDriven services. You may also pay | MCoins can pay for all MDriven services. You may also pay using a [[Calender based license|calender based license model]]. | ||
There are NO free services, but free MCoins | There are NO free services, but rather, free MCoins. | ||
MCoins have a nominal value of 1 Euro | MCoins have a nominal value of 1 Euro. | ||
An account | An account has two types of MCoins: | ||
*Paid MCoins | *Paid MCoins | ||
** | **A lifetime of 5 years | ||
*Free MCoins | *Free MCoins | ||
**Varying lifetime | **Varying lifetime | ||
*** | ***Auto refill: once a week | ||
***Giveaways: | ***Giveaways: once a year | ||
Free MCoins are used before the Paid | Free MCoins are used before the Paid MCoins in an account. | ||
Paid MCoins can be | Paid MCoins can be: | ||
* | *Sold online (to fill up an account) | ||
* | *Sold via vouchers of different kinds | ||
**By resellers (pre use) | **By resellers (pre-use) | ||
**On an invoice (after use) | **On an invoice (after use) | ||
Free MCoins are given away | Free MCoins are given away: | ||
*Every week to all accounts | *Every week to all accounts | ||
*On recruitment | *On recruitment | ||
| Line 28: | Line 28: | ||
*For used time | *For used time | ||
*For calendar time | *For calendar time | ||
*Certain functions in the | *Certain functions in the Designer are blocked until you log in. Once you log in, we track the Designer's day usage; used this day or not (Play, Generate code, 20 classes limit) | ||
Prices for '''Used Time''' | '''Prices for''' '''Used Time''' | ||
*Running the | *Running the Designer "ad hoc": 2 MCs / day | ||
*Running a basic hosted model: 0.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 overridden by the admin to correctly assign a cost to heavier sites. This weight factor should be automatically calculated in the future based on the model size and/or transaction amount and/or DB usage and/or production status. | ||
*Running a basic hosted model (MDrivenServer) on | *Running a basic hosted model (MDrivenServer) on your machine: 0.1 MC/day | ||
*MDrivenServer features can be individually priced, but that | *MDrivenServer features can be individually priced, but that is a future decision. | ||
*In the future | *In the future, Azure pricing may perhaps be used as a basis for MC costs. | ||
Prices for '''Calendar Time''' | Prices for '''Calendar Time''' | ||
*Designer: 60 MCs / year | *Designer: 60 MCs / year | ||
| Line 40: | Line 40: | ||
*Client: 120 MCs / year | *Client: 120 MCs / year | ||
===MCoin accounts=== | ===MCoin accounts=== | ||
These hold both Free and Paid MCoins. | |||
An account can have | An account can have an MCoin credit (that is, it can be negative): | ||
*To avoid stopping an account's services right away when the account reaches 0 | *To avoid stopping an account's services right away when the account reaches 0. | ||
* | *For corporations that should be invoiced afterward instead of paying upfront. | ||
====Account | ====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 | 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 is not limited to calendar time but has a price. | ||
===Arguments for | ===Arguments for Why We Have the MCoin Payment System=== | ||
If you run out of money in the middle of the week, you can 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 | You can use a small amount of the MCoin 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) | 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 | You can choose to run on your own hardware (on-prem) or hired hardware (cloud) and only pay for the usage of MDriven components. | ||
[[Category:MDriven Services]] | [[Category:MDriven Services]] | ||
Revision as of 08:17, 25 January 2023
MCoins
MCoins can pay for all MDriven services. You may also pay using a calender based license model.
There are NO free services, but rather, free MCoins.
MCoins have a nominal value of 1 Euro.
An account has two types of MCoins:
- Paid MCoins
- A lifetime of 5 years
- Free MCoins
- Varying lifetime
- Auto refill: once a week
- Giveaways: once a year
- Varying lifetime
Free MCoins are used before the Paid MCoins in an account.
Paid MCoins can be:
- Sold online (to fill up an account)
- Sold via 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 the Designer's 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 overridden by the admin to correctly assign a cost to heavier sites. This weight factor should be automatically calculated in the future based on the model size and/or transaction amount and/or DB usage and/or production status.
- Running a basic hosted model (MDrivenServer) on your machine: 0.1 MC/day
- MDrivenServer features can be individually priced, but that is a future decision.
- In the future, Azure pricing may perhaps 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
These hold both Free and Paid MCoins.
An account can have an MCoin credit (that is, it can be negative):
- To avoid stopping an account's services right away when the account reaches 0.
- For corporations that should be invoiced afterward 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 is not limited to calendar time but has a price.
Arguments for Why We Have the MCoin Payment System
If you run out of money in the middle of the week, you can pay your way out of the problem or wait.
You can use a small amount of the MCoin 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 the usage of MDriven components.
This page was edited more than 8 months ago on 05/03/2024. What links here