Setting up MT4 PAMM on MetaTrader 4 starts with preparing the broker’s existing MT4 infrastructure.
The exact technical requirements depend on the MT4 PAMM provider and the integration architecture, but the core server-side requirements are generally similar.
1. MT4 Server and Account Group Requirements
The broker needs its own licensed and operational MetaTrader 4 server.
When assessing the legal requirements for running PAMM on MT4, the broker should confirm that its licence and local rules allow it to offer pooled investment services.
The PAMM setup should include 2 dedicated account groups:
- Leader group
- Investor group
Accounts participating in the same PAMM pool should use 1 deposit currency. This keeps deposits, withdrawals, P&L, fees, investor shares, and settlements within the same accounting basis.
The broker should also configure withdrawal permissions for leader accounts at the MT4 group or account level. Since the leader’s own balance can participate in the PAMM pool, withdrawals affect pool equity, available margin, and settlement calculations.
2. MT4 Manager Account Requirements
The PAMM service needs a Manager account with access to both Leader and Investor groups.
The account should have sufficient permissions for the operations used by PAMM, including:
- access to manager and investor accounts
- account balance information
- balance operations
- access to open trades
- access to trading history
- account and group information
The Manager account’s visibility mask should include all MT4 groups participating in PAMM so that the service can access both sides of the investment structure.
The exact MT4 access rights and integration method depend on the PAMM provider and should be configured for the specific installation.
3. PAMM Host Server Requirements
The PAMM application is deployed as a Windows Service on a Windows Server connected to the broker’s MetaTrader environment.
For the Takeprofit PAMM server environment, the application stack includes:
- OS: Windows Server
- Backend runtime: .NET 10
- Frontend: React 19
- Database: SQLite
- Database path: Contents/pamm.db
- Encryption key storage: Contents/keys/
The PAMM database stores application-side data such as:
- investments
- investor shares
- allocation history
- settlements
- fee calculations
- high-water marks
- operational records
The database and the encryption keyring should be included in the same backup procedure. Stored MetaTrader Manager credentials depend on the keyring, so both are required to restore the PAMM service correctly.
4. PAMM Configuration and Credentials
Administrative credentials for the PAMM service are configured on the application side.
In the current Takeprofit PAMM architecture, admin credentials are stored through the application configuration, while MetaTrader Manager credentials are protected using the server-side encryption keyring.
The broker should therefore include the following in the PAMM backup and disaster-recovery process:
- PAMM database
- application configuration
- encryption keys
- MetaTrader connection credentials
- other environment-specific service settings
5. MT4 Trading and Risk Settings
Risk management in a PAMM setup can be applied at both the PAMM and MT4 server levels.
Within the PAMM application, the broker can configure investment-level controls such as:
- investor risk limits
- stop-loss protection
- settlement rules
- withdrawal and exit logic
- investment restrictions
The MT4 server controls the trading conditions for PAMM accounts, including:
- leverage
- margin
- stop-out
- symbol restrictions
- trading permissions
- account-level restrictions
- group-level trading conditions
Additional server-side risk plugins can also be included when planning how to set up MT4 PAMM.
For example, broker-side controls can enforce:
- drawdown limits
- equity thresholds
- daily loss limits
- exposure restrictions
These settings define how PAMM protects investor funds across both the investment and trading processes.
6. Split of Responsibilities Between MT4 and PAMM
The PAMM application manages the investment side:
- leader and investor relationships
- investor shares
- allocation calculations
- investment history
- settlements
- fee calculations
- high-water marks
- investor entry and exit
MetaTrader manages the trading side:
- trading accounts
- orders and positions
- execution
- leverage
- margin
- stop-out
- symbols
- trading permissions
- server-side account restrictions
This split is important when comparing PAMM vs MAM on MT4. In MAM, proportional trades are created on individual investor accounts, so the responsibilities between the money-management system and the MT4 server are distributed differently from a pooled PAMM structure.
MT4 PAMM Server Requirements Checklist
Before deployment, the broker should prepare:
- a licensed and operational MT4 server
- 2 dedicated groups: Leader and Investor
- 1 deposit currency within each PAMM pool
- withdrawal controls for leader accounts
- an MT4 Manager account with access to both groups
- permissions for account, balance, trade, and history data
- Windows Server
- .NET 10
- React 19
- SQLite database
- backup of Contents/pamm.db
- backup of Contents/keys/
- configured MT4 leverage, margin, stop-out, and trading permissions
Learn more
Try MT4 PAMM with Takeprofit Tech.