Brokerpilot: dealing supervision, risk controls and broker operations

Brokerpilot is Indigosoft’s dealing and risk-management software for FX/CFD brokers. It combines live supervision, account and trading-pattern analysis, historical reports and actions that can change server settings. The distinction between observation and control is central to the product: a desk may inspect exposure with limited access, while a leverage change, trading restriction or balance adjustment requires additional authority. The platform is aimed at the broker’s staff rather than customers seeking a retail trading account.[2]

The anti-fraud product separates patterns such as rapid trading, account relationships and unusually profitable deals so a desk can investigate their context. This is operational classification, not an independently established finding that an account breached a contract. The notification workflow supports that distinction: staff can accept an event, mark it suspicious, exclude an account from a trigger or, where authorised, block further trading while leaving login access available.[15][13]

Brokerpilot’s SaaS setup guide covers MetaTrader 4, MetaTrader 5 and cTrader. MetaTrader uses manager connections and server configuration, while cTrader setup requires environment and connection information from Spotware. A platform appearing in the compatibility list does not establish parity for every administrative operation. The specialised manuals are more specific about which actions require an MT4 or MT5 administrator connection.[7]

The API guide distinguishes frontend REST calls from backend requests and describes how parameters are encoded for those routes. A persistent service token is a material access credential, not a short-lived browser login. The public documentation provides an integration mechanism; it does not establish a contractual bulk-export window or continued API access after a software subscription ends.[10][11]

The public offer directs prospective customers to a demonstration and commercial discussion. The reviewed pages do not publish a monetary licence tariff, minimum commitment, setup fee, per-server charge or usage-rate schedule. SaaS and on-premises are delivery choices rather than publicly priced tiers. A quotation needs to identify the connected servers, enabled functions and service obligations; no zero cost should be inferred for a function simply because its manual is public.[1]

These are the vendor’s stated minimums for the specified footprint, rather than a measured capacity or latency guarantee. Database access must include read, write, deletion and schema/table creation capabilities. “Read-only” therefore cannot describe the entire on-premises application, even if a separate support login on a trading server is restricted to observation.[8]

Historical reporting accumulates data after installation. The documentation says at least a day is needed for initial history and longer periods are needed for weekly or monthly views. It lists cashflow, account balance/equity, commissions, swaps and trading reports, with filtering and export through Metabase. This changes migration expectations: connecting a server is not evidence that the new reporting database immediately contains the broker’s complete legacy history.[16]

Trigger setup requires a defined scope, such as accounts, groups or symbols; an empty scope normally leaves a rule inactive, with documented exceptions such as Account Events. The manual also limits overlapping scopes for several trigger types. These rules are not universal across the suite: Net Dynamic Leverage separately uses ordered precedence when more than one rule matches. The configuration therefore has to be checked against the individual trigger’s operating rules.[12][21]

Brokerpilot advertises 24/7 technical support and resource monitoring for its on-premises option. Public documentation and release notes also provide substantial self-service operating material. The reviewed offer does not specify severity-based response/restoration targets or a guaranteed migration timetable.[1]

The terms identify Indigosoft Software Design LLC as the operator and describe Brokerpilot as software. They exclude brokerage, investment advice, transaction execution as a financial service and management of client money. A software action can still affect a broker’s server when the broker grants the necessary permissions; that technical authority is different from the vendor becoming the financial counterparty. The website terms do not replace the enterprise service and processing agreements.[4]

User administration supports separate module switches and invitations that expire after 24 hours. This provides another control layer above connected-server credentials. The privacy policy offers access, correction, deletion and readable copies of an individual’s personal information via support, while describing retention by purpose and legal need. It does not supply a whole-broker export specification or a fixed universal retention period.[9][6]

The current site identifies the UAE company INDIGOSOFT SOFTWARE DESIGN L.L.C and company licence number 1116215. That identification is not evidence of a financial-services permission.[1]

Indigosoft’s corporate site describes software engineering for financial systems, high-load applications and data analysis, with Brokerpilot as its flagship product. It publishes an operating office in Dubai Industrial City and separately labels an Al Quoz 3 address as the address on its commercial licence. These are two stated address roles; this profile records Dubai without presenting the website disclosure as an independently checked company-register record.[5]

Brokerpilot’s account of its origins describes a former chief dealer building an internal tool and developing it into a commercial product for dealing, risk and operations teams. That development helps explain the combination of analytical screens, operational reports and controls that can act on trading-server settings.[3]

Operator

INDIGOSOFT SOFTWARE DESIGN L.L.C

Service scope

Broker dealing supervision, exposure and account analysis, configurable risk controls, reporting and scheduled server operations.

Customer types

FX and CFD brokers; Brokerage dealing desks; Broker risk and operations teams

Delivery

SaaS; On premises; API

Pricing publication

Quote only

Headquarters

Dubai, United Arab Emirates

Platforms

Brokerpilot

Integrations

REST API; Metabase; CSV exports; MetaTrader 4/5 manager APIs (feature-dependent rights); cTrader connection via Spotware environment

Implementation

Vendor cloud or customer infrastructure; server connections, account permissions and task-specific activation are required.

Support

Publishes sales and support email routes; advertises 24/7 technical support and resource monitoring for the on-premises offer.

Permissions and regulatory scope

Software supplied by a UAE company. The published company licence number does not establish a financial-services authorisation; the terms exclude brokerage and investment services.

Provider metadata checked 20 Oct 2026Source 1Source 3Source 7Source 8Source 4Source 10Source 11Source 16Source 2

Monitoring, plugins and dynamic leverage

Brokerpilot markets its monitoring function as operating without server plugins.[1]

The Net Dynamic Leverage manual documents an MT4/MT5 server plugin configured through Brokerpilot. Its Standard mode applies the selected tier to the full relevant volume; Layered mode applies tiers to portions of that volume. Higher-margin-period rules can change treatment around events, and the manual discusses existing-position treatment, account-leverage limits and overlapping-rule precedence. It warns that other plugins changing open-position margin or leverage can conflict and recommends testing the relevant transitions and logs. No equivalent cTrader implementation is established by this manual.[21]

Scheduled adjustments have action-specific safeguards

Swap editing requires both the relevant MetaTrader permissions and activation by Brokerpilot support; MT5 uses a separate administrator connection. Dividend adjustments require their own accountancy/dealing rights. Their manual contains an explicit option to allow adjustment during a trading session alongside outside-session instructions, so session timing must be read with the enabled setting. A generic claim that every scheduled operation has the same permissions or trading-hours rule would miss these distinctions.[18][20]

Read-only chat, background scanning and model data flows

The chat assistant analyses account metrics and suggests risk or routing decisions without executing those changes. Its server runs internally in Docker, but query results and numerical trading metrics reach an external language model, with specified identity fields excluded. The guide separately assigns OpenAI to documentation and query-text embeddings and says trading/account data is not sent to OpenAI. Conversations are stored locally in MongoDB with configurable automatic deletion; no universal retention duration is stated. A background scanner checks selected accounts and can maintain a watchlist automatically, independently of a chat request. Its labels and scores are analytical outputs, not established findings of misconduct.[22]

Current releases and installed versions

The latest inspected release entry identifies version 3.65.0, with an October 16 heading and October 17, 2026 metadata. It describes a dedicated AI page, changes to markout grouping that distinguish server and symbol, A-book CSV improvements and fixes involving reconnects and cross-server imports. These are published release changes, not confirmation that a particular customer installation has been upgraded. They also show why platform and report behaviour should be matched to the deployed version rather than inferred solely from a general product page.[23]