Quantalyze

Portfolio intelligence platform for quant allocators. Connect exchange API keys, get a unified dashboard across all your strategies with TWR/MWR analytics, correlation matrix, risk decomposition, attribution, and a relationship/document layer. Asset managers publish exchange-verified strategies; allocators discover, compare, allocate, and track.

Prerequisites

• Node.js 20+ (pinned in .nvmrc; enforced by package.json engines)
• Python 3.12 (for the analytics service — pinned; matches the Dockerfile and CI)
• Supabase CLI and a Supabase project

Quick Start

# 1. Clone and install
git clone https://github.com/AI-Isaiah/Quantalyze.git
cd quantalyze
npm install

# 2. Set up environment
cp .env.example .env.local
# Edit .env.local with your Supabase project URL and anon key

# 3. Apply database migrations with the Supabase CLI
#   supabase link --project-ref <your-project-ref>
#   supabase db push
# (supabase/migrations/ holds 230+ timestamp-named migrations.) Set the
# admin email before the is_admin backfill migration runs, so it backfills
# automatically:
#   ALTER DATABASE postgres SET app.admin_email = '[email protected]';
#
# IMPORTANT: on this repo, merging a supabase/migrations/** file to main
# AUTO-APPLIES it to the PRODUCTION database. Read CONTRIBUTING.md
# ("Deploy semantics") before touching migrations.

# 4. Start the dev server
npm run dev

Open http://localhost:3000. You'll be redirected to the login page.

Project Structure

quantalyze/
  src/
    app/              # Next.js App Router pages
      (auth)/         # Login, signup, onboarding
      (dashboard)/    # Authenticated pages (discovery, strategies, portfolios, allocations, profile, preferences)
        admin/match/  # Founder-only Match Queue (triage + detail + eval dashboard)
        portfolios/   # Portfolio dashboard, management, documents
      (marketing)/    # Public marketing shell (shared layout): landing, legal/*, for-quants, security — route group, URLs unchanged
      api/            # API routes
        cron/         # Vercel Cron handlers (warm-analytics, sync-funding, reconcile-strategies, cleanup-wizard-drafts, cleanup-ack-tokens, founder-lp-report)
        # plus: verify-strategy, portfolio-*, alert-digest, admin/match/*, preferences, factsheet/[id]/pdf
    components/       # React components (ui/, layout/, charts/, strategy/, portfolio/, admin/, preferences/, landing/, auth/)
    hooks/            # Reusable React hooks (useKeyboardShortcuts, useBreakpoint SSR-safe viewport class, useMediaQuery, useTapPin touch tap-to-pin chart reveal)
    lib/              # Utilities, types, Supabase clients, queries, preferences, personas, portfolio-insights
  analytics-service/  # FastAPI backend (Python) — strategy + portfolio + match analytics
    services/         # metrics, portfolio_metrics, portfolio_risk, portfolio_optimizer, match_engine, match_eval
    routers/          # analytics, cron, exchange, portfolio, match
    scripts/          # operational one-offs + read-only ground-truth harnesses (deribit_ground_truth, bybit_reconcile)
    docs/             # tracked evidence docs (deribit-ground-truth.md answers template + evidence/)
  supabase/           # Database migrations (timestamp-named; auto-applied to prod on merge — see CONTRIBUTING.md)
  e2e/                # Playwright specs (auth, discovery, match-queue, ...)
  .github/workflows/  # CI + watchers/probes (main-CI-cancelled watcher, shared-test-db mutex drill)
  docs/
    architecture/     # ADRs (RLS authz, observability, error handling, secret handling, ...)
    runbooks/         # Operational runbooks (match-engine.md, bridge-outcome-cron.md, ...)
    superpowers/plans/ # Design + implementation plans from /autoplan
    pitch/            # Cap-intro partner pitch artifacts (qualification script, term sheet, one-pager)
    demos/            # Demo scripts + before/after metric capture for the partner demo

Version and changelog live in VERSION (4-digit MAJOR.MINOR.PATCH.MICRO) and CHANGELOG.md — /ship bumps both. The current release is tracked in VERSION.

Deploys

Merging to main deploys to production automatically: Vercel (frontend) on every push, Railway (analytics) on green CI, and Supabase migrations under supabase/migrations/** apply to the prod database on merge. Read CONTRIBUTING.md for the full deploy semantics and the operational gotchas (test-DB lag, Railway skip-on-red-or-cancelled-CI, version-bump rules) before merging.

Tech Stack

Layer	Technology
Frontend	Next.js 16, TypeScript, Tailwind CSS 4
Charts	Lightweight Charts, Recharts, @nivo/boxplot
Database	Supabase (PostgreSQL + Auth + RLS + Storage)
Analytics	FastAPI + quantstats + numpy + pandas + scipy + CCXT
Email	Resend
PDF	Puppeteer
Observability	Sentry (frontend + analytics service), structlog, end-to-end correlation_id
Deploy	Vercel (frontend), Railway (analytics)

This is the beginning of the README. Read the rest at the original. Read the full README ↗