Skip to content

Architecture Diagram Description

ComponentFunctionKey Controls
CloudflareWAF, CDN, DDoS protection, DNS, rate limitingTLS full-strict, DNSSEC, OWASP WAF rules
GCP Cloud Run (web)Next.js frontend, BFF API routes, SSR/SSE proxyBranch-based environments via Cloud Build, Doppler secrets, IAM-controlled deployments
SupabasePostgreSQL, Auth, Row-Level SecurityRLS by org_id, AES-256 at rest, PITR, env isolation
GCP Cloud Run (agents)FastAPI agent service, LangGraph executionDoppler secrets, branch-based environments via Cloud Build
Supabase AuthIdentity provider, MFA, SSO, OAuth, email/passwordJWT tokens with custom_access_token_hook, RLS policy enforcement
AnthropicClaude LLM (Cloud Run → Anthropic API)TLS in transit, DPA governs data use
DopplerSecrets managementRole-based access, audit trail, native sync to Cloud Run/Supabase
                    ┌─────────────────┐
                    │  Customer        │
                    │  Browser         │
                    └────────┬────────┘
                             │ HTTPS (TLS 1.2+)

                    ┌─────────────────┐
                    │  Cloudflare      │
                    │  WAF / CDN /     │
                    │  DDoS / DNS      │
                    └────────┬────────┘
                             │ HTTPS (TLS 1.2+)

                    ┌─────────────────┐
                    │  GCP Cloud Run   │
                    │  Next.js App     │
                    │  BFF API Routes  │
                    │  SSR / SSE Proxy │
                    └───┬─────────┬───┘
                        │         │
           HTTPS        │         │        HTTPS
        (TLS 1.2+)      │         │     (TLS 1.2+)
                        ▼         ▼
              ┌──────────┐   ┌──────────────┐
              │ Supabase  │   │  GCP Cloud   │
              │ PostgreSQL│   │  Run (agents)│
              │ Auth / RLS│   │  FastAPI /   │
              └──────────┘   │  LangGraph   │
                             └──────┬───────┘
                                    │ HTTPS (TLS 1.2+)

                             ┌──────────────┐
                             │  Anthropic    │
                             │  Claude API   │
                             └──────────────┘

    ┌───────────────────────────────────────────────┐
    │  Supporting Services                          │
    │                                               │
    │  Doppler ─────── Secrets sync to all services │
    │  Supabase Auth ─ Identity / Auth / OAuth       │
    │  CrowdStrike ─── Endpoint protection          │
    │  GCP Cloud Mon ─ Uptime / alerting / logging  │
    │  GitHub ──────── Source control / CI/CD       │
    │  1Password ───── Team credential management   │
    │  Backblaze ───── Object storage / backups     │
    └───────────────────────────────────────────────┘
SegmentProtocol
Browser → CloudflareTLS 1.2+ (Cloudflare managed)
Cloudflare → GCP Cloud RunTLS 1.2+ (Cloudflare Origin CA)
GCP Cloud Run → SupabaseTLS 1.2+
GCP Cloud Run (web) → GCP Cloud Run (agents)TLS 1.2+
GCP Cloud Run (agents) → AnthropicTLS 1.2+
GCP Cloud Run (agents) → SupabaseTLS 1.2+
SystemMethod
Supabase (PostgreSQL)AES-256 (Supabase managed)
Backblaze B2AES-256 server-side
Google WorkspaceAES-256 (Google managed)
1PasswordAES-256 + Secret Key (zero-knowledge)
DopplerAES-256 (Doppler managed)

All customer data is scoped by org_id (organization ID from Supabase Auth custom_access_token_hook). Row-Level Security with current_setting('app.current_org_id') enforces this at the database layer — isolation is enforced by data policy, not by separate infrastructure.

SystemWhat It Monitors
CrowdStrike FalconEndpoint threats, malware, suspicious processes
GCP Cloud MonitoringUptime checks, API health, alert policies, log anomalies, SSL expiry
DependabotDependency vulnerabilities
Google WorkspaceSuspicious sign-ins, admin changes, DLP
1Password WatchtowerCompromised credentials, weak passwords
  • No raw payment card data stored — Stripe handles all payment processing (PCI DSS compliant)
  • Customer data residency: United States
  • No customer data used for model training — governed by Anthropic DPA
  • All administrative access requires MFA; no SSH or direct server access exists
  • Infrastructure is fully serverless/managed — no OS-level patching required

  • Information Security Policy
  • Data Classification Policy
  • Backup and Recovery Policy
  • Incident Response Plan

Meridian Seven — Confidential