Everything we got wrong caching a multi-tenant SaaS on one domain

Short summary

A detailed post-mortem on caching a multi-tenant SaaS platform served from a single domain across four content surfaces: marketing, blog, tenant storefronts, and the logged-in app. The author explains two separate decisions—consolidating SEO authority on one domain and keeping the app in one repo—that happened to produce the same layout. The post covers routing regimes, cache bugs, header provenance, and purge timing lessons.

• •Four content surfaces with opposite caching needs served from one domain
• •Two unrelated decisions (SEO authority and repo simplicity) drove the single-domain layout
• •Covers routing, cache bugs, header management, and purge strategy trade-offs

Generated with AI, which can make mistakes.