Takeprofit Bridge is an alternative to oneZero Hub.
With Takeprofit Bridge, the onboarding process is a sequence of installation and configuration steps: deploying the bridge, connecting liquidity providers, mapping instruments, setting routing and risk rules, testing the setup, and handing access over to the broker’s team.
The process below shows what happens from the first installation files to the first verified order.
What You Receive to Start
The Takeprofit Tech support team provides two core components:
- the bridge bundle, which contains the software
- the license file, which is required for the bridge to run
On the broker’s side, the main infrastructure requirements are a Windows server and PostgreSQL 14 for the database.
Installing Takeprofit Bridge
The installation itself is relatively short.
The bridge bundle can be unpacked into any folder on the server. The folder name becomes the Windows service name.
After that:
- Place the license file in the root bridge folder.
- Install PostgreSQL.
- Open Contents\appsettings.json.
- Configure the main parameters, including the web interface address and port, API port, FIX defaults, database connection, and logging.
- Run _service install.bat as administrator.
- Run _service start.bat as administrator.
Once the service starts, the bridge GUI becomes available in a browser at the address and port configured in the settings file.
The installation itself is only the first part. Most of the onboarding work happens in the software interface, where liquidity, symbols, routing, accounts, and client connections are configured.
Takeprofit Bridge Configuration: Recommended Order
The order of configuration matters because most objects depend on settings created earlier in the process.
1. Create bridge symbols
The first step is to create the instruments that will exist inside the bridge.
These are the internal symbols against which liquidity from different providers is mapped and aggregated.
If an instrument has only one liquidity source, the manual recommends adding the provider name to the symbol, for example: EUR/USD.lp1or EUR/USD.lp2.
This helps distinguish instruments that are intentionally tied to a specific source.
2. Create liquidity providers
Next, create the makers.
A maker represents one connection to one liquidity provider. The connection is configured using the FIX credentials supplied by that provider.
Each provider is added separately, so brokers can connect several LPs and manage them from the same bridge environment.
3. Map provider symbols
Liquidity providers often use different symbol names, contract specifications, volume settings, and tick sizes.
Each provider symbol therefore needs to be mapped to the corresponding bridge symbol.
During mapping, the broker can configure settings such as markups, volumes, price multipliers, volume factors, volume steps, and tick sizes.
This normalizes liquidity from different providers before it is used in the common order book.
4. Configure aggregation and provider priority
Once the symbols are mapped, aggregation logic can be set for each instrument.
Simple aggregation may be used where only one provider is available.
Where several liquidity providers cover the same instrument, the broker can configure a priority list to determine the preferred execution order between them.
This is also the stage where the broker defines how the software should behave if the preferred source becomes unavailable.
5. Create risk profiles
Risk profiles define the rules applied to trading activity before orders are routed further.
Where several margin accounts are planned, the recommended approach is to create a separate risk profile for each account.
This keeps account-level routing and risk settings easier to manage independently.
6. Create and fund margin accounts
Margin accounts are then created and funded.
They are used by the system to track exposure and execution against liquidity providers.
For full A-book execution, the manual recommends disabling Allow SO.
7. Create price channels
Price channels determine what each client receives from the bridge.
They can define the available instruments, markups, spread limits, and depth settings.
When several liquidity providers support the same instrument, the recommended setup is to use one price channel per provider. This helps ensure that orders are routed consistently to the intended liquidity source.
8. Create takers and attach price channels
A taker is the downstream connection consuming liquidity from the bridge. This may be an MT4 or MT5 server connected through a bridge, a white-label partner, or another external client.
At this stage, the required price channels are assigned to the taker.
There is also an infrastructure dependency here: the bridge server IP address and the relevant taker ports must be whitelisted for incoming client connections.
This is one of the few onboarding steps that may depend on another infrastructure or networking team.
9. Place a test trade
Before real trading flow is enabled, a test trade should be placed.
The result can then be checked in the Orders screen, particularly the maker column, to confirm that the order was routed to the expected liquidity provider.
This is the final practical verification that symbols, routing, risk rules, accounts, and taker settings work together as intended.
10. Create users and roles
Once the core trading configuration is complete, user accounts and access roles can be created for the people who will work with the bridge.
This allows the broker to separate operational, dealing, monitoring, and administrative access where required.
When to Make Configuration Changes
Routine configuration changes do not require development work, but timing still matters.
The manual recommends making non-urgent configuration changes, especially bulk spreadsheet imports, during periods of the lowest trading load.
For large updates, the weekend is generally the preferred maintenance window.
Two Features That Shorten Onboarding
Bulk import
Large symbol sets do not have to be entered manually. Takeprofit Bridge supports TSV import and export for:
- instrument settings
- price-channel rules
- provider symbol mappings
Symbol sets can also be imported from an MT5 server export.
For brokers working with hundreds of instruments, this can reduce setup time significantly compared with configuring every symbol individually.
Test orders
Takeprofit Bridge also allows the routing configuration to be tested without sending a real order to a liquidity provider.
The bridge can generate an order as if it came from a selected taker and run it through the complete configuration chain, including the price channel, risk profile, and routing rules.
The result is shown in the system, but the order is destroyed immediately before it reaches the provider.
This gives the broker a way to validate routing logic before live trading begins.
Migration from oneZero and PrimeXM
Brokers planning to migrate from oneZero Hub to Takeprofit Bridge, or evaluating Takeprofit Bridge as an alternative to PrimeXM XCore, can follow the same staged process, moving liquidity and client connections gradually while keeping the existing setup available during the transition.
What Happens After Go-Live
Once Takeprofit Bridge API and FIX integration and onboarding is complete, Takeprofit Tech continues to support the broker during day-to-day operation of the Bridge.
Personal account manager
Each broker has a dedicated personal manager who stays in contact after onboarding and helps coordinate ongoing requests and product questions, including its improvements and custom developments.
Brokers can discuss how customizable Takeprofit Bridge is in terms of additional functionality, new liquidity provider connections, and risk configuration changes.
Ticket-based support
For configuration questions, connectivity issues, and other non-critical technical requests, brokers can use the support ticket system, where issues are tracked, assigned, and resolved in a structured way.
24/7 emergency support
For critical incidents, brokers have access to a 24/7 emergency support line.
Updates
A few times a year, we release bridge updates with new features and additional functionality.
Bridge updates are performed by replacing the relevant files and restarting the service. After an update, the recommended checks include confirming that there are no GUI or log errors, makers and takers have reconnected, quotes are flowing correctly, and no unexpected rejects are appearing.
Conclusion
For brokers with multiple liquidity providers, Takeprofit Bridge performs as a single environment for managing connectivity, aggregation, routing, risk settings, monitoring, and ongoing operational changes.
See how Takeprofit Bridge compares as an alternative to oneZero Hub.