Architecture Overview
ChimeraMiND is a single production backend plus five client surfaces, not a collection of ad-hoc scripts. This page maps the tiers an engineer or auditor would need to understand the system without a walkthrough from the founder.
Infrastructure tiers
| Tier | Role | Owner |
|---|---|---|
| Backend | FastAPI, 500+ route handlers across 57 route files, single VPS | Self-hosted, Cloudflare-fronted |
| Data | Supabase (PostgreSQL + Auth + RLS) | Supabase managed |
| Cache / pub-sub | Redis | Self-hosted on the same VPS tier |
| Edge | Cloudflare (DNS, Pages, Workers, Turnstile) | Cloudflare |
| Payments | Whop (canonical checkout, since 2026-04) | Whop |
| Error tracking | Sentry | Sentry |
| Exchange execution | 7 gateways (Binance, OKX, Bybit, Bitget, Coinbase, Kraken, Paper) via a non-custodial vault pattern | Per-exchange, credential-isolated |
Client surfaces
- Desktop — Svelte 5 + SvelteKit + Tauri 2. Owns the exchange-credential vault; the backend never receives plaintext exchange keys.
- Web — React 19 + Vite, this marketing/account/billing surface (chimeramind.com).
- Admin — React 19 + shadcn/ui, internal operations console.
- Mobile — Expo 54 + React Native.
- This docs site — Docusaurus, static, deployed independently of the product surfaces above.
Runtime shape
- Live product state (positions, signals, portfolio, bot status) flows over Socket.IO. No REST polling on the client for live data.
- The backend runs long-lived in-process daemons for decision recording, alert evaluation, and model heartbeats (RL, NAS, ghost-protocol, swarm) — these are supervised processes, not one-off cron scripts, so a restart resumes state rather than losing it.
- Strategy decisions are produced by an ensemble (16 strategy modules coordinated through
strategy_muxanddecision_engine), not a single model — see Service Catalog for the full inventory.
Multi-tenant model
Each user's trading state (positions, calibration, portfolio) is isolated by Redis key namespace and Supabase Row-Level Security. The platform also runs a _system paper account, isolated from real tenant data, used for internal measurement and model validation.
Why this matters for continuity
None of the above depends on tribal knowledge. Every tier in this table is a named, documented, independently operable service — see Engineering Practice for how that documentation is enforced, and Decision Log for why each major architectural choice was made.