No VPS execution path
Users do not need to keep an EA running on a VPS for MetaAPI-connected accounts.
Cloud trade execution for Telegram signals using the customer's own MetaAPI subscription. No VPS is needed for the execution path, and MetaAPI billing stays directly with the user.
The copier still handles Telegram parsing, routing, AI recognition, settings, and logs. MetaAPI receives the approved trade execution request for each connected MT account.
Users do not need to keep an EA running on a VPS for MetaAPI-connected accounts.
Each customer creates and pays for their own MetaAPI account directly at metaapi.cloud.
This plan does not cap MetaAPI-linked MT account slots inside the copier.
For this copier, users need MetaAPI's core MetaApi API for MT4/MT5 accounts. They should choose the MetaAPI subscription size that supports the number of MT accounts they want to run.
After subscribing, users manage MetaAPI inside Dashboard -> MetaAPI Cloud.
Save the broker login that should receive copied trades.
Deploy the same MT4/MT5 account inside the user's MetaAPI portal.
Use the dedicated dashboard page to connect the account securely.
Run the connection test before switching the account to MetaAPI execution.
Subscribe to the connector plan, then connect the customer's own MetaAPI details in the dashboard.