Security and isolation
A demo you can open without risk.
How the sandbox is kept away from real data and real servers.
Public internetReverse proxy with TLS
Marketing siteStatic files only
Lead gatewayOwn process and database
CRM sandboxSimulated MT5, database per visitor
No network route
Production CRM and MT5 ManagerDifferent machine. Never reachable from the demo host.
- Separate host and processesMarketing site, lead gateway and CRM sandbox run as separate processes with separate files. Nothing shares memory or database locks with a production system.
- Simulated MT5The sandbox cannot connect to a real MT5 server. It starts only when no production secrets are present, and refuses to start otherwise.
- A database per visitorEach session is a private copy of a fictional template. It is deleted after an hour of inactivity, and the template is rebuilt daily.
- No outbound messagesEmail and chat notifications are disabled, so the sandbox cannot be used to send spam.
- Abuse limitsPer-network session limits, a cap on concurrent sandboxes, upload limits and form protection against bots.
- Not in the order pathThe CRM reads and manages accounts through the Manager API. It does not sit between your traders and order execution.
See it with your own hands first.
Open the sandbox in one click. When you want to talk architecture or white-label, we are one message away.