Privacy-first Mood & Habit Tracker with Correlation Analysis Understand why some days are good and others are not — selfhosted today, offline-capable by design, 60 seconds per day.
People sense that sleep, exercise, remote work days, or social contacts influence their wellbeing — but rarely know which factors actually matter, how strongly, and with what time delay. Existing apps are either too simple (just mood emojis), too cloud-dependent (a privacy problem for health data), or too complex (targeting quantified-self enthusiasts).
CorrelCore fills this gap:
| Promise | Description |
|---|---|
| Correlations, not raw data | The app explains why days were good or bad |
| Selfhosted now, offline-ready next | Your health data stays on your instance; PWA shell caching is live; full Dexie offline sync is a follow-up |
| 60 seconds per day | No more, or it simply won't get done |
| No gamification, ever | You track your habits — not how often you open the app |
- M0 — Monorepo, CI/CD, Docker stack, native JWT auth, empty app shell
- M1 — Daily entry: mood, energy, stress, tags (curated + custom), symptoms (curated + custom), notes, app-level Fernet encryption at rest, login/register UI, email verification, GDPR erasure (offline sync moved to M4 — ADR-0009)
- M2 — Visualisations: mood time series (multi-metric), tag frequency heatmap with drilldown, entry streak widgets, CSV/JSON export (GDPR Art. 20), custom SVG charts, habit schema prep (ADR-0012), developer view (ADR-0015)
- M3 — Insights v1: correlation analysis, template-based statements, tiered confidence system, cold-start UX (retrospective onboarding, insight confidence scale, day-over-day delta, weekday pattern insight, onboarding profile questionnaire)
- M3.1 — Insights polish: non-blocking InsightStore, canonical InsightCard, full Insights feed, correlation disclaimer, and neutral heatmap styling
- M3.5 — Frontend web and mobile optimisation: app shell, entry bottom sheet, Home recomposition, Trends tabs, Settings/i18n, tag lifecycle. Release-complete after rendered QA on 2026-05-27. See
docs/M3_5_SPRINT_STATUS.mdanddocs/quality/M3_5_VISUAL_QA.md. - M3.6 — Insight maturity phases: ADR-0021 API contract (
insight_maturity), Journey Banner, Maturity Badge, phase-aware empty states, and phase milestone cards. Release-complete after rendered QA on 2026-05-27. Seedocs/M3_6_SPRINT_STATUS.mdanddocs/quality/M3_6_VISUAL_QA.md. - M3.7 — Color system hardening: complete semantic tokens, legacy primary alias cleanup, ADR-0027 contrast gate, light-mode QA documentation, and Web CI integration. Release-complete locally after rendered QA on 2026-05-28. See
docs/M3_7_SPRINT_STATUS.md. - M4 (partial) — Quick wins + PWA hardening: entry slots, cycle day, guided onboarding, Dev Mode mocks, install banner, service worker (app shell),
/offlinefallback. Follow-ups: Dexie offline sync, sync-conflict log, Web Push, app lock. Seedocs/M4_SPRINT_STATUS.mdanddocs/features/PWA.md. - M5 (Habits Core) — Goal-based habit adherence (
build/reduce),/api/v1/habits, Settings tag configuration, Trends Habits tab. Co-occurrence deferred to M5.1/backlog. Seedocs/M5_SPRINT_STATUS.md. - M7 — Insights v2: Lasso regression, lag analysis, symptom analytics, tag clustering, optional local LLM (Ollama). See
docs/M7_NOTES.mdanddocs/M7_M8_MILESTONE_SWAP.md. - M8 — Sleep & Health Connect: manual sleep fields, Android wearable import, sleep↔mood insights, cycle HC sync (with M11). See
docs/M8_NOTES.md. - M9 — Beta hardening: monitoring, GlitchTip, external testers, documentation
- M10 — Public selfhost release v1.0
- M11 — Android Play Store (Capacitor)
- M12 — SaaS mode (managed hosting)
- M13 — Photo & media: local upload to MinIO, EXIF strip, thumbnail gallery; optional Immich reference integration as follow-up
Full roadmap: docs/DESIGN_DOCUMENT.md
| Milestone | Status | Notes |
|---|---|---|
| M3 | Complete | Insights v1 is closed with backend analytics, worker generation, read APIs, Home preview, cold-start onboarding, and day-over-day delta. See docs/M3_SPRINT_STATUS.md. |
| M3.1 | Complete | Focused Insights polish after M3: InsightCard/InsightFeed, non-blocking store behaviour, disclaimer route/modal, and neutral correlation matrix styling. See docs/M3.1_SPRINT_STATUS.md. |
| M3.5 | Complete | Frontend/mobile optimisation release-complete after rendered QA (2026-05-27). See docs/M3_5_SPRINT_STATUS.md and docs/quality/M3_5_VISUAL_QA.md. |
| M3.6 | Complete | Insight maturity phases release-complete after rendered QA (2026-05-27). See docs/M3_6_SPRINT_STATUS.md and docs/quality/M3_6_VISUAL_QA.md. |
| M3.7 | Complete | Color system hardening release-complete locally after rendered light-mode QA (2026-05-28). See docs/M3_7_SPRINT_STATUS.md. |
| M4 | Partial | Quick wins + PWA hardening merged on main; Dexie sync, conflict log, push, and app lock remain follow-ups. See docs/M4_SPRINT_STATUS.md and docs/quality/M4_VISUAL_QA.md. |
| M5 | Partial | Habits Core merged on main; rendered QA and issue closeout still pending. Co-occurrence is M5.1/backlog. See docs/M5_SPRINT_STATUS.md. |
| Layer | Technology | Rationale |
|---|---|---|
| Backend API | FastAPI (Python 3.12) | Async, OpenAPI-native, fast iteration |
| Web Frontend | SvelteKit + Skeleton UI | Performance, bundle < 150 KB gz |
| Mobile | Responsive web + partial PWA (install banner, SW shell cache); Capacitor Android in M11 | Maximum code sharing, native Health Connect access later (ADR-0002) |
| Charts | Custom SVG components | No external framework, JS budget maintained, token-compliant |
| Database | PostgreSQL 16 + pgvector | Row-level security for multi-user, vector for insights |
| Cache / Queue | Redis 7 | Sessions, rate limiting, sync queue |
| Object Storage | MinIO | Selfhost-compatible S3 foundation; photo upload and EXIF strip are M13 scope |
| Reverse Proxy | Traefik v3 | Automatic TLS, Docker label routing |
| Auth | Native JWT phase 1, Authentik from M12 | OIDC, SSO, selfhostable (ADR-0004) |
| Offline Sync | Planned: Dexie.js (IndexedDB) | PWA shell cache live; delta sync and conflict log are follow-ups after M4 quick wins |
| Analytics | pandas + scikit-learn | M7: Lasso, lag, symptom analytics; correlation engine live since M3 |
| Migrations | Alembic | Schema versioning |
| Monitoring | GlitchTip + Uptime Kuma | Selfhosted error tracking |
| Notifications | UnifiedPush / FCM | Privacy-first push |
- Docker >= 24 + Docker Compose v2
- A domain with DNS pointing to your server
git clone https://github.com/Sturmi77/correlcore.git
cd correlcore
cp infra/docker/.env.example infra/docker/.env
# Edit .env: set DOMAIN, SECRET_KEY, POSTGRES_PASSWORD, ...
docker compose -f infra/docker/docker-compose.yml up -dAfter startup, CorrelCore is available at https://your-domain.tld
Note: CorrelCore is under active development (pre-alpha). Production use is recommended from v1.0 onwards.
correlcore/
├── apps/
│ ├── web/ # SvelteKit web app; partial PWA (service worker, install banner)
│ └── android/ # Capacitor Android app (from M11)
├── backend/
│ ├── app/ # FastAPI application
│ ├── migrations/ # Alembic migrations
│ └── workers/ # Analytics worker, insight engine
├── infra/
│ ├── docker/ # docker-compose.yml, .env.example
│ └── traefik/ # Traefik configuration
├── docs/
│ ├── DESIGN_DOCUMENT.md # Single source of truth
│ ├── ARCHITECTURE.md
│ ├── API.md
│ ├── FRONTEND.md
│ ├── MARKET_ANALYSIS.md
│ ├── quality/ # Quality gate reports (M1, M2, ...)
│ └── adr/ # Architecture decision records
└── .github/
└── ISSUE_TEMPLATE/
When working with AI models (Claude, Cursor, Copilot, Perplexity), always load DESIGN_DOCUMENT.md as context first:
Context: Read DESIGN_DOCUMENT.md in full first. Strictly follow the architecture,
tech stack and frontend principles defined there. If you want to deviate,
justify it and propose an ADR entry.
Task: <your specific task here>
| Document | Content |
|---|---|
| DESIGN_DOCUMENT.md | Vision, features, architecture, roadmap — single source of truth |
| ARCHITECTURE.md | Component diagram, deployment topologies, sync protocol |
| API.md | OpenAPI guidelines, endpoints, auth flow |
| API_CONTRACTS.md | API contract strategy, frontend constants, OpenAPI client plan |
| FRONTEND.md | Design principles, atomic design, i18n, performance budget |
| DEVELOPMENT.md | Local setup, quality gates, NAS/pnpm notes, test database |
| MARKET_ANALYSIS.md | Competitive and market analysis, monetisation, marketing |
| DOCUMENTATION_LANGUAGE_PLAN.md | English-first collaboration and documentation migration plan |
| RENAMING_TO_CORRELCORE.md | Rename and deployment migration notes from MoodSync to CorrelCore |
| M4 Sprint Status | M4 quick wins + PWA hardening tracking |
| M5 Sprint Status | M5 Habits Core tracking |
| M7 Notes | Insights v2: Lasso, lag, symptom analytics, clustering |
| M8 Notes | Sleep, Health Connect, cycle deep integration |
| M7/M8 swap | Milestone reorder rationale and consequence index (2026-05-29) |
| M5.1 Visual QA | Tag co-occurrence heatmap closeout (2026-05-29) |
| M13 Notes | Photo & media milestone scope (deferred post-M12) |
| PWA | Install banner, service worker, offline fallback |
| Cycle tracking | Neutral cycle_day domain scope |
| COLOR_SCHEME_CONCEPT | Token framework and contrast rationale (M3.7) |
| ADR Index | Architecture decision records (0001–0034) |
| Quality Gates | M1–M4 visual QA and quality gate reports |
CorrelCore is currently a solo project. Contribution guidelines will be published once v1.0 is released. Issues and discussions are welcome.
Interested in beta testing? Open an issue or sign up on the landing page (coming soon).
CorrelCore is released under the GNU Affero General Public License v3.0. For commercial selfhost licenses without AGPL copyleft, contact via issue.
CorrelCore is not a medical diagnostic tool. All correlations and insights shown are intended solely for personal reflection and do not replace medical or therapeutic advice.