Open-source micro-frontend framework that composes independently built front-ends without shared framework or rewrite
- for
- Frontend teams needing isolated, incremental integration of legacy or separate apps
- pricing
- open source
- license
- MIT
- lib-features@0.11.0lib-features v0.11.02 days ago
- lib-versioning@0.9.0lib-versioning v0.9.015 days ago
- lib-ui-utils@0.0.9lib-ui-utils v0.0.915 days ago
Key features
- Zero runtime dependencies — Runs without adding any runtime libraries to the host app
- Strong isolation via iframes — Each feature lives in its own iframe for crash-resilience
- Secure typed communication — Typed messages routed through a broker with optional encryption
- Incremental adoption — Add or replace features one at a time without a full rewrite
- TypeScript first — Full TypeScript support and MIT-licensed SDK packages
- Framework agnostic — Works with any stack – demos show Vue 3 features in a React host
Use cases
- Compose independently shipped apps on a single page without merging codebases
- Embed a feature built by another team without learning their stack
- Enable cross-window (iframe) communication with typed, encrypted messages
- Modernize a large legacy system incrementally, avoiding a full rewrite
Hyperfrontend FAQ
How do I add a micro-frontend to my app?+
Install @hyperfrontend/features via npm, load the feature shell in an iframe, and let the host manage its lifecycle.
Do I need to change my build process?+
No build-time dependencies are required; features are loaded dynamically at runtime.
Is communication between host and features secure?+
Yes, messages are typed and can be encrypted through the @hyperfrontend/nexus broker.
Can I adopt Hyperfrontend gradually?+
Yes, you can incrementally replace parts of your UI with micro-frontends without a full rewrite.
Summarized by DevHunt from hyperfrontend.dev · Sep 27, 2026. Details may change; check the official site.