Company
Built inside a brokerage, for brokerages.
GarnetSync is the CRM and back office for brokerages on MetaTrader 5: leads and clients, approvals, the trading desk, the client portal and partners, on one database connected live to your server. The people who build it run a brokerage, and the first company on it is our own.
GarnetSync, in five lines
In production- What it is
- A multi-tenant CRM and back office for brokerages on MetaTrader 5.
- Who builds it
- People who run a brokerage. Production's first company is our own.
- Where it runs
London, on an encrypted private database.- How it connects
Through MT5's Web API, with a manager login you grant.- How it is checked
- 510 API tests and 744 real-browser checks, at every release.
Why it exists
We needed it ourselves.
A brokerage runs on more than a CRM. It runs on the trading server, the payment details, the KYC files and the partner tree, and on the people who keep them in agreement. GarnetSync puts all of them on one database, connected live to MT5, with each control written where nothing can go round it.
We build it for our own brokerage first: production's first company is ours, connected to its own MT5 server. What gets built is decided by what running a brokerage asks for.
The first deposit we sent to our brokerage's live MT5 server, on its demo groups, showed why the rules matter. MT5's answer didn't match its own documentation: it spelled the ticket field differently. The bridge had recorded the deposit before sending it, found it on the server by its reference a minute later, and never sent it again.
Our own switch comes first, too: the brokerage's previous CRM keeps running while GarnetSync reads the same server, until the numbers agree. What that teaches us goes into the product, and into our guide to a parallel run.
How we work
Six rules, and where each one is kept.
None of these is a slogan. Each is enforced by the product or by how a release ships, and the right-hand column says where.
- 01
Every release has notes
Each release is written up before it ships: what changed, how it was verified and how to roll it back. The production database is snapshotted first, and the release goes out only when a person approves it.
Where it's keptA snapshot before every production release
- 02
Every claim is tested
510 API tests and eight walks through the product in a real Chrome, 744 checks in all, run at every release, not only for the part that changed. The safeguards also get deliberately broken copies, mutants, that their tests have to catch.
Where it's kept510 tests and 744 browser checks
- 03
Controls live in the database
Two people above the threshold, both documents before a KYC approval, a sub-partner never paid above its parent: each rule is written once, in the database, so no screen, script or role can disagree with it.
Where it's keptRow-level security on 58 tables
- 04
Nothing is deleted
No role can delete or rewrite a ledger entry, a request or an account. Corrections are new entries, MT5 accounts are archived, and the audit log records who did what, with the before and after.
Where it's keptUPDATE and DELETE revoked on the audit log
- 05
Money moves once
A balance operation is a database row before anything is sent to MT5. If an answer is lost, the server's deals are searched for its reference, and it is sent again only once it is proven absent.
Where it's keptAt most 3 sends, then a person
- 06
Your brand, never ours
Clients see your name, your colours and your own web address. A deposit's deal comment reads Deposit #7F3K9QX2M4PA and names nobody, and GarnetSync's name stays off your MT5 server.
Where it's keptA portal address containing 'garnet' is refused
Where it runs
What we didn't build, named.
GarnetSync runs on a short list of other people's services, each doing one job.
- Production, in London: an encrypted private database, and no SSH into the servers.
- Its Web API, through a manager login you grant, with no delete, Configuration or Administration rights.
- CloudflareThe certificate for your portal's own address, and the bot check on its sign-up form.
- BrevoMail to your clients, from your own domain once its DNS records and a code sent to the address check out.
- ClamAVScans every uploaded document beside the API, so files never leave our servers.
Cloudflare
BrevoNames and logos belong to their owners and are shown to say what GarnetSync uses.
The name
Why garnet?
A garnet crystal has many faces and is still one stone. That is the idea: the CRM, the back office, the portal, the partners and the desk as faces of one database, never out of step with each other or with the server.
Where to next
See it on a demo brokerage.
Thirty minutes on Corvane Markets, our demo brokerage on an MT5 test server: the desk, approvals and the client portal.