EA Trading at Sway Funded: Rules, Setup, and What's Prohibited

Sway Funded permits Expert Advisors and automated trading systems on both challenge and funded accounts, subject to compliance with the firm's trading rules. The catch is that Sway's proprietary platform Liquid Charts is not MetaTrader; MT4 and MT5 EAs cannot run directly on Liquid Charts and must be connected via a copy trading bridge. This guide covers the rules, setup requirements, prohibited behaviours, and operational considerations for running EAs on Sway Funded accounts.

The structural posture at Sway is permissive but rule-bound. Algorithmic execution is welcome as long as the strategy itself complies with the firm's prohibited-pattern list. The list focuses on three categories: HFT-style execution, cross-broker arbitrage, and latency-exploitation strategies. Strategies outside those categories generally run cleanly on Sway accounts.

EA compliance checklist at a glance

Run through every row before connecting any EA to a Sway account. Each item is a structural compliance gate; missing one creates an outsized risk of account suspension during the funded phase.

Permitted EA types at Sway Funded

Most retail EA categories are permitted on Sway Funded accounts. The permitted list is wide because Sway focuses on prohibiting behaviour patterns rather than EA categories themselves. An EA that produces a 15-minute average trade duration with 3 to 10 trades per day fits cleanly; an EA that fires 200 trades per hour does not.

Categories that fit

• Trend-following EAs with hourly or daily timeframes
• Mean-reversion EAs targeting session ranges
• Breakout EAs entering on confirmed range exits
• News-event EAs operating outside the 5-minute buffer
• Grid-style EAs with conservative sizing and structured exits
• Algorithmic execution of discretionary signals from external systems

Categories that fight the structure

• High-frequency trading EAs firing dozens of trades per minute
• Cross-broker arbitrage scripts comparing price feeds
• Latency-exploitation systems profiting from feed-delay differences
• Tick-scalping EAs with sub-second trade durations
• Cross-account hedging systems that open opposing positions

Why Liquid Charts is not MetaTrader

Sway Funded uses Liquid Charts as its primary trading platform. Liquid Charts is a proprietary platform built specifically for the firm; it is not MetaQuotes' MT4 or MT5. This matters for EA traders because MT4 and MT5 EAs are coded in MQL4 or MQL5 and run inside the MetaTrader runtime. Liquid Charts does not have that runtime, which means MT4 and MT5 EAs cannot execute natively on the platform.

The workaround is to run the EA on a separate MT4 or MT5 instance (typically on a VPS) and connect that instance to the Sway Liquid Charts account via a copy trading bridge service. The bridge replays trades from the MT4/MT5 source to the Sway account in real time. The mechanic is operationally well-established across the prop firm industry; many firms with proprietary platforms support EA traders this way.

Copy trading bridges in practice

Several copy trading services support Liquid Charts as a destination. The bridge service typically runs as a third application alongside the source MT4/MT5 and connects via API to the Sway account. Latency through a good bridge service is typically 50 to 200 milliseconds, which is acceptable for any strategy outside the prohibited HFT category. Latency-sensitive strategies should not use Sway's bridge architecture; their structural fit at Sway is poor regardless of EA permission.

Setting up an MT4 or MT5 EA to copy to Sway

1. Choose a VPS provider with low latency to Liquid Brokers' server region
2. Install MT4 or MT5 on the VPS and connect to a retail broker for the source feed
3. Load and test the EA on the source MT4/MT5 in a paper or demo environment
4. Install the chosen copy trading service on the same VPS
5. Configure the copy service to send signals to the Sway Liquid Charts account
6. Test the entire chain end to end with small position sizes before live trading
7. Confirm trade replication latency, position sizing accuracy, and stop placement

Why VPS hosting matters

Running an EA on a home computer creates two failure modes: power outages and internet disruptions both kill the EA execution mid-trade. A VPS eliminates both because it runs in a professional data centre with redundant power and network connections. Most EA traders treat VPS hosting as non-optional rather than nice-to-have for any serious automation.

VPS location matters for latency. European data centres in London, Frankfurt, or Amsterdam typically produce the lowest latency to Liquid Brokers' servers given the GMT+2 to GMT+3 server time zone. North American VPS locations add 100 to 150 milliseconds of latency, which is usually acceptable for non-HFT strategies but suboptimal for tight scalping.

Prohibited patterns in detail

Three categories of prohibited behaviour cover most of what Sway will flag during automated trading: HFT patterns, arbitrage, and latency exploitation. Each has a specific technical fingerprint that the firm's monitoring systems can identify in trade history data, independent of whether the trade was placed manually or by an EA.

HFT patterns

HFT typically shows up in trade history as dozens or hundreds of trades per minute with sub-second durations. Sway's monitoring flags this pattern regardless of whether the strategy is technically profitable. The reason is that HFT exploits market microstructure in ways that retail-style prop firms do not want to support. An EA designed to trade once every 15 minutes does not look anything like HFT in the trade log.

Cross-broker arbitrage

Arbitrage strategies compare price feeds across multiple brokers and profit from temporary discrepancies. The pattern shows up as trades that consistently profit from short-term feed asymmetries, with trade timing tightly clustered around the asymmetry windows. The behaviour is prohibited across nearly all prop firms because the firm itself becomes the liquidity provider absorbing the arbitrage loss.

Latency exploitation

Latency exploitation profits from the time delay between the firm's price feed and another, faster feed. The pattern is subtle but identifiable in trade timing data. Sway prohibits it for the same reason as arbitrage: the firm loses money on these patterns systematically. Traders sometimes inadvertently approximate this pattern with high-quality external feeds, which is why running the source MT4/MT5 on the same broker feed type as Sway uses reduces the risk of inadvertent flags.

Position sizing compliance for EAs

Sway's standard risk rules apply to EA execution: max risk per trade typically 1 percent of account balance, daily loss limit at 4 to 5 percent, and overall max drawdown enforced. Configure the EA to respect these rules at the position-sizing level so that no individual trade can breach the limits even in adverse conditions.

Daily loss limit kill switch

The single most important EA safeguard for a prop firm account is a daily loss limit kill switch set at 4 percent (below the 5 percent hard limit). The kill switch prevents the EA from breaching the daily limit during a losing session without manual intervention. EAs without this safeguard can blow through the daily limit in minutes during adverse market conditions, terminating the account.

Implement the kill switch at two layers: in the EA's own code (preferred) and at the VPS / source MT4 level via account-monitoring scripts (as a backup). Two-layer protection is cheap to set up and catches scenarios where the EA itself malfunctions and ignores its own internal kill switch.

News trading restrictions

Sway enforces a 5-minute buffer around high-impact news releases on certain instruments. EAs trading those instruments must pause during the buffer window. Most modern EAs support news filter plugins that read economic calendar feeds and disable execution during configured windows; verify the EA's news filter accuracy against Sway's specific buffer policy.

Cross-account hedging detection

Sway prohibits cross-account hedging where opposing positions on the same instrument are opened across accounts the same trader controls. The detection runs across account ownership rather than per-account, so multiple Sway accounts under the same trader profile are all checked. An EA running the same strategy across two accounts at opposite biases would trigger this flag.

The cleanest single-account operating posture is to run the EA on one Sway account at a time and use peer firms or retail brokers for second accounts if multi-seat strategy testing is needed. Cross-firm hedging is not prohibited as long as it does not involve two Sway accounts.

Common EA-trading mistakes at Sway

• Assuming MT4 or MT5 EAs run natively on Liquid Charts
• Skipping VPS setup and running EAs on a home computer
• Missing the daily loss limit kill switch in the EA configuration
• Choosing a copy trading bridge without testing Liquid Charts compatibility
• Running latency-sensitive strategies that approximate prohibited patterns
• Opening multiple Sway accounts with opposing-bias EAs
• Forgetting the news filter and trading through restricted release buffers

Backtesting requirements before live deployment

Run the EA through a minimum 6-month backtest at retail-broker conditions before connecting to Sway. The backtest should confirm trade frequency stays under HFT thresholds, drawdown stays within Sway's daily and overall limits, and the strategy produces positive expectancy at conservative position sizes. Forward-test the EA on demo for at least 2 weeks before connecting to a live Sway challenge.

Monitoring and incident response

Active monitoring is essential even with EAs designed to run hands-free. Set up alerts for unusual trade frequency, drawdown approaching daily limit, and any technical disconnection between the source MT4/MT5 and the Sway destination account. Plan an incident response that includes pausing the EA, closing open positions safely, and reviewing the issue before resuming.

Algo style and Sway product fit

EAs that produce flat daily P&L distributions fit Sway's consistency rules naturally. EAs that concentrate profit on a few big sessions can fight Sway's specific consistency-rule mechanic. Match EA design to the funded-phase rule structure to avoid post-pass payout friction; the EA that passed the challenge may not be the same EA that produces clean funded payouts if the rule sets differ between phases.

Bridge service vendor considerations

Several copy trading bridges support Liquid Charts as a destination. Choose a bridge with documented Liquid Charts integration, demonstrable execution latency under 200 milliseconds, and active support for the specific MT4 or MT5 source you are running. Test the bridge end to end on a demo Sway account before purchasing a live challenge; bridge issues are the most common operational failure point for EA traders on proprietary-platform prop firms.

Edge cases and special situations

A few less common situations come up often enough on Sway EA accounts to warrant explicit treatment. The first is the EA-vendor update that changes execution behaviour mid-challenge; pause execution and forward-test the new version before resuming on live accounts. The second is bridge service downtime that suspends trade replication; have a manual close-positions plan ready for these windows. The third is EA-specific behaviour during weekend or holiday gaps; many EAs do not account for gap risk and need supplementary controls.

Comparing Sway EA support to peer firms

Sway's EA support posture is broadly similar to peer prop firms that run proprietary platforms. The proprietary-platform category (Sway, Lucid, Tradeify on certain accounts) requires bridge architecture for MT4/MT5 EAs. The MetaTrader-native category (FTMO, FundingPips, FundedNext) supports EAs directly without a bridge. The trade-off is platform freedom versus bridge overhead.

Performance considerations on bridge-architecture EA execution

The 50 to 200 millisecond bridge latency creates real execution slippage on entry and exit orders. For a strategy with average trade duration of 15 minutes, 100 milliseconds of slippage on entry and exit costs roughly 0.1 percent of trade P&L on volatile instruments. The cost is small for swing or trend strategies; it grows large for tight scalping or news-reactive strategies.

Slippage by strategy type

EA development for Sway specifically

Traders building EAs from scratch for use on Sway should design with three constraints in mind: trade frequency below HFT thresholds (under 10 trades per hour as a safe ceiling), bounded per-trade risk at 1 percent or less, and built-in compliance with the daily loss limit. Building these constraints into the EA at the design stage produces a cleaner result than retrofitting them onto an existing EA that was designed for different rule sets.

Sway funded-phase rules and EA interaction

After passing the Sway challenge, the funded account applies its own rule set that EAs must respect. Verify the specific funded-phase consistency rules, payout caps, and any additional restrictions in the Sway dashboard. EAs that passed the challenge under one rule set sometimes need re-tuning for the funded phase if the rules differ. The cleanest approach is to design the EA against the funded-phase rule set from the start so the challenge phase rules are a strict subset of the EA's compliance envelope.

Operational checklist before going live

1. Confirm EA strategy passes 6-month retail backtest at conservative sizing
2. Confirm EA has 2 weeks of clean demo forward-test on the bridge architecture
3. Confirm VPS is configured with auto-restart and monitoring alerts
4. Confirm copy trading bridge is set up and tested end to end
5. Confirm daily loss limit kill switch is implemented in EA and at VPS layer
6. Confirm news filter is configured against current Sway buffer policy
7. Confirm position sizing math respects 1 percent per-trade and 4 percent daily anchors
8. Confirm incident response plan is documented and tested with manual close drill

Cost considerations for EA traders

Running EAs on Sway involves three recurring costs beyond the prop firm fees: VPS hosting (typically $20 to $50 per month for a prop-suitable VPS), copy trading bridge subscription (typically $10 to $50 per month per account), and source MT4/MT5 broker connection (often free with retail brokers but check terms). The combined operational stack adds $30 to $100 per month to the cost of running EAs on Sway accounts.

Multi-account EA management

Traders running EAs across multiple Sway accounts face additional operational complexity. Each Sway account requires its own bridge connection from the source MT4/MT5; the bridge service typically charges per account, and the VPS must have enough processing capacity to run multiple bridge instances cleanly. The economics scale roughly linearly: 3 Sway accounts means 3 bridge subscriptions and roughly 3x the operational monitoring effort.

Multi-account management also amplifies the cross-account hedging risk. EAs must run with consistent biases across all Sway accounts the trader controls. The simplest compliance posture is to run identical EA configurations across all accounts so that there is no possibility of opposing positions on the same instrument.

Failure modes and how to handle them

Three failure modes account for most operational issues with EA execution on Sway: VPS or source connection failure, bridge service downtime, and EA self-malfunction. Each has a specific response pattern that should be planned before going live rather than improvised during the incident.

VPS or source connection failure

The source MT4/MT5 stops feeding signals to the bridge. The Sway destination account has whatever open positions existed at the time of failure and receives no further EA-driven actions until the source restores. Response: monitor for the disconnect via VPS-level alerts, log into Sway directly to assess open positions, manually close or adjust if the disconnect extends beyond a few minutes.

Bridge service downtime

The source MT4/MT5 fires signals but the bridge does not relay them to Sway. Open positions on Sway remain static; new entries do not happen. Response: same as VPS failure, monitor and intervene manually. Some bridge services have failover routes; verify availability before relying on them.

EA self-malfunction

The EA enters an unintended state, perhaps because of a market condition the developer did not anticipate. The trades that flow to Sway may not match the intended strategy. Response: stop the EA, close positions on Sway directly, debug the EA in a sandbox before resuming. The two-layer kill switch should catch most of these scenarios automatically. The pattern of EA malfunction is most common during regime changes (high-volatility events the EA was not designed for), parameter optimization bugs, and broker feed-data anomalies that the EA's data-handling logic does not gracefully manage.

EA testing methodology before Sway deployment

A structured testing methodology reduces the chance of expensive surprises on a live Sway challenge. Stage testing through retail backtest, demo forward-test, and small live test before scaling to full position sizes.

1. Stage 1: 6-month backtest on retail broker data at conservative sizing
2. Stage 2: 2-week demo forward-test on the full bridge architecture
3. Stage 3: 1-week live test on a small Sway challenge at minimum position sizes
4. Stage 4: Scale up to full position sizing on the live challenge
5. Stage 5: After pass, continue monitoring on funded account at scaled sizing

Documentation and journaling for EA execution

Maintain a journal of EA performance across all stages of testing and live execution. Document the EA version running, the bridge service version, the VPS location, the source MT4/MT5 broker, and any configuration changes between test runs. The journal becomes essential if you need to investigate an unexpected trade pattern or respond to a Sway compliance inquiry. The journal also informs scaling decisions because the data accumulated across multiple weeks of execution reveals patterns that single-week snapshots miss.

When EA trading is not the right choice at Sway

EA trading is structurally a good fit at Sway for strategies producing flat daily distributions at non-HFT frequencies. It is not the right fit for traders new to automation who lack the operational discipline to maintain VPS infrastructure, monitor bridge connections, or respond to incident scenarios. The overhead of EA operations is meaningful; discretionary traders should not adopt EA execution unless the strategy genuinely benefits from automation. The 30 to 100 dollars per month operational cost plus the time investment compounds against the trader if the EA does not produce a meaningfully better outcome than discretionary execution would have.

Bottom line

EAs are permitted at Sway Funded provided the strategy itself complies with the firm's prohibited-pattern list (HFT, arbitrage, latency exploitation). MT4 and MT5 EAs cannot run natively on Liquid Charts but connect via copy trading bridges; VPS hosting in European data centres is the recommended setup. The single most important safeguard is a daily loss limit kill switch at 4 percent on the EA, plus a backup layer at the source MT4 level. Run a minimum 6-month backtest plus 2-week demo forward-test before connecting any EA to a live Sway challenge. Match EA design to Sway's funded-phase consistency rules to avoid post-pass payout friction. The operational overhead of bridge architecture plus VPS plus monitoring adds 30 to 100 dollars per month and meaningful time commitment, which is the structural reason EA execution at Sway only fits traders whose strategy genuinely benefits from automation rather than every trader looking for a hands-off solution.

Frequently Asked Questions

Are EAs allowed on Sway Funded challenges?

Yes, EAs, bots, and copy trading are permitted on both challenge and funded accounts. The underlying strategy must comply with all rules, which includes Sway's prohibited-pattern list covering HFT, cross-broker arbitrage, and latency exploitation. EAs running standard retail strategies at reasonable trade frequencies fit cleanly within the rule set.

Can I run an MT4 or MT5 EA directly on Liquid Charts?

No, Liquid Charts is not MT4 or MT5. MT4 and MT5 EAs must be connected to Liquid Charts via a copy trading bridge service that runs on a separate MT4 or MT5 instance, typically on a VPS. The bridge replays trades from the source MetaTrader to the Sway account in real time. This setup is operationally standard for prop firms with proprietary platforms.

What is prohibited for automated trading at Sway Funded?

HFT, price arbitrage between brokers, latency exploitation, cross-account hedging, and trading on non-public information are all prohibited. Each has a specific technical fingerprint in trade history data that Sway's monitoring systems can identify independent of whether trades were placed manually or by an EA. The behaviour itself is the rule trigger, not the execution method.

How do I connect an MT4 EA to Sway Funded's Liquid Charts?

Run the EA on a separate MT4 or MT5 terminal (local machine or VPS) connected to a retail broker for the source feed. Connect a copy trading service compatible with Liquid Charts to relay trades from the source MetaTrader to your Sway Funded account. The chain has three components: source MT4/MT5, bridge service, and Sway Liquid Charts account.

Does Sway Funded monitor automated trading patterns?

Yes, prop firms monitor trading behaviour regardless of whether it is manual or automated. Prohibited patterns like HFT or arbitrage are identifiable in trade history data through analytic signatures: trade frequency per minute, average duration, profitable-tick-asymmetry rate, and others. Sway's monitoring runs on all accounts and flags patterns matching the prohibited list.

Do I need a VPS for EA trading at Sway Funded?

Not strictly required but strongly recommended. A VPS provides continuous uptime, lower latency, and stable performance, particularly important for time-sensitive strategies or 24/7 automated execution. Running EAs from a home computer creates failure modes (power outages, internet disruptions) that can kill execution mid-trade and lead to account-rule breaches the trader cannot recover from.

Where should I locate my VPS for trading Sway Funded?

European server locations like London, Frankfurt, or Amsterdam minimize latency to Liquid Brokers' servers given the GMT+2 to GMT+3 server time zone. North American VPS locations add 100 to 150 milliseconds of latency, which is acceptable for non-HFT strategies but suboptimal for tight scalping. Latency under 100 ms is the practical target for serious EA traders.

What is the most important EA safeguard for a prop firm account?

A daily loss limit kill switch set at 4 percent (below the 5 percent hard limit). This prevents the EA from breaching the daily limit during a losing session without manual intervention. Implement the kill switch at two layers: in the EA's own code (preferred) and at the VPS or source MT4 level via account-monitoring scripts as backup. Two-layer protection catches EA self-malfunctions.

Can I use a copy trading service from another prop firm's MT5 account to copy to Sway Funded?

Potentially, but verify the source account is not on a Sway Funded account, which could constitute cross-account hedging if positions oppose. Using a retail broker MT5 as the signal source is typically fine. The compliance question is whether the source-destination pair triggers Sway's cross-account hedging rule or the broader cross-broker arbitrage rule.

What happens if my EA accidentally triggers a prohibited pattern?

The account may be flagged, reviewed, or closed. Sway Funded's terms allow them to void trades or accounts found to be in violation of prohibited behaviours. The flag is usually triggered by automated monitoring rather than human review, which means once the pattern appears the account is at risk regardless of whether the trader intended to violate the rules. Test thoroughly before live deployment.

How long should I backtest an EA before connecting to Sway Funded?

Minimum 6 months of backtesting at retail-broker conditions, plus 2 weeks of forward-testing on demo. The backtest should confirm trade frequency stays under HFT thresholds, drawdown stays within Sway's daily and overall limits, and the strategy produces positive expectancy at conservative position sizes. Forward-testing catches issues that backtests miss because of slippage and execution differences.

Can the EA bridge handle the news filter requirement?

Most modern EAs support news filter plugins that read economic calendar feeds and disable execution during configured windows. Verify the EA's news filter accuracy against Sway's specific buffer policy (typically 5 minutes around high-impact releases on certain instruments). The filter should pause both new entries and EA-controlled exits during the buffer window.

Does the bridge service add latency that affects strategy performance?

Yes, copy trading bridges typically add 50 to 200 milliseconds of latency between source and destination. The added latency is acceptable for any strategy outside the prohibited HFT category. Latency-sensitive strategies (scalping with sub-30-second durations) suffer materially from bridge latency; their structural fit at Sway is poor regardless of EA permission.

Can I run the same EA on multiple Sway accounts?

Same EA on the same direction is permitted, but cross-account hedging (opposing positions on the same instrument) triggers the cross-account hedging prohibition. Running the same long-bias EA on two Sway accounts is fine; running a long EA on one and a short EA on the other for the same instrument is not.

What if my source MT4 broker shuts down or has a feed issue?

Trade replication pauses until the source feed restores. Open positions on the Sway destination account remain open but receive no new EA-driven adjustments during the outage. Have a manual close-positions plan ready for these windows because EA-driven exits will not fire during the source outage. This is one of the operational failure points that VPS hosting alone does not solve.

Do EA traders need a separate Sway Funded plan or platform?

No, EA traders use the same Sway Funded plans and the same Liquid Charts platform as discretionary traders. The difference is purely in how trades reach the platform: discretionary traders click manually, EA traders relay through a copy trading bridge. The funded rules, drawdown limits, and consistency requirements are identical regardless of execution method.