System architecture
How the codebase is built — markets, code boundaries, data, UI and infrastructure
The macro-level choices behind the platform: how requests flow, where data lives, and how the monorepo is split.
Multi-market
Cüte runs several markets on shared code. Multi-market rails is the map of what a market owns — currency, payment provider, carriers, served countries — and why no runtime code may branch on a market's name. Payment account custody covers the line between what we store and what the provider stores.
Code organization
Commerce package is the transactional kernel: state machines, money, the rules that don't care about the UI. Enforcement layers shows how those rules are held in place at every level from the database up.
Data & performance
Caching strategy explains the "use cache" model. Seeding strategy covers the three seed buckets and which databases each may touch.
UI
Header architecture documents the global chrome and its Suspense boundaries. Z-index layers is the stacking ladder.
Routing & locales
Locale resolution — how the locale reaches every server component without being passed around, and the two places it has to be passed explicitly.
Infrastructure
Fly.io socket auto-stop — the WebSocket server's machine-suspension workaround.