One session for every micro-frontend.
A shell plus feature apps on separate origins, each shipping its own login. Handled Cloud gives the whole estate one session at the edge: add a new app by adding a route.
Sign up (opens in new tab)Your micro-frontends ship their own login.
A micro-frontend estate is a shell plus feature apps on separate origins: products, accounts, and checkout.
A new feature app is a new route.
Each app ships its own browser identity stack, and browser session management is a specialist job: the home page explains why.
- A session on one app does not follow the user to the next
- A new micro-frontend repeats the whole identity stack before it can ship
- Cookie and token handling differ per app, so security review is per app too
One session for the whole estate.
Handled Cloud runs a single session at the edge, across every micro-frontend in your configuration. A user logs in once, against the identity provider you already run, and every app in the estate recognizes that session.
Each origin receives a standard JWT. A new feature app is a new route, not a new identity stack, and your application code never touches a cookie or an OAuth flow.
How the session stays secure is on the security page; where the deployment runs in your estate is on the architecture page.
Ready to run one session across your micro-frontends?