Trading infrastructure should belong to the people who trade.

We started PerkBridge because running many trading accounts meant either handing passwords to a cloud vendor or babysitting remote desktops. We build the third option: software that turns your own servers into a managed trading fleet.

What we will not compromise on

Your credentials are yoursBroker passwords are encrypted to your own server for each start and never land in code, images or logs. Remembering one is opt-in, and it is split so that neither your server nor the Control Plane can open it alone.

Trading safety firstNo blind restarts, no deleting an active environment because a link dropped, and ambiguous outcomes are reconciled, never retried. Closing a position stays possible even during a halt.

Broker neutralWe do not design around one broker or take commission on your trades. You choose who you trade with.

Honest labelsAvailable means merged and usable. Everything else says In progress, Coming soon or Planned.

Decisions on recordMajor architecture choices are written down as decision records, and the website follows them.

Demo before liveEarly access supports MetaTrader 5 demo accounts only. Real-money accounts are refused, and no independent security audit has been done yet.

Where we are todayHeadless MetaTrader 5 on your Ubuntu 24.04 servers from a signed image catalog, a Trading API with market and pending orders, risk rules and time rules next to the terminal, remembered credentials, notifications, an emergency stop and single sign-on. Failover to a standby server is included.

What comes nextDirectConnect, an opt-in low-latency order path, plus faster order dispatch, Windows servers, remote screen access, an in-browser demo and a production release key. cTrader is coming soon.

What we have not built yetReal-money accounts, in-place upgrades, two-factor sign-in, user management in the dashboard and a published production release key.

Contact

Talk to a person.

EMAILsupport@perkbridge.euSales, partnerships, support and security reports. Include your deployment ID, never a password. For a security issue, use the subject “Security report” and see our security and disclosure policy.