Frequently asked questions
These are the questions brokers actually ask before they start — answered the way we'd answer them on a call. If yours isn't here, ask us directly.
Products & compatibility
Which platforms do you support?
Server plugins are native MT4 and MT5 modules, written in C++ and Rust and loaded by the trade server itself. Toolbox and the cloud WebAPI talk to MT4, MT5 and MatchTrader through each platform's Manager API. A mixed setup is fine — one Toolbox account can drive all of them side by side.
Do you build client-side EAs or indicators?
No. We work on the server side only — plugins, Manager API integrations and cloud services. Expert advisors and indicators live in the client terminal, and that is a different craft with its own specialists; our ground is the trade server.
Can I try before I buy?
Yes, and without talking to sales first. Most plugins ship as demo builds with documented limits — typically the first hundred requests are processed, and a server restart resets the counter, so you can evaluate behaviour on your own environment. Toolbox and WebAPI have a free Sandbox: a full-featured staging environment at pre.toolbox.cplugin.com and pre.mywebapi.com where you build and test at no cost. Billing starts only when you connect to production.
Delivery & installation
How is your software delivered?
From our privately hosted NuGet server, installable directly or through Chocolatey — so installing is one command, upgrading is one command, and you can pin or roll back to any previous version. No installers, no dongles. The exact steps are in How to obtain files.
Do you need access to our trade server?
For plugins — no. You copy the module and set its parameters following the product's documentation, or we walk through it together on a call. Cloud products connect through the platform's Manager API using a manager account that you create and control: each product documents the minimal rights it needs, you grant nothing beyond that, and you can rotate or revoke the account at any time. Your admin credentials never enter the picture.
Pricing & terms
How does pricing work?
Plugins and standalone tools are sold as licenses — write to us for a quote. Toolbox is billed by the hour for the resources you have connected, so you pay for time actually used and can switch things off. WebAPI is pay-as-you-go on a regressive scale: the more you use, the cheaper each unit, with calls and realtime events metered separately. The Sandbox is always free. The full model is described in Pricing and terms.
Why is there no cart on this site?
Deliberately. Subscriptions and billing live inside Toolbox, next to the usage numbers and the forward cost estimate they apply to. For plugin licenses and bespoke work the right first step is a short conversation, not a checkout — get in touch and we'll take it from there.
Do long-term clients get better terms?
Yes. There is no coupon machinery here; terms improve the old-fashioned way, by working together. Brokers who have been with us for years get better pricing and priorities, worked out individually.
Custom development
Can you build something that doesn't exist yet?
That is a large part of what we do. Describe the problem — business terms are enough, no specification required — and we come back with an approach and an estimate, then build it around your platform. If an existing product almost fits, we'll say so and extend it instead of billing you for a rewrite.
Do you sign NDAs? Who owns the code?
We sign NDAs on request — before you tell us anything sensitive, if you prefer. The source code of what we build stays with CPlugin; you receive the binaries and a license. That split is what keeps maintenance viable: when the platform moves underneath the product, we update the code because we still own it.
Support & updates
What happens when MetaQuotes releases a new server build?
Version drift is the quiet cost of the native layer: interfaces shift and behaviour changes between builds. Tracking it is part of our job, not yours — we follow platform releases, update the affected products and publish to the same NuGet and Chocolatey feed you installed from, so staying current remains one command.
What support do we get?
A direct line to the engineers who wrote the code, the founder included. There are no ticket tiers and no first-line script to get past: you describe the problem, and the person answering is the person who can fix it.
Company
Who is behind CPlugin?
A small, founder-led engineering house. The founder wrote his first lines in forex in 2006; CPlugin has been building on that experience since 2015. The operating entity is CPlugin Labs LP, registered in the United Kingdom. The work is done in C++ and Rust, on the server side of MetaTrader, and that focus is deliberate — one discipline, done deeply.
Is CPlugin a product or a company?
A company. Toolbox and WebAPI are its products, and the plugin catalogue is its craft. When you buy from us you are not subscribing to a faceless platform — you are hiring a house you can call.