MBBM Zero-Dependency Self-Hosted Integrated Platform

What it addresses

Running IM, music, e-books, and casual games on separate third-party clouds usually means handling account sync, credential uploads, cross-device state, and extra service dependencies. MBBM targets a narrower problem: run a local-first platform on self-managed hardware or a NAS while avoiding npm dependencies. It fits engineers who want local messaging, SMB/WebDAV music access, and e-book reading without relying on a hosted account service.

How it works and core capabilities

• Instant messaging: PIN identity, E2EE, direct and group chat (≤30), files/audio, and QR invite; APIs cover register, login, bootstrap, stream(SSE), send, contact, group, history, e2ee/pubkey, and avatar.
• Music library: connects to SMB/WebDAV, supports 14 formats, cover caching, and mobile playback; common endpoints include music/artists, music/albums, music/tracks, music/file(Range), and music/config.
• Casual games: Snake, Tetris, Pong, 1v1 matches, and leaderboards, running as relatively independent modules.
• E-books: online search, local multi-format import, full-screen reading, comics, e-ink support, and TTS; endpoints include search, cover, wikisource, gutenberg, books, book, epub, comic, and import.

The modules are described as relatively independent services: they can be deployed separately or aggregated through a main site shell. The deployment model can target QNAP/Synology, with each module in an independent container, persistent data volumes, and automatic exclusion of data/. Bluetooth Mesh relay uses a Mac as the BLE hub, where nearby devices join over BLE for store-and-forward and cluster delivery; /mesh/status can be used for verification.

Boundaries

All endpoints are local self-hosted endpoints, and the material states that it does not send credentialed requests outward. You still need to handle network reachability, permissions, backups, and access control. Group chat is capped at 30, Bluetooth Mesh requires an available BLE hub, and music depends on reachable SMB/WebDAV sources. If exposing it publicly, evaluate proxying, authentication, and TLS yourself; do not assume centralized account sync or hosted-cloud behavior is included.