Federation module
Greenfield or rewrite. Built with Vite + Module Federation, imports
useAuth, authService directly from the host, routes inside the
host’s BrowserRouter.
Whisker Platform
One shell, one CLI, one component library — the toolchain for shipping Whisker Platform modules and services without coordinating through a single core team.
30+
Shared components
6
Platform packages
7
Architecture decisions
2
Integration paths
The platform, in one sentence
Section titled “The platform, in one sentence”Module teams own a
module-manifest.jsonfile, ship their code on their own cadence, and the platform’s runtime + pipeline glue them into a coherent shell without any coordinated release with the host.
Platform pieces
Section titled “Platform pieces”whisker-hostBuiltThe runtime shell — auth, navigation, dashboard, iframe sandbox — that composes every module. Always runs on port 3001.thundercats CLIBuilt · v0.1.0One binary your team learns, one CLI your agents discover. Scaffolds modules and services, keeps AI agent context in sync.whisker-module-kitBuiltDay-to-day dev CLI for front-end modules — dev orchestration, manifest generation and validation, doctor checks.whisker-service-kitBuilt · pilot pendingThe back-end equivalent of module-kit for BFF services owned by module teams.whisker-component-libraryBuilt & published30+ shared retail components, Nike theme, swappable analytics adapter, slide-out singleton, DevTools.whisker-manifest-publisherBuiltLambda that lets modules self-register by publishing a manifest to S3 — no host PR required.
Two ways in
Section titled “Two ways in”Iframe consumer
You already have a working app. Keep your own stack, talk to the host
over postMessage for auth tokens, own your own router.
Read the full comparison in Guide → Federation vs. iframe.