Challenge
Multiple brands and internal tools needed independent deploy surfaces while sharing auth patterns, UI tokens, lead capture, and timeline publishing without a single brittle monolith deploy.
Monorepo platformInternal
A9 Web Ecosystem
Turborepo of brand sites, team tools, timeline publishing, and shared packages — the internal delivery surface behind every customer-facing property.
Approach
A Turborepo workspace-per-app layout ships myfamcrafts, dad-ac-landing, eric-hub, a9intel-web, and ace9-admin with shared packages and per-service Railway railpack configs.
- @a9/ui and @a9/brand for consistent navy/gold public and admin themes
- Shared lead-capture with rate limits, CSP, and optional Supabase + Resend adapters
- Timeline publish → export → journal revalidate hooks across services
Outcomes
Each property deploys on its own cadence while Eric-hub writing, myfamilycrafts journal, and Ace9 timeline stay synchronized through documented APIs and optional Supabase feeds.
Key highlights
- Workspace-per-app layout with shared @a9/ui, @a9/brand, and lead-capture packages
- Railway-first deployment with per-service railpack and volume-backed inquiries
- Cross-brand timeline feed with Supabase persistence and journal revalidation
- Talk A9 inquiry widgets wired to brand-specific submit adapters
More case studies