Muninn

A private space for reflection

Muninn brings everyday writing, memories, mood tracking and reflection together. The aim is to preserve more than the text of an entry: what happened, how it felt and which patterns become visible when returning to it later.

Journals contain dated entries with tags, categories, attachments and revision history. Timelines and local search help revisit earlier experiences; weekly reflections and structured wellbeing questionnaires provide another way to look back. Encrypted account exports support portability, including synchronized attachments.

Returning to earlier experiences

The timeline brings dated entries and mood records into a calendar. Selecting a day reveals its entries alongside the month view, so a date becomes a route back into the writing. The separate Memories view revisits entries from the same day in previous years.

Privacy as an architectural constraint

Journal content and attachments are encrypted in the browser before upload. Current entry formats also encrypt titles, tags and categories. WebCrypto supplies AES-256-GCM encryption, with fresh data keys for entry revisions and attachments.

Recovery is part of the privacy story. An authenticated, email-confirmed browser can recover account access, and the service can recover account keys. This is client-side encryption with server-assisted recovery, not end-to-end encryption against the service. Some structural and wellbeing metadata remains visible to the backend.

Search runs over an in-memory index of locally decrypted entries. Neither queries nor that decrypted index are sent to the backend, and the plaintext index is not persisted.

Offline editing and synchronization

IndexedDB holds encrypted drafts and cached history. Changes that cannot reach the API are queued as encrypted requests and retried when connectivity returns. Stable identifiers, idempotent mutations, version checks and incremental change feeds support synchronization.

Concurrent edits are surfaced as conflicts, preserving local work for deliberate reconciliation. Offline access depends on the content and keys already available in that browser.

Architecture and delivery

The backend is a NestJS modular monolith with explicit boundaries for journals, entries, identity, attachments, synchronization and wellbeing. Domain behavior and application use cases are separated from HTTP, persistence, storage and AI providers.

PostgreSQL and Drizzle handle records and encrypted payloads; Azure Blob Storage holds encrypted files. An OpenAPI contract produces TypeScript clients for the React application, which uses MUI, TanStack Router and TanStack Query.

An Nx and pnpm monorepo contains the API, web app, public website and shared branding. Applications retain independent versions and deployment artifacts. Docker and Azure DevOps support delivery, while separate infrastructure uses Kubernetes, Helm and Argo CD. Vitest, Supertest and Playwright cover testing boundaries; OpenTelemetry, structured logging and Seq support diagnostics.

Optional AI, explicit consent

AI workflows include summaries, tag suggestions and visual memories. Controls exist at deployment, journal and request level, with selected content reviewed before external processing. Production backend AI is disabled by default. Provider previews are distinguished from actual model output, and self-reported mood remains separate from inferred observations.

Current status

Muninn is in closed beta, focused on the React web application and backend. Native iOS and Android clients using SwiftUI and Jetpack Compose are planned; they are not part of the currently implemented client experience.