single-spa
A framework for joining several JavaScript micro-frontends into one app, with different frameworks side by side.
Best for: Mixing frameworks in one page.
Visit single-spa →Tools and platforms for bringing separate user interfaces together: micro-frontend frameworks, web components, portals and digital experience platforms, UI composition and GraphQL layers, and low-code front ends.
A framework for joining several JavaScript micro-frontends into one app, with different frameworks side by side.
Best for: Mixing frameworks in one page.
Visit single-spa →A technique and tooling for loading code from separately built and deployed apps at runtime.
Best for: Sharing code between independent builds.
Visit Module Federation →A framework for building modular front ends from independently deployed plugin modules, called pilets.
Best for: Plugin-style portals.
Visit Piral →An open-source micro-frontend framework from SAP that composes apps in one shell with shared navigation.
Best for: Enterprise app shells.
Visit Luigi →A micro-frontend framework built on single-spa, with HTML entry loading and sandboxing.
Best for: Large web apps with many teams.
Visit qiankun →A registry and framework for sharing and rendering independently deployed front-end components.
Best for: Server-rendered components across teams.
Visit OpenComponents →A server-side micro-frontend library for composing pages from services owned by different teams.
Best for: Server-side composition.
Visit Podium →A monorepo build system with support for module federation and micro-frontend setups.
Best for: Managing many front-end projects.
Visit Nx →A web framework with an islands architecture that can combine components from several UI frameworks.
Best for: Content sites mixing frameworks.
Visit Astro →A small library for building fast web components that work across frameworks.
Best for: Framework-neutral components.
Visit Lit →A compiler that generates standards-based web components for design systems.
Best for: Cross-framework design systems.
Visit Stencil →A workshop for building, documenting and testing UI components in isolation.
Best for: Sharing a component library.
Visit Storybook →A platform for building, versioning and sharing independent components across projects.
Best for: Composable component platforms.
Visit Bit →An open-source JavaScript UI library from SAP for enterprise web apps.
Best for: SAP-style enterprise UIs.
Visit OpenUI5 →An open-source-based digital experience platform for portals, intranets and customer portals.
Best for: Portals and integrated customer experiences.
Visit Liferay →HCL's digital experience platform, formerly IBM WebSphere Portal, for enterprise portals.
Best for: Large enterprise portals.
Visit HCL Digital Experience →Adobe's content management and digital experience platform for building and delivering web experiences.
Best for: Marketing-led digital experiences.
Visit Adobe Experience Manager →A digital experience platform with content management, personalisation and commerce.
Best for: Composable digital experiences.
Visit Sitecore →SAP's service for building a single entry point to SAP and non-SAP apps, replacing the Fiori launchpad service.
Best for: Unified access to SAP apps.
Visit SAP Build Work Zone →Microsoft's platform for intranets, portals and document collaboration, extensible with web parts.
Best for: Microsoft 365 intranets.
Visit Microsoft SharePoint →An open-source framework for developer portals, with plugins that bring tools into one UI.
Best for: Developer portals.
Visit Backstage →A GraphQL platform with federation to combine many back-end services behind one API for front ends.
Best for: One data layer for many UIs.
Visit Apollo GraphQL →A tool for combining APIs and GraphQL services into one layer for front-end teams.
Best for: Federating APIs for front ends.
Visit WunderGraph →An engine that gives instant GraphQL and REST APIs over databases and services.
Best for: Quick API layers for UIs.
Visit Hasura →A platform for building internal tools and dashboards that connect to databases and APIs.
Best for: Internal tools on many data sources.
Visit Retool →An open-source platform for building internal apps and admin panels over databases and APIs.
Best for: Self-hosted internal apps.
Visit Appsmith →A low-code platform for building web and mobile apps that integrate with enterprise systems.
Best for: Enterprise web and mobile apps.
Visit OutSystems →A low-code platform for building enterprise apps with visual development and integration.
Best for: Governed low-code at scale.
Visit Mendix →Microsoft's low-code platform for building apps that connect to Microsoft 365 and hundreds of services.
Best for: Microsoft-centred apps.
Visit Microsoft Power Apps →Match your requirement to a starting point, then compare vendors.
| Many teams, one web app | Micro-frontends with single-spa, Module Federation or Piral |
|---|---|
| Shared look and feel | A web component library and design system |
| A single entry point for users | A portal or digital experience platform |
| One API for many screens | A GraphQL federation layer |
| Internal tools fast | A low-code or internal-tool platform |
| Mixed frameworks | Web components or an islands approach such as Astro |
Neighbouring directories and hubs.
Quick answers.
UI integration brings separate applications, services or components together into a unified user interface, so users work in one place instead of switching between many apps.
A micro-frontend splits a web app into smaller parts that independent teams build, test and deploy separately, then compose into one page or app in the browser or on the server.
Micro-frontends suit product teams building one large app. Portals and digital experience platforms suit bringing many existing apps and content into a single access point.
Yes. They are a browser standard for reusable elements that work across frameworks, so they are a common basis for shared design systems and mixed-framework pages.
Micro-frontends can add complexity, duplicate dependencies, slow page loads and inconsistent design. Agree on shared standards, a design system and performance budgets early.
UIs usually depend on APIs for data. A common pattern is a backend-for-frontend or GraphQL layer that combines several back-end services into the shape each UI needs.
Descriptions summarise each vendor's or project's own positioning, checked on 5 October 2026. Product names and offerings change often, so confirm details on the linked site before deciding.