There is a question that comes up constantly among funded traders and almost never gets a straight answer: is it safe to run several prop firm accounts from a single VPS?
The reason nobody answers it cleanly is that the honest answer has two halves that sound contradictory. Running your own accounts from one machine with one IP is normal, expected, and in some cases explicitly required. Running accounts that belong to other people from that same machine is account sharing, which every firm prohibits and several actively detect. The infrastructure looks identical from the outside. What differs is whose accounts they are — and the monitoring systems cannot see intent, only patterns.
So the practical skill is understanding which patterns their systems flag, and making sure your legitimate setup does not accidentally produce them.
Why Prop Firms Monitor IP Addresses At All
Prop firms have a specific commercial problem. Their business model assumes that the person who buys an evaluation is the person who trades it. When a “challenge passing service” takes fifty clients’ accounts and trades them all from one desk, the firm is no longer underwriting fifty independent traders — it is underwriting one trader fifty times, with all the correlated risk that implies. If that trader is good, the firm pays out fifty times on one skill set. If they are reckless, the firm eats fifty simultaneous blowups.
So firms watch for it, and the cheapest, most reliable signal available is network origin. If forty accounts registered to forty different names all connect from the same IP, that is not a coincidence and no explanation makes it one.
📊 Key Stat: IP-based detection is the primary account-sharing control at most prop firms because it requires no cooperation from the trader and no additional infrastructure. It is passive, automatic, and runs continuously — which is why it catches people who assumed nobody was looking.
What They Are Actually Looking For
The monitoring is more nuanced than “same IP equals ban”. The patterns that draw attention:
Many accounts, many names, one IP. The classic pass-service signature. This is the one that ends accounts.
One account, many rapidly changing IPs across distant geographies. Logging in from London at 09:00 and Singapore at 09:30 is physically implausible for one person and suggests the account is being operated by someone else — or by several someones.
Trade timing correlation across accounts. Even without an IP match, if fifty accounts open the same position on the same symbol within the same second, the firm can see it. Copiers produce this signature by design.
IP patterns associated with shared VPN pools. Consumer VPN exit nodes are shared by thousands of users, many of whom are doing things prop firms care about. Appearing on one is not itself an offence, but it removes your ability to demonstrate a consistent, individual origin.
Sudden origin changes at suspicious moments. An account that trades from one IP all through an evaluation and then switches origin the week a payout is requested invites a closer look.
⚠️ Warning: Do not run a consumer VPN on top of your trading VPS. It is a common instinct — more privacy, surely more safety — and it produces precisely the wrong outcome. You take a clean, dedicated, static IP that demonstrates a consistent individual origin, and replace it with a rotating shared address that thousands of strangers also use. You have paid extra to look more suspicious.
What Is Explicitly Fine
Now the reassuring half. Firms are not trying to stop you from being organised.
Running several of your own accounts from one VPS is normal. Traders routinely hold two or three evaluations across firms, or run one aggressive and one conservative account in parallel. Nobody at the firm considers this unusual. Your name is on all of them, your KYC matches, and the IP consistency is evidence for you rather than against.
Some firms require a dedicated VPS. This is the part that surprises people. Several prop firms now stipulate that traders using automation must operate from a dedicated VPS with a consistent geographic IP, subject to audit. FundingPips is a documented example. The requirement exists precisely because a static, attributable IP is easier to verify than a shifting residential one — the firm wants the consistency, not the anonymity.
Using a copier across your own accounts is generally permitted, though rules vary by firm and some restrict it. What is not permitted is copying to accounts that are not yours.
Trading from a datacenter IP is not itself a flag. Prop traders use VPSs; the firms know this and expect it. What matters is the pattern, not the address type.
💡 Tip: If you hold accounts at three firms and you are unsure how any of them view your setup, email their support and describe it in one paragraph: how many accounts, all in your name, one dedicated VPS, one static IP, using a copier or not. Keep the reply. It takes ten minutes and converts an ambiguity into documentation you can point at if a payout ever gets held for review.
The Setup That Keeps You Clean
1. One Dedicated VPS, One Static IP, Only Your Accounts
The foundation. A dedicated VPS gives you an IP that is yours and does not change. Every account on it is yours. That is the whole compliance story, and it is a simple one to tell.
2. Do Not Share the Machine
Do not let a friend log in to check something. Do not run a family member’s account “just this once”. Do not sell or lend access. The moment a second person’s accounts touch that IP, your clean pattern becomes the pass-service pattern, and you will not get to explain the difference to an automated system.
3. Keep the IP Genuinely Static
No VPN layers. No switching datacenters mid-evaluation. If you need to move regions for latency reasons, do it between accounts rather than mid-challenge, and expect that the origin change is visible.
4. Be Deliberate About Copiers
If you run a copier across your own accounts, understand that it produces a highly visible correlation signature — identical entries, identical timing, proportional sizing. That is fine when the accounts are yours and the firm permits copying. Check that second condition explicitly, because a minority of firms restrict it, and “I did not know” is not a defence at payout review. Our copy trading setup on VPS guide covers the architecture.
5. Respect Each Firm’s Rules Independently
Running two accounts on one machine does not merge their rule sets. If Firm A permits news trading and Firm B does not, your copier will happily violate Firm B’s rules on your behalf while satisfying Firm A’s. Configure per-account restrictions in the copier, not globally.
🚀 Try FXVPS free for $1.99 — get 7 days on the Core VPS risk-free with a dedicated static IP. No long-term commitment, cancel anytime.
Sizing a Multi-Account VPS
The resource question is separate from the compliance question, and it is where people undersize.
Each account generally means a platform instance. Each platform instance means memory. The multiplier is worse when browsers are involved, because browser-native platforms — TradeLocker, Match-Trader, DXtrade — are far heavier than MetaTrader.
Core Plan ($29/mo — 2GB RAM, 1 vCPU) handles one or two MetaTrader instances comfortably, or a single browser-platform session. It is the plan for a trader with one or two accounts on the same platform.
Pro Plan ($39/mo — 4GB RAM, 2 vCPUs) is the realistic size for three to four accounts, or any mix that includes a browser platform alongside MetaTrader, or a copier with several destinations. Most serious multi-account prop traders live here.
Scaling Plan ($79/mo — 8GB RAM, 4 vCPUs) covers five or more accounts, multiple browser sessions, or a copier fanning out widely. If you are managing meaningful funded capital across firms, the $50 difference from Pro is not a real consideration.
Our guides on how many MT4 terminals a VPS can run and running multiple MT4 and MT5 terminals go into the per-instance numbers.
✅ Best Practice: Undersizing a multi-account VPS creates a failure mode that looks like a strategy problem. When memory runs out, Windows starts paging to disk, and a terminal that is paging can take seconds to process a tick it should have handled instantly. You will see it as slippage and missed entries across all accounts simultaneously, and you will spend a week debugging your EA before you check Task Manager. Watch committed memory during the London open in your first week.
What To Do If You Are Flagged
If a firm queries your setup, the response is straightforward and should be boring:
- State the facts plainly. How many accounts, all registered in your name, all traded by you, from one dedicated VPS with a static IP.
- Provide the VPS details if asked — provider, region, IP. A legitimate setup survives this trivially; that is the entire point of having one.
- Do not change anything mid-review. Switching IPs while under review looks like evidence destruction, regardless of your reasons.
- Point at any prior correspondence where you described the setup in advance. This is why the ten-minute email earlier is worth sending.
The traders who get permanently banned are overwhelmingly the ones who genuinely were sharing accounts. The traders who get a query and then a shrug are the ones whose story is simple, consistent and checkable.
Summary
- Prop firms monitor IP addresses to detect account sharing, and the detection is automatic and continuous.
- Running your own accounts from one VPS is normal, and some firms explicitly require a dedicated VPS with a consistent IP for automated trading.
- Running other people’s accounts from your machine is account sharing, and no infrastructure choice makes it acceptable.
- Do not add a consumer VPN — it replaces a clean static IP with a shared rotating one and makes you look worse, not better.
- Copiers produce a visible correlation signature. That is fine across your own accounts at firms that permit copying. Confirm the second part.
- Each firm’s rules apply independently, even when the accounts share a machine.
- Size the VPS for the account count, especially if browser-based platforms are involved.
Pick a plan at /pricing/, or set up your multi-account environment on a $1.99 seven-day trial first.
Frequently Asked Questions
Can I run multiple prop firm accounts on one VPS?
Yes, provided all the accounts are yours. That is a normal and widely used setup, and some firms explicitly require a dedicated VPS for traders using automation. What is prohibited is operating accounts belonging to other people.
Will prop firms ban me for using a VPS?
No. Prop firms expect traders to use VPSs and several require one. The ban risk comes from account sharing, not from datacenter hosting.
Should I use a different VPS for each prop firm account?
Generally unnecessary if all the accounts are yours — one consistent IP across your own accounts is a clean signal, not a suspicious one. Separate machines make sense for resource reasons or to isolate a strategy, not for compliance.
Does using a VPN with my VPS improve safety?
The opposite. A consumer VPN gives you a rotating IP shared with many other users, which is the pattern associated with account sharing. Your dedicated VPS IP is the asset here; do not obscure it.
Can I use a trade copier across my prop accounts?
Usually, but check each firm’s rules — a minority restrict copying, and the rules differ between evaluation and funded stages. Also configure per-account rule restrictions, because a copier will otherwise replicate a trade that is legal at one firm into an account where it is not.
How much RAM do I need for four prop accounts?
4GB is the sensible floor for four MetaTrader instances, and it may be tight if any of them are browser-based platforms like TradeLocker or Match-Trader. Watch committed memory during the London open in your first week and size up if it exceeds about 70%.
Related Reading
- Prop Firm Rules: How a VPS Helps Compliance — drawdown, consistency and the other rule categories
- VPS for Prop Firm Challenges — the case for hosting an evaluation properly
- Copy Trading Setup on VPS — multi-account architecture
- Running Multiple MT4 and MT5 Terminals on a VPS — resource planning
- Funded Account Management on VPS — operating a funded account day to day