How usage-based pricing works — the full explanation
We published a complete write-up of what meters, what never meters, and how per-hour billing compares with a flat monthly fee — with the arithmetic included so you can check it against your own setup.
Billing questions come up often enough that a short answer stops being useful, so we wrote the long one.
The article covers what actually meters (platform hours and module hours), what never does (non-trading API calls, disabled modules, the sandbox, storage), and a worked example with the arithmetic spelled out — including how much a single decision, like switching the trade copier off over weekends, changes the invoice. WebAPI is billed separately on its own model, with REST and real-time SignalR priced differently; current rates are on the API pricing page.
Two things in it are worth knowing even if you skip the rest. The pricing page reads its rates out of the billing system itself, so the number you are quoted and the number you are charged cannot drift apart. And the price-match offer has no end date: if you find a comparable solution cheaper, tell us and we will either match it or show you exactly what sits inside each price.
Read it here: How usage-based pricing works for MT4, MT5 and MatchTrader management tools
Your own numbers are always on Pricing and API Usage — both read live data, not an estimate.
This note sums up an article on the CPlugin™ blog. Read the full article ↗