Quantum Engine
IBM Runtime workloads (your account), portfolio async jobs, and integrations
Engine Telemetry
Current execution mode, available backends, API health, and active job count. Shows whether you're running on real quantum hardware or the local simulator.
Enterprise
—
Mode
Simulator
Backends
0
API Status
…
Portfolio jobs active
0
IBM workloads listed
—
IBM Quantum
Get a token from quantum.ibm.com. Optional instance CRN (from IBM Instances) is sent as instance and stored in integration metadata. Sent to POST /api/config/ibm-quantum for the selected enterprise, persisted server-side (not in the Next.js bundle).
Verify checks IBM Runtime (backends + instances) for the selected enterprise without saving the token. Add a CRN if IBM requires a specific instance. Connect saves token (and optional CRN) for this server’s DB and tenant.
Integration coverage
Status for the active enterprise (—). Braket follows the same tenant metadata pattern; AWS credentials typically stay in server environment / IAM.
IBM Quantum
Not configured
No backends listed
AWS Braket
Not enabled
Set BRAKET_ENABLED=true and BRAKET_* on the API server for annealing jobs.
IBM Runtime workloads
Recent jobs from your IBM Quantum account (same view as quantum.ibm.com "My Recent Workloads"). Requires GET /api/config/ibm-quantum/workloads with API key.
Connect IBM Quantum to list Runtime jobs for your API token.
IBM Runtime smoke test
Loads annualized returns and covariance (same pipeline as portfolio optimize), then runs one EfficientSU2 sample on IBM Runtime (fixed parameters — same ansatz family as VQE on hardware). Reports weights from counts and a single-eval Sharpe-style ratio. Choose a preset below (or custom tickers). POST /api/config/ibm-quantum/smoke-test
▸Custom tickers (optional override)
Comma-separated symbols. Leave empty for Mag 7 + JPM (same as the first preset).
Connect IBM Quantum above to run a Runtime smoke test.
IBM VQE — tickers & prices
Queues the same async optimize job as below, but forces objective: "vqe". The API loads returns and covariance from your Ledger tickers; when an IBM token is stored and the universe is small enough, the optimizer may run on IBM hardware (otherwise it falls back to classical simulation).
- IBM token: not connected — connect above to enable hardware
- Universe size: 10 / 20 (recommended max for hardware)
Portfolio jobs
Uses the current Ledger session (same objective, tickers, and weight bounds as the banner above — set them in Portfolio Lab or Strategy Builder). Async runs call Flask /api/jobs/* (server-side queue, not the IBM Runtime list). With IBM connected, objective vqe can use hardware via the API optimizer path.
- Session: hybrid · 10 tickers · weights 0.005–0.20
- Backtest window (default): 2024-08-13 → 2026-08-13 (monthly rebalance)
No jobs submitted yet. Jobs use your Ledger session (shown above).