When should I use Shellui?

Use Shellui when you are starting a web app and do not want to rebuild the same infrastructure every time: navigation, authentication, administration, storage, themes, and i18n. It shines when development is split across teams working in a single app - each team owns its own surface while the shared shell keeps chrome and collaboration consistent. It is also a strong fit for greenfield products and for composing multiple apps in a microfrontend. If you already have a mature stack you are happy with, you probably do not need it.

Should I migrate my application to Shellui?

Usually not as a full rewrite. A working application is expensive to replace, and Shellui is not a drop-in for an existing design system or backend. A better path is to adapt your app so it can run both ways - on its own, and inside the Shellui shell - then adopt the shell where it helps. That is often easier for a new surface you are adding than for moving an entire production app overnight. Try the playground first if you are unsure.

Is Shellui production ready?

Shellui is used in real projects and is still evolving. APIs and behavior can change, so pin your versions and follow the changelog rather than treating it as a frozen long-term contract.

What if the project disappears?

Shellui is our in-house solution. It is bootstrapped, we run it ourselves, and we have no plan to stop using it. It is also MIT licensed, so you keep the source, you can fork it, and you are not locked into a hosted platform.

Introducing Shellui Read more

Shellui Build the App.
Not the Infrastructure.

Shellui is an open-source, opinionated microfrontend shell for building web applications. It provides the shared foundation developers need, so they can focus on their applications instead of rebuilding the same infrastructure over and over.

Get started View on GitHub

Features

Shellui ships the infrastructure every web app needs so you can focus on what makes yours unique.

Shellui

Microfrontend Shell

The runtime that stitches your apps together. Sidebar navigation, modals, drawers, themes, i18n, toasts, settings, cookie consent, and offline support — all configured from a single shellui.config.ts.

Explore microfrontend

Your Application

Sidebar layout Top bar layout Window layout

Sidebar, top bar, and window layouts

Identity

Authentication

Sign-in in the shell with identity-service or Supabase. Protect routes, choose public, domain allow-list, or invitation-only access, and issue tokens for users and services.

Explore authentication

Files

Storage

S3-compatible company bucket with private-by-default files, access grants, share links, and quotas. Apps talk to it through shellui.storage.

Explore storage

Admin

Administration

Staff and owners open an embedded admin for users, groups, login logs, and tokens. Inject your own apps into the sidebar from config.

Explore administration

See all features | View our roadmap

Frequently asked questions

Can’t find the answer you’re looking for? Reach out to our customer support team.

When should I use Shellui?: Use Shellui when you are starting a web app and do not want to rebuild the same infrastructure every time: navigation, authentication, administration, storage, themes, and i18n. It shines when development is split across teams working in a single app - each team owns its own surface while the shared shell keeps chrome and collaboration consistent. It is also a strong fit for greenfield products and for composing multiple apps in a microfrontend. If you already have a mature stack you are happy with, you probably do not need it.
Should I migrate my application to Shellui?: Usually not as a full rewrite. A working application is expensive to replace, and Shellui is not a drop-in for an existing design system or backend. A better path is to adapt your app so it can run both ways - on its own, and inside the Shellui shell - then adopt the shell where it helps. That is often easier for a new surface you are adding than for moving an entire production app overnight. Try the playground first if you are unsure.
Is Shellui production ready?: Shellui is used in real projects and is still evolving. APIs and behavior can change, so pin your versions and follow the changelog rather than treating it as a frozen long-term contract.
What if the project disappears?: Shellui is our in-house solution. It is bootstrapped, we run it ourselves, and we have no plan to stop using it. It is also MIT licensed, so you keep the source, you can fork it, and you are not locked into a hosted platform.

Ready to dive in?
Start using Shellui today.

Get started: Follow the documentation to scaffold a project and start building with the shared shell.
Try Shellui now: Explore a live Shellui app - navigation, auth, and the full shell - with no install and no scaffolding.

Shellui Build the App. Not the Infrastructure.