Getting started

This page walks you through running a 12-repo MTS1B stack locally — Docker Compose or Proxmox LXC.

⚠️ The v1 launch is in progress. Repos exist as skeletons; commands below are the target API. Track progress at github.com/MTS1B.

Prerequisites

Component	Minimum	Recommended
OS	macOS 12+ / Ubuntu 22.04+ / Windows 11 (WSL2)	Ubuntu 24.04 LTS
Python	3.11	3.12
Docker (Compose target)	24.0+	latest
Proxmox VE (LXC target)	8.0+	8.2+
RAM	8 GB	32 GB
Disk	20 GB	100 GB SSD

Install the deploy tool

pip install mts1b-deploy

Run the menuconfig installer

mts1b-deploy menuconfig

This launches a kernel-style TUI where you pick:

1. Target — docker-compose (default), proxmox-lxc, native, or kubernetes-helm (v2)
2. Profile — backtest-only (minimal), foundational-12 (full v1), paper-trading, live-trading
3. Asset classes — equities, crypto, options, fx, futures
4. Optional services — LLM router, AI bots, frontends
5. Vault setup — managed by deploy or external

Press s to save your config to mts1b.config.

Install

mts1b-deploy install --config mts1b.config

This will:

1. Pull or build the 12 foundational container images
2. Wire up Postgres, NATS, Redis, MinIO, Caddy, Authentik
3. Render service configs from your menuconfig choices
4. Launch each service and wait for /healthz green

For Proxmox LXC, this spawns 12 LXC containers (one per service) on your Proxmox host via the API.

Verify

mts1b-deploy status

Expected output:

✓ mts1b-foundation     loaded
✓ mts1b-platform       /healthz green
✓ mts1b-marketdata     /healthz green
✓ mts1b-quantkit       loaded
✓ mts1b-portfolio      /healthz green
✓ mts1b-riskengine     /healthz green
✓ mts1b-oms            /healthz green
✓ mts1b-GPUbacktester  /healthz green
✓ mts1b-brokers        /healthz green (paper)
12/12 services healthy

Run a smoke backtest

mts1b-deploy demo backtest-equities

Runs a 10-year SPY momentum backtest end-to-end through mts1b-GPUbacktester and dumps a result parquet you can inspect with any tool.

Next steps

• Read the architecture overview to understand the dependency graph.
• Check each repo's docs for API reference.
• Join the Discord to ask questions.