HonorPro Architecture

Platform architecture · 23 Aug 2026

How the whole thing fits together

One codebase, two products, and one installation per broker. The drawings below show what talks to what, which way each conversation starts, and where a broker's data is and is not allowed to go.

01The platform

HonorProCore terminal · gateway · MT5 bridge · components vendored, pinned vendored, pinned HonorPro360 signs licences · owns the catalogue publishes signed builds our own brokerage runs here too: terminal · MT5 · existing CRM everything ships here before it is sold HonorProHub · Broker A own machines · own MT5 · own clients HonorProHub · Broker B own machines · own MT5 · own clients HonorProHub · next broker one installation each, never shared asks for licence, catalogue, builds Every arrow to 360 starts at the broker. 360 has no route into a broker's network — it can stop selling a component, but it cannot reach in and touch one. A licence is a signed document, so it still verifies while 360 is unreachable.
One shared codebase feeds both products. 360 is the authority and our own brokerage; each Hub is a separate installation on a broker's own infrastructure, and it is always the one that starts the conversation.

02Inside one broker's installation

Web terminal broker's domain Mobile app broker's store listing Broker's staff console, dealing desk BROKER'S LINUX MACHINE Gateway REST + live stream for the terminal orders, quotes, accounts, history binds loopback, published behind TLS Hub licence: verify, refresh, warn console for this installation agent: pulls builds and configs CRM component (or the broker's own) outbound connections only Broker's CRM, if they have one identity and KYC stay there; five calls, no second copy of a client record BROKER'S MT5 SERVER (WINDOWS) MetaTrader 5 server accounts, orders, quotes — the truth Plugin bridge in-process, listens on loopback only Copy engine replicates master to follower accounts HTTPS SSH tunnel to loopback to 360 No trading data leaves this picture. The plugins are never exposed to the internet; the only outbound conversation is the Hub asking 360 for its licence and builds.
One broker, two machines. The gateway serves the clients and reaches MT5 only through a tunnel to loopback; the Hub sits beside it holding the licence, the console and delivery. Whether the CRM is the bundled one or the broker's own changes who answers five calls, nothing else — and the sign-up screen asks an onboarding provider, so a broker running neither still registers clients.

03Bringing a new broker up

1 · One screen name, components, term → the command 2 · Paste and run gateway + Hub + agent, secrets made on the box 3 · Hub pulls licence, catalogue, signed builds 4 · Plugins on MT5 copy, configure, restart the server 5 · Point at MT5 switch the gateway to the real backend the only step that needs a restart window Steps 1 to 3 are reversible and take minutes. Step 4 is trading infrastructure: plan it outside session hours, like any other MT5 server restart.
The order a broker actually goes through, and where the risk sits: everything before the MT5 restart is undoable, everything after it touches a live trading server.

Provisioning is a single pass through one screen — brokerage name, the components they bought, the term — and it returns the licence, the install key and the exact command their engineer pastes onto a clean machine. A pass that cannot be completed writes nothing at all, so there is no half-provisioned broker who is unable to install.

Two things this path used to get wrong, now closed. The installer carried constant credentials that the setup guide published — every installation opened with the same admin password. Nothing constant ships now: the secrets are generated on the broker's own machine, written to a file created private before a byte lands in it, and printed once.

And a fresh installation used to answer with invented prices from a mock backend until someone remembered to switch it. It now refuses to serve clients until a real trading backend actually answers — configured is not the same as connected — while the operator surface stays up, because that is where it gets fixed. A demo installation is still possible, but it announces itself on screen rather than hiding in a config file.

04What the broker holds locally

Everything we ship a broker lands inside their own installation: the installer, the plugin packages, the mobile builds, and the whole documentation set — setup and plugin guides, operations manual, API reference, release notes for the version they are actually running, and a document per component they licensed.

It travels the same path as any build: published by 360, checked against its signature and digest before it touches disk, then served from the Hub's own door. A broker whose network cannot reach us still has their documentation, and anything not yet delivered is named with an offer to fetch it — never a link to somewhere else.

05Where the data is allowed to be

Stays on the broker's own machinesCrosses to 360
Client accounts, balances, positions, orders and history · quotes · KYC documents · support conversations · the CRM record of every client Which components this installation is licensed to run · the signed licence itself · which builds were delivered · health and version of the installation

That split is what lets a broker keep their regulator's answer simple: nothing about their clients or their book is held by us. It is also why the licence is a signed document rather than a permission call — the platform has to keep working through an outage on our side, and it does, on the dates inside the document.

06Which repository builds what

RepositoryShipsRuns where
HonorProCore Terminal (web and mobile), gateway, MT5 plugin bridge, copy engine, admin shell, brand layer Nowhere on its own — vendored into both products at a pinned version
HonorPro360 Licence authority, component catalogue, tenant registry, build publishing, provider console Our infrastructure, alongside our own brokerage
HonorProHub Installation console, agent, delivery, licence client, bundled CRM, branding Each broker's own machine, one installation per broker