Sandbox any web app, however old, and compose it at build time or at runtime. Open source, zero runtime dependencies, enterprise edition announced.

Integrate in weeks.
Modernize without a rewrite.

Coordination between engineering teams — different timezones, separate sprints, conflicting priorities — is painful. Someone's always waiting on someone else. Hyperfrontend lets each team ship on their own schedule. No more "we're blocked on Platform."

Swipe to navigate

$npm install @hyperfrontend/features
TypeScriptMIT LicenseZero runtime deps
live demo
Connecting…cross-site
center to activate
Live democross-site
center to activate
Live democross-site
shipping soon

Chess

In planningcross-site
shipping soon

Events

In planningcross-origin, same site
shipping soon

File Share

In planningcross-site
shipping soon

Views

In planningcross-origin, same site

Connecting to the live demo on its own origin… All demos →

1:18 · with sound

How it works

Each feature operates in its own iframe with standardized communication via the @hyperfrontend/nexus library. Messages are routed through a broker-channel architecture with optional encryption.

How a feature runs inside a hostA host application window with a feature shell seated in its page. Inside the shell, a dashed boundary marks a separate browsing context, and inside that the feature application runs from its own origin. A message broker sits between the host's page and the shell, and contract messages cross it in both directions.Host applicationhttps://app.example.comfeature shellBrowsing contexthttps://checkout.team-b.devFeature applicationMessage broker