Matters AI — Full Runtime Architecture Diagram

How to read

Left to right: actors, Vercel edge, apps, data plane, SaaS
Solid arrows are request-time reads and writes; dashed are async, webhook, or failover paths

Design choices

Root doubles as public app and monorepo root; workspace, partners, memo, webdocs deploy separately
Shared code graduates from root lib into packages auth, lib, ui, theme, config
proxy.ts runs on Node in every Next app; partners still uses middleware.ts
Cron telemetry sync and email fallback share the same SaaS corridor

Trust + limits

Clerk session plus email allowlist plus per-route RBAC; diagram shows verify on workspace, same pattern guards partners + memo owner
Root proxy blocks scraper UAs, honeypot paths, and unknown hosts before rendering
Mongo-backed rate limits and timing-safe webhook secrets guard every mutation
Dropped long edges live in cards: partners Salesforce writeback, memo Redis JWT keys, cron telemetry sync