soma

Your health stack, finally unified.
Garmin · Hevy · Strava — one self-hosted dashboard, your data, your server.

Live Demo →

Daily steps, resting heart rate, stress trend, body composition, recovery status, weekly training load, activity streaks — your full health picture on one page.

Pace progression across every run, monthly mileage history, VO2max trend, training zones, HR vs pace scatter, split analysis, shoe mileage tracking.

Muscle activation map (front & back) with volume by muscle group across all sessions. Exercise progression, personal records, gym frequency heatmap.

Sleep stages over time (deep, light, REM, awake), score trend, sleep schedule, HRV, blood oxygen, respiration rate, body battery, training readiness.

See exactly what synced, configure push rules (e.g. Hevy strength → Strava), and monitor the live data pipeline.

Garmin Connect ──┐
                 ├──▶  TS sync (Actions + Vercel crons)  ──▶  Neon PostgreSQL  ◀──  web/ (Next.js)  ──▶  Vercel
Hevy API ────────┘                                                                       │
                                                                                         ▼
                                                                                    Strava (push)

The stack is all TypeScript. The ingest/routing pipeline runs as GitHub Actions (.github/workflows/sync.yml → scripts/sync-pipeline.mts) plus Vercel cron functions, composing the same lib modules the web/ app reads. Shared logic is published as npm packages — macro-engine-core, banister, run-dj, garmin-auth — and the UI (web/ + the cross-platform universal/ Expo app) renders from the shared soma-style design system.

# Apply the schema migrations (in order)
for f in web/lib/db/migrations/*.sql; do psql "$DATABASE_URL" -f "$f"; done

Set Root Directory → web in Vercel, then add:

GitHub OAuth app setup: go to github.com/settings/developers → New OAuth App → set Authorization callback URL to https://your-app.vercel.app/api/auth/callback/github.

Then visit /connections to complete Strava OAuth.

cd web && npm install && npm run dev          # → http://localhost:3456
cd web && npx tsx scripts/sync-pipeline.mts    # manual sync run (TS pipeline)
cd universal && npm install && npm run web     # cross-platform Expo app (RN Web)

A floating chat bubble in the bottom-right of every soma page spawns a local claude -p subprocess per turn — no API key, no extra service. It reuses your Claude Code subscription auth from ~/.claude/.

Requirements:

• Claude Code CLI installed and authenticated (claude --version should print a version).
• soma running locally (npm run dev above). The widget makes a subprocess call, so it can't work on Vercel deployments — local-only by design.

On the first message the route bootstraps a new session, captures its UUID, and stores it at ~/.soma/chat.json so subsequent turns resume the same conversation. Click the pencil icon in the chat header to start a fresh thread.

The assistant is primed by web/lib/chat-system-prompt.md — role, project layout, DB schemas, conventions. Edit that file to change how it behaves.

You can have the deployed soma forward chat requests to your Mac's local Claude Code via a Cloudflare tunnel. Vercel becomes a thin proxy; the actual claude -p still runs on your machine against your subscription auth.

On the Mac (one-time setup):

brew install cloudflared
cloudflared tunnel login                                    # browser auth
cloudflared tunnel create soma-chat                         # creates UUID + creds
cloudflared tunnel route dns soma-chat chat.your-domain.com # your subdomain

~/.cloudflared/config.yml:

tunnel: soma-chat
credentials-file: /Users/<you>/.cloudflared/<UUID>.json
ingress:
  - hostname: chat.your-domain.com
    service: http://localhost:3456
  - service: http_status:404

Then run it (or launchctl it for autostart):

cloudflared tunnel run soma-chat

Add a shared secret to web/.env.local:

SOMA_CHAT_TOKEN=$(openssl rand -base64 32)

Keep npm run dev running on the Mac as usual.

On Vercel (Settings → Environment Variables):

Redeploy. The widget now shows a status dot in the header:

• 🟢 green — direct local subprocess (when you're on localhost:3456)
• 🔵 blue — proxied via Vercel → your Mac's tunnel (when you're on the deployed URL)
• 🔴 red — tunnel unreachable (Mac asleep, no internet, etc.)

Rotate SOMA_CHAT_TOKEN on both sides if it ever leaks. The shared secret is the only thing standing between your tunnel's public DNS name and your local filesystem.

Two plists under ~/Library/LaunchAgents/ (per-user, no sudo) keep everything alive across Mac sleep/wake/reboot:

Logs land in ~/Library/Logs/soma/. Manage with launchctl bootstrap gui/$UID <plist> to load and launchctl bootout gui/$UID dev.gkos.soma.web to temporarily stop for hands-on development.

If your domain's authoritative DNS lives somewhere other than Cloudflare, you can still use a Cloudflare Quick Tunnel — but its trycloudflare.com URL rotates on every cloudflared restart. To keep the deployed Vercel chat pointed at the live URL automatically, add a third agent that tails the tunnel log and syncs URL changes into Vercel env:

Prereq: the Vercel CLI must be logged in (vercel login) once on the Mac so the watcher's CLI calls work non-interactively.

This becomes unnecessary once you migrate your zone to Cloudflare DNS (the named-tunnel route in the previous section), since the URL is then stable.

MIT