Questions and answers
Solo 76 sells software, not financial services. Because the product lives next to trading, the questions below come up often enough to answer them in one place.
Is Solo 76 a broker or an exchange?
No. Solo 76 sells software. The Trading Strategy Engine is a licensed binary library that you install and run on your own machine. It has no venue of its own, no order book of its own and no counterparty role. Where an order goes is decided by the venue and the market-data feed you contract with directly.
Does Solo 76 hold my money or my assets?
No. There is no customer account, no wallet, no deposit and no withdrawal. The only money that changes hands is the licence fee for the software. Your trading capital stays where it already is — at your own broker or venue — and Solo 76 never has access to it and never acts on it.
Is Solo 76 regulated by a financial authority?
No, and it does not need to be. A financial-regulator licence covers firms that execute orders, take custody of client assets or give investment advice. Solo 76 does none of these: it supplies a developer tool. Whatever obligations you have towards your own regulator follow from what you do, and they are neither created nor removed by the tool you use.
Where do my data and my strategy logic go?
Nowhere. The engine runs entirely on your premises: strategy logic, market data and order flow never leave your perimeter. The software contacts Solo 76 only to check its licence. That request carries the licence identifier, hashed identifiers of the machine, the licence's robot ceiling, the highest number of robots the machine has run at once, and a description of the environment: native, virtual or container, the hypervisor, a boot identifier and the local time. On Windows the boot identifier includes the machine's MachineGuid unhashed. Nothing in the request says what those robots do, what they trade or what they hold; chapter 9 of the reference lists it field by field.
Can I move my licence to another machine?
Yes. A licence runs on one machine at a time: it binds to the machine the engine first runs on, identified by a coarse hardware fingerprint, and refuses to start anywhere else. To move it, release the binding in your account and then start the engine on the new machine — the first start there claims the licence. Four transfers are allowed in any twelve months, and your account shows how many are left. Replacing hardware or re-creating a virtual instance can look like a different machine, so it spends a transfer.
What happens to us if Solo 76 stops being around?
Source-code escrow is available on request. Under it, the source of the engine and the materials needed to build it are deposited with an independent escrow agent and released to you on defined events — Solo 76 ceasing to operate, or ceasing to support the product — under a licence to maintain it for your own internal use. Because the engine checks its licence periodically, the deposit is written to include the means to keep running without that check, so that a release event does not stop your systems. It is a standard arrangement and we will enter into it on request.