Component Federation
Every large codebase has the same problem: the same patterns get reimplemented across dozens of applications because nobody knows they already exist elsewhere. Authentication hooks, API client wrappers, form components, data utilities — built and rebuilt, each version slightly different, each carrying its own bugs.
Component Federation solves this at the root. MeshOS automatically detects reusable components across your entire application portfolio, scores them for reusability, and manages their promotion to a shared library with full version control and dependency tracking.
Automatic detection
When you upload an application, MeshOS analyzes it for reusable building blocks:
- UI components — React, Vue, and Angular components with clear props interfaces
- Context providers — State management contexts and stores
- Custom hooks — Reusable logic that can move between applications
- Service classes — Business logic that shouldn't be duplicated
- Utility functions — Pure functions with no side effects
- Type definitions — Shared interfaces and types
- API clients — Typed integration layers for external services
Detection is automatic — you don't tag anything. MeshOS identifies the candidates and scores them.
Reusability scoring
Each detected component receives a reusability score from 0 to 100 based on five criteria:
| Criterion | Weight | What it measures | |-----------|--------|-----------------| | Clear API surface | 25% | Minimal, well-typed interface | | No tight coupling | 25% | Not wired to specific application context | | Test coverage | 20% | Unit tests present and passing | | Documentation | 15% | Props documented with usage examples | | Dependency footprint | 15% | Minimal external dependencies |
Components scoring 70 or above automatically appear in the Promotion Queue. Below 70, they're flagged as detection candidates with specific recommendations for what would need to change to make them promotable.
Component maturity lifecycle
Components move through a defined maturity path:
| State | Meaning | |-------|---------| | Detected | Found in an application, not yet evaluated | | Candidate | Score ≥ 70 — ready for promotion review | | Beta | Promoted to the registry — accepting feedback | | Stable | Approved for production use across teams | | Deprecated | Being phased out with a replacement available |
The Stage Zero library
Stage Zero is the highest tier — the canonical shared library for your organization. Components reach Stage Zero when they have been in stable state, are used across at least three applications, and have received explicit admin approval.
Stage Zero components are the source of truth. When a pattern exists in Stage Zero, teams import it rather than reimplementing it. This is how standards propagate across an organization without mandates — the better option is simply more convenient.
Dependency tracking
MeshOS tracks which applications use which version of which component. When a component in the registry is updated, all consumers are notified. Consumers can pin to a specific version or opt into automatic updates.
The dependency graph view shows the complete component-to-application relationship across your portfolio. Before deprecating a component, you know exactly which applications it would affect.
Promotion workflow
Promoting a component to the registry is a deliberate process, not an automatic one. A reviewer sees the component's reusability score breakdown, assigns a maturity level, assigns an owner, and approves the promotion. This creates accountability — someone owns the component, someone approved it, and there's a record of both.
See the application registry → See readiness scoring → MeshOS overview →