Every product eventually grows sideways. A shop appears next to the landing page, then docs, then a status page, then something experimental you are not ready to name. The usual answer is a new repository per idea — and a year later, five half-maintained codebases that all render the same header slightly differently.
One core, many surfaces
We took the opposite bet: a single shared core that every app inherits. Design system, authentication, content pipeline — written once, compiled into every app at build time. Each app stays independently deployable, but none of them can drift.
- Shared components and theme tokens come from the core.
- Each app owns only what makes it different.
- A fix in the core reaches every app on its next build.
Independence is for deployment. Consistency is for people.
What it feels like
Spinning up a new app takes minutes, not days. It arrives already speaking our design language, already connected to content and auth, already routable under its own subdomain. The boring parts are inherited; only the interesting parts get written.
