Back of House Ecosystem

Back of House Ecosystem An architecture diagram generated by Archify. Restaurant Operators · public visitors · Architecture component Restaurant Operators public visitors Cloudflare · CDN · Workers · geo-block · Architecture component · Cloudflare Cloudflare CDN · Workers · geo-block Marketing Site · HubSpot CMS · backofhouse.io · Architecture component · HubSpot Marketing Site HubSpot CMS · backofhouse.io HubSpot CRM · contacts · deals · Architecture component · HubSpot HubSpot CRM contacts · deals Marketplace · Next.js · Vercel · Architecture component Marketplace Next.js · Vercel Supabase · PartnerBackend · Postgres · Architecture component · shared DB · Supabase Supabase PartnerBackend · Postgres shared DB Vendor Portal · Next.js · Vercel · Architecture component Vendor Portal Next.js · Vercel Vendors · partners & teams · Architecture component Vendors partners & teams PostHog · product analytics · Architecture component PostHog product analytics Resend · transactional email · Architecture component Resend transactional email Vendor CRMs · via Unified.to · Architecture component Vendor CRMs via Unified.to HTTPS browse & submit lead proxied forms → contacts leads · profiles new lead accept leads deal sync contact · deal sync edge fn emails API emails events Legend Frontend Backend Database Cloud External

Surfaces

  • • Marketing site: HubSpot CMS (220 modules) behind Cloudflare
  • • Marketplace and Portal: Next.js 15 + React 19 + Mantine on Vercel
  • • Algolia powers marketing-site search

Shared data

  • • One Supabase project (PartnerBackend) for vendors, leads, and profiles
  • • vendors_draft must mirror vendors: drafts publish on admin approval
  • • 14 edge functions send email through Resend

Integrations

  • • HubSpot CRM: contact and deal sync, form abandonment
  • • Unified.to: bidirectional deal status with vendor CRMs
  • • PostHog tracks all three apps (only the Marketplace edge is drawn)
← Directory