Bit Harmony

Bit's open-source micro-kernel extension engine for composable software — Aspects (full-stack, versioned components) composed via dependency injection and Slots into shell apps at build time.

Kevin pasted bit.dev/docs/harmony-intro as an "add it" capture alongside Remix. Harmony is the foundation layer under Bit and Bit Cloud's composable product model. Source: User, 2026-06-14

Core model

• Aspects — full-stack, independently versioned packaged-by-concern units (PBCs): UI + logic + config shipped as one composable unit, not a monolith repo slice.
• Harmony runtime — micro-kernel that wires Aspects together through dependency injection and Slots (extension points in a host "shell" app).
• Build-time composition — shell apps assemble from published Aspects rather than copying code; aligns with modular product lines and design-system-as-packages thinking.

Harmony is the engine; Bit Cloud is the distribution/registry layer on top. Source: bit.dev/blog/meet-harmony, npm @teambit/harmony, 2026-06-14

Wiki lens

• Composable products: connects to Services-as-Software — verbs and modular surfaces instead of one-off app copies.
• Frontier stack: listed in Frontier Stack 2026 related: as a composability primitive for teams building many product variants from shared Aspects.
• Design systems: Aspects pattern parallels tokenized Design System packages with runtime composition boundaries.

Research entry point: bit.dev/docs/harmony-intro, @teambit/harmony on npm.

---

Timeline

• 2026-06-14 | Full capture ingest from Kevin (bit.dev/docs/harmony-intro). Cross-linked Frontier Stack 2026, Services-as-Software. Source: User, 2026-06-14