A Quantitative Trading Research & Education Platform — Inspired by Nature
Running capital on behalf of others.
Multi-tenant workspaces with hard isolation. Every tenant's book is schema-separated at the database level — not filtered in application code, enforced by the engine. By invitation.
Why schema separation matters
Most multi-tenant systems keep everyone's data in the same tables and add a customer ID column, then filter on it in application code. That works right up until one query forgets its WHERE clause — and then one client sees another's book. myMTree gives each tenant its own database schema. The boundary is enforced by the database itself rather than by remembering to filter. It is the difference between a locked door and a sign asking people not to enter. Learning state is isolated the same way. Your outcomes tune your weights, and nobody else's results touch your model.
What the console gives you
Per-tenant provisioning
Provision, export and audit each book independently, with its own entitlements.
Cross-book reporting
NAV, allocation and drawdown across every book you run, without merging the books themselves.
Full decision provenance
Every staged order traceable back to the signal that caused it — which matters when someone asks why a position exists.
Role-scoped access
An operator control plane kept separate from the trading desk, so administration and execution aren't the same set of hands.
myMTree is a research and education platform. Nothing here is investment advice, and no past or projected performance is shown or implied. Options and futures involve substantial risk of loss and are not suitable for every investor. New accounts are simulated.