Infrastructurepattern

Per-user state via `user_email` column

Multi-user vibe-coded tools spawn per-tenant DBs and auth gymnastics. One user_email column on every table; works fine at sub-1000-user scale.

TierCCatalog — Pattern outlined, candidates for deeper work

EffortS · Days

Forany vibe-coder building a multi-user tool

What

Per-user CRM rows, per-user API keys, per-user sender identity, per-user swipe state — all via a user_email column on every relevant table. No per-tenant database carve-out, no auth gymnastics. Works at sub-1000-user scale.

← All casesC-052