Solutions

Built for people who run more than one account.

Whether you trade your own accounts, run strategies for clients or answer to a compliance team, PerkBridge gives you the same thing: the whole fleet in one place, on servers you own.

Multi-account and prop-firm traders

Every account on one screen, with limits that never sleep.

Run your own accounts and funded challenges across brokers without logging in to a remote desktop for each one.

THE PROBLEM TODAYFive VPS logins and ten terminals. You find out a terminal froze, or a loss limit was crossed, after the damage is done.
TYPICAL SETUP5 to 50 accounts on 1 to 5 servers
WHAT YOU GET
One fleet dashboard. Every server, account and broker link with its health, in one place.
Health alerts where you look. A frozen terminal, a lost broker link or an offline server raises an alert in the dashboard, and rules can send it to Telegram, Slack, email or a webhook. A stalled terminal is never restarted blindly.
Limits sized for your challenge. Start from evaluation or funded values a step inside your firm’s rules; they hold even if the dashboard is offline. Time rules can keep you out of news windows and close positions before the market closes.
Any MT5 broker. Find the broker server by name or paste its installer link. Demo accounts only for now.
Several accounts per server. No more one VPS per account.
How risk limits work →
CHALLENGE STARTING POINT · 100,000 USD ACCOUNT Daily loss 4,000 USD · 5 open positions · 2.00 lots per order

EA vendors, signal providers and account managers

Run strategies on client accounts without holding their passwords in someone else’s cloud.

Serve many client accounts through one API, with each account isolated and every action recorded.

THE PROBLEM TODAYClients have to give their broker password to a third-party cloud service that you then have to vouch for.
TYPICAL SETUP20 to 200 client accounts
WHAT YOU GET
One API over every account. Place orders, read positions and market data with the same call everywhere.
An isolated environment per account. Each client’s terminal runs in its own container.
Scoped tokens per strategy route. Each strategy only reaches the accounts it is allowed to trade.
Credentials sealed to your server. Delivered encrypted to the agent, held in memory, never logged. Remembering a password is opt-in.
An audit log. Show clients exactly who did what and when.
Read the Trading API reference →
SAME CALL FOR EVERY ACCOUNT POST /v1/trading/accounts/{account_id}/orders

Small funds and trading desks

Trading infrastructure your security team can sign off.

Keep terminals, credentials and the control plane inside your own perimeter, with central risk control and access management.

THE PROBLEM TODAYSecurity or compliance rules forbid giving broker passwords to a SaaS, so the desk runs terminals by hand.
TYPICAL SETUPA team managing 10 to 100+ accounts
WHAT YOU GET
Fully on-premises. Control plane, database, sign-in, agents and terminals all run inside your perimeter, installed with the Docker Compose installer.
Your single sign-on. Sign in through your own OIDC identity provider or the bundled one, with roles per person.
Central risk limits. Loss, exposure and order-rate limits per account and strategy route, enforced on your server.
Halt one account or the whole fleet. With one call or one click.
Least privilege and audit. No exposed Docker API, approved images only, every privileged action recorded.
Users, roles and single sign-on →
STOP EVERYTHING POST /v1/trading/halt-all

Delegating access to managers, clients and apps

Let others watch or trade an account without giving them the password.

Give a money manager, a client, a colleague or an EA exactly the rights it needs, on exactly the accounts it needs, and take them back at any time.

THE PROBLEM TODAYSharing means handing over a password: the investor password so someone can watch, the master password so they can trade. Taking access back means changing it at the broker.
TYPICAL SETUPAny account shared with another person or app
WHAT YOU GET
Read only or trade. Viewers see balances, positions, orders and history; traders can also place orders and close positions.
Per account, not all or nothing. Rights are granted on chosen trading accounts, so a client sees only their own.
Tokens for apps and EAs. A read-only or full-access API token, optionally limited to one strategy route.
Revoke at any time. Access ends at once; the broker password stays the same and stays on your server.
Every action recorded. The audit log shows who placed or closed what, and when.
How access grants work →
TWO LEVELS PER ACCOUNT Read only: watch · Trade: place orders and close positions
Under consideration

Brokers and introducing brokers

Many brokers already sponsor VPS hosting for active clients. A white-label PerkBridge fleet gives those clients a dashboard, an API and risk limits under your brand, on infrastructure you control.

White-label dashboard for your clients
Hosted on your servers, in your regions
Commercial terms to be agreed
Talk to us

Is it for you?

A quick guide by fleet size.

1 accountYour platform’s built-in hosting is simpler. Come back when you add more.
3 to 10One server, one dashboard, alerts and loss limits. The point where PerkBridge starts to pay off.
10 to 100The sweet spot: several servers, routes per strategy and scoped tokens.
100+Teams, single sign-on and audit. Talk to us about your setup.