Karybase storefront migration
Move the public storefront into its own app, without losing tenant-aware routing.
The standalone storefront already resolves wildcard subdomains and customer domains, rewrites into a shared route tree, and keeps organization identity attached to every request. This first pass upgrades the UI and font foundation so the app can start looking like the real storefront surface before we wire in auth and catalog data.
Domain resolver
Active
Subdomains and custom domains stay in storefront.
UI migration
Started
Fonts and landing surfaces are now being ported.
Next phase
Auth + data
Login and live catalog wiring can layer in next.
Tenant-aware middleware
Custom domains resolve first, subdomains second, and tenant headers flow to server components.
Domain provisioning hooks
The app includes Vercel SDK helpers plus route handlers for add, verify, inspect, and remove.
SEO-safe cutover path
Canonical redirects remain available once a tenant’s custom domain becomes primary, so UI migration does not disturb hostname ownership.
Fallback hostname
{slug}.store.karybase.com
Safe default for every organization while custom domains are pending or optional.
Customer-owned domain
customer.com
Verified domains can become canonical without changing the route tree you are migrating into.
Platform root
store.karybase.com
Reserved for the app shell and management entry points, not tenant storefront traffic.