FMZ Bot Billing by Runtime Hour and Bot Lifecycle
Summary
The announcement describes a change to FMZ automated trading bot charges: billing is calculated in hourly periods beginning when a bot starts, with a minimum charge for the initial hour. Stopping a bot does not pause that hour, and restarting within the same period does not create another charge. Each bot is billed independently, so separate bots do not share paid time. The platform also removes its concurrent bot limit, while warning that insufficient account funds can cause bots to stop.
For users managing live or test systems, the practical lesson is to account for runtime costs and to stop bots through the platform controls. Simply removing a server-side Docker process may leave a bot marked as running, allowing charges to continue. The announcement explains billing and stop procedures, but does not analyze trading performance or provide a cost comparison beyond the stated hourly rate. Charges and operational behavior are specific to the described FMZ system.
Key ideas
- Billing periods begin when each bot starts and are measured in hours.
- A bot's billing period is independent of other bots and continues while it is stopped.
- Insufficient account balance can lead the platform to stop bots.
- Users should stop bots through FMZ controls because removing Docker alone may leave billing active.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.