Skip to main content

The Jupyter-Native Workflow

ClyptQ is designed for the Jupyter notebook workflow that quant traders already use. Each notebook cell maps to a stage of the strategy lifecycle:
No compilation step. No deployment pipeline. No separate “production” environment. The same Python objects you create in Cell 2 are the same objects that trade live in Cell 6.

Cell-by-Cell Walkthrough

Cell 1: Discovery

Cell 2: Build the Strategy Graph

Cell 3: Configure and Run Backtest

Cell 4: Analyze Results

Cell 5: Iterate

Modify the graph, re-run the backtest, compare results. The graph object is mutable — add/remove nodes, change parameters, test different operator combinations:

Cell 6: Submit & Deploy

Once you’re satisfied with your backtest results, submit your strategy to the platform. Paper and live trading are not available in notebook cells — they are managed through the dashboard.
  1. Submit your strategy from the notebook or via the marketplace submission flow
  2. Open the dashboard to start Paper Trade or Live runs
  3. Monitor performance, manage risk parameters, and scale capital from the dashboard
The same StatefulGraph you developed in Jupyter runs identically on the dashboard. Code parity is preserved — the only difference is where execution is triggered.

Python Ecosystem Freedom

ClyptQ operators are pure Python. Use any library inside compute():
Common integrations:

ML/DL Integration Pattern

Train models externally, deploy inside operators:
This pattern works because:
  • Model training happens outside ClyptQ (any framework, any method)
  • Model inference happens inside a BaseOperator.compute() call
  • The operator is stateless — same inputs produce same outputs
  • The graph handles lookback, warmup, and data routing automatically
Research environment only: ML/DL strategies that load external model files (.bst, .pkl, .pt, .onnx) currently work only in the Jupyter research environment. The marketplace submission pipeline accepts strategy code (.py) only — model weight files cannot be uploaded alongside the strategy.Coming soon: A workspace file explorer will allow builders to upload model artifacts into a managed workspace. This will enable ML/DL strategies to be submitted to the marketplace and deployed to paper/live trading with their model files intact.

Quickstart

Full quickstart with complete code

Operator Protocol

How to write custom operators with BaseOperator

First Strategy Tutorial

Step-by-step SMA crossover with explanations

Backtest to Live

Full deployment lifecycle tutorial