Where your data lives, and who can reach it.

Own build per broker on Modern WebTrader. Database isolation on PipLine.

Modern WebTrader · velmora build single-tenant

database address 1 · db_velmora
keys 1
route to another broker none
shared write quotes · price feed

PipLine · sales rep · Kelvar FX RLS

>SELECT customers 3 rows · assigned
>SELECT customers · Velmora Markets 0 rows · no error
>INSERT customer · Velmora Markets rejected · 42501

RLS · enforced in the databaseAPI keys · organization from the key

Simulated isolation checks. Modern WebTrader: the Velmora build holds one database address and one key, has no route to another broker’s database, and its only shared write is quotes from the price feed. PipLine: a Kelvar FX sales rep reads three assigned customers; reading Velmora Markets’ customers returns zero rows; writing into Velmora Markets is rejected with error 42501.

Two isolation models. We build both.

Modern WebTrader: one build and one database per broker.
PipLine: one platform, isolation enforced in the database.

FIG.4 · IsolationSimulated dataStatic

Modern WebTraderone build per broker

W-1
Shared: the price feed. Quotes only, no admin key.quote → 3 databases
W-2
Each broker writes only to its own database.INSERT · db_velmora
W-3
One address, one key. No route between brokers.1 address · 1 key

PipLineone platform

P-1
Reps see only customers assigned to them.3 rows · assigned
P-2
Other organizations are filtered out. No error.0 rows
P-3
Writing into another organization is rejected.rejected · 42501
P-4
IB users see only their own partners.own partners
P-5
One panel over every organization you run.3 orgs · totals
P-6
The AI analyst reads only what you may see.read-only · your permissions
P-7
Integrations are pinned to their organization.org from key

Diagram. Modern WebTrader gives each broker its own build and database; a shared price feed writes only quotes into each. PipLine is one platform: requesters reach one database through row-level security, or through the gateway for API keys; rows carry their organization.

Who sees what, inside PipLine.

Sales reps: Only the customers assigned to them. Team leads see their team.
IB users: Only their own partners.
Company Panel: Totals across your company’s organizations, for authorised managers.
AI data analyst: Reads with the asker’s permissions, one organization at a time. Read-only.
API keys: Pinned to their organization: it comes from the key, not the request.
MT5 sync: Runs under its own database role, with your licensed Manager API login.

Every order, every deposit. Traced.

FIG.3Simulated dataStatic

Order → Ledger

01Quote1.08469
Raw price plus your group markup.
02Checks4/4
Stale feed, hours, slippage, margin: checked before fill.
03Risk engine#4,812
Scheduled sweep runs SL/TP, trailing stops, stop-out.
04LedgerT-884121
Fill written to your database, audit-logged.

Deposit → Net cash

01Request2,500.00
Deposit request from the CRM.
02Approval2,500.00
Approved by an operator.
03PSP fee−62.502.50%
PSP fee at the rate on the transfer date.
04Net cash835,357.50
Posted to net cash and accounting.

Once per cycle, the margin check rejects an oversized order.Two traced paths, simulated data. An order: quote with group markup, four pre-fill checks, a scheduled risk engine, then a write to your own database; once per cycle an oversized order is rejected at the margin check. A deposit: CRM request, operator approval, PSP fee at the dated rate, net cash.

Security questions? Send them through the contact page