Moving to your own infrastructure
Keep your code. Own the whole stack.
Hosted trading APIs are a quick way to start. As a fleet grows, many teams want the terminals, the credentials and the risk limits on servers they control. PerkBridge keeps the REST experience you already know and runs it on your infrastructure, so moving is mostly a new base URL, a new token and a few field names.
Why teams move
The same API, with everything inside your boundary.
Moving is usually driven by growth: more accounts, stricter clients or investors, and a wish to control every part of the setup.
The same order, side by side
A market buy.
On the left, a generic hosted API call, simplified. On the right, the real PerkBridge request from the Trading API reference. The API also places limit, stop and stop-limit orders with time in force, and can modify and cancel them. Stop loss and take profit work on pending orders but not yet on MT5 market orders. DirectConnect, an opt-in low-latency order path, is coming next.
Migration path
Run both side by side, then switch.
Nothing has to move in one go. Bring one account across, run it in parallel on demo, and switch the rest when you are happy.
- 1Install the control plane →Run the installer on an Ubuntu 24.04 server. It sets up the Docker Compose stack with automatic HTTPS.
- 2Add a trading server →Enter its address in the dashboard. The host key is verified and the agent is installed for you.
- 3Bring one account across →Pick the platform, find the broker server by name, enter the demo login, and set the account’s risk limits.
- 4Point your bot at it →Issue a trading token, change the base URL and field names, and run it next to the old setup.
- 5Move the rest →Bring the remaining accounts across at your pace. As good practice after any move, rotate each broker password.
Good to know
A hosted API may still suit you better if you need:
Try one account first.
Ask for a private sandbox and we will help you bring a demo account across on a call.