Layer I · Operations
The systems that run while you are away.
A strategy is the smallest part of a trading operation. Around it sit the jobs that fetch overnight, the monitors that watch positions and the alerts that wake you. Here they are written as code in your project and run under supervision on your own machine.
What it holds
The systems around the strategy: schedules, monitors and the jobs that run overnight.
01Processes that outlive the window
Long-running sessions are supervised, not tied to the interface. See what is running and on which ports, read back the logs, and stop anything that needs stopping. Close the app and it keeps going.
02Monitors and schedules, as code
The jobs around your strategy, scheduled fetches, health checks and alerts, are written into your project like everything else: readable, versioned, and changed by instruction rather than by configuration screens.
03Stacks that remember
A Stack packages a working setup, its tools, the instructions that tell the AI how to use them, and a starter project, so a way of working is installed in one action and returned to later instead of rebuilt from memory.
04Shared privately, without your keys
Send a Stack to a partner or a colleague and the work travels while the credentials stay behind. Nothing is published anywhere by default.
Monitors & alerts · Scheduled jobs · Stacks that remember · Private sharing
Due diligence
Questions asked first.
Does it need to run in the cloud?
No. QuantIDE runs on your own hardware. If you want something running around the clock, that is a machine you control, not a runtime we host.
What is inside a Stack?
Skills, the instructions that tell the AI how this workspace is meant to be used, plus the MCP servers it depends on and a starter project. All of it lands in your file tree.