Murmur Platform Overview
Purpose
Section titled “Purpose”Orientation for anyone new to the Murmur codebase: which repo owns which concern, and how they talk to each other. Grounded in each repo’s own README/docs at the time of the Atlas audit (2026-09-20) — see
docs/engineering/design-source.mdfor the audit methodology.
Repositories
Section titled “Repositories”murmur-web
PRODUCTIONNext.js website/admin UI + murmur-api (Go): the API and MCP access layer that Tidepool, third parties, and agents call.
cbackstrom80/murmur-web
murmur-app
BETAMURMUR / codename PATCHWORK EIGHT — the C++20 DSP core and 8-engine algorithmic synthesizer. Standalone; does not embed the legacy Patchwork AI repo.
cbackstrom80/murmur-app
murmur-hub (Tidepool)
BETADesktop installer and license/library manager. Current v0 is a minimal beta-distribution tool, not yet the full catalog app.
cbackstrom80/murmur-hub
murmur-cast
BETALive Immersive Broadcast — captures a multitrack performance and delivers a spatialized, rendered mix. Split out of murmur-app once it outgrew being a subdirectory; still pins murmur-app's DSP primitives via git submodule.
cbackstrom80/murmur-cast
murmur-sdk
BETAThe shipping native SDK: C ABI, language kits, device profiles, client bindings. Talks to murmur-web's API/MCP layer rather than hosting its own.
cbackstrom80/murmur-sdk
Cloud service split
Section titled “Cloud service split”murmur-web’s docs/CLOUD.md is the source of truth for the live split: Go owns the public API, Python does AI/intelligence work, Rust is audio processing, and Next.js stays the website/admin UI, all behind nginx.
Internet -> nginx -> murmur-web (Next.js, :3001) website / admin HTML -> murmur-api (Go, :3002) /api/v1, /api/auth, cron, webhooks, billing -> GenerationJob / AudioJob (Neon) -> murmur-intelligence (Python) -> murmur-audio (Rust)A rendered version of this topology (D2 source:
diagrams/source/murmur-cloud-topology.d2) will render here once CI has
run npm run diagrams — see diagrams/generated/README.md.