Technology

Architecture Overview

Tech Stack

Infrastructure

Vercel Projects

Repository Structure

Integrated System (4 repos, tightly coupled)

These repos share a common Supabase backend and must be considered together:

~/code/sv-portal     # Customer-facing React app
~/code/sv-edge       # Supabase Edge Functions (Deno/TypeScript)
~/code/sv-db         # Database migrations (SQL)
~/code/sv-docs       # System documentation

Standalone Projects

These repos have NO Supabase integration, NO shared code with the portal.

sv-portal (Customer Portal)

Overview

• Tech: Vite + React + TypeScript + Tailwind CSS
• Auth: Supabase magic links (email-based, no passwords)
• State: React Query for server state
• Routing: React Router (4 routes only)

Routes (Non-Negotiable)

Key Components

src/
├── components/
│   ├── ItemCard.tsx        # Individual item display
│   ├── BookingsList.tsx    # Booking management
│   ├── AddItemModal.tsx    # Item creation
│   └── EditItemModal.tsx   # Item editing
├── pages/
│   ├── Login.tsx           # Auth page
│   ├── Dashboard.tsx       # Main inventory view
│   ├── Schedule.tsx        # Booking flow
│   └── Account.tsx         # User settings
└── lib/
    └── supabase.ts         # Supabase client

Commands

cd ~/code/sv-portal
npm run dev          # Start development server (localhost:5173)
npm run build        # Build for production
npm run typecheck    # TypeScript validation
vercel --prod        # Deploy to production

sv-edge (Edge Functions)

Overview

• Runtime: Deno (Supabase Edge Functions)
• Auth: JWT verification + RLS
• Deployment: supabase functions deploy

Functions

Deployment (CRITICAL)

cd ~/code/sv-edge

# Individual function
supabase functions deploy stripe-webhook --no-verify-jwt
supabase functions deploy calendly-webhook --no-verify-jwt

# Or use the deploy script (recommended)
./deploy-and-test.sh

Webhook URLs

Integrations

Stripe

Calendly

Supabase Storage

Security

Authentication

• Method: Magic links (email-based, no passwords)
• Provider: Supabase Auth
• Token: JWT with user ID
• Session: Managed by Supabase client

Row Level Security (RLS)

All customer tables are protected by RLS:

• Users can only see/modify their own data
• auth.uid() used in all policies
• Service role bypasses RLS (edge functions only)

Billing Protection

Billing fields on customer_profile are protected:

• Users CANNOT update subscription_status, stripe_customer_id, subscription_id
• Updates only via SECURITY DEFINER functions from webhooks

Secrets Management

Deployment

Portal (Vercel)

cd ~/code/sv-portal
npm run build        # Verify build passes
vercel --prod        # Deploy to production

Auto-deploys from GitHub main branch.

Edge Functions

cd ~/code/sv-edge
./deploy-and-test.sh
# OR manually:
supabase functions deploy <function-name> --no-verify-jwt

Database Migrations

cd ~/code/sv-db
supabase db push --linked

Requires: Docker Desktop running

Git Configuration

Use only real, verified email addresses. Fabricated emails cause Vercel permission failures.

Architecture Constraints (Non-Negotiable)

1. 4 routes only: /login, /dashboard, /schedule, /account
2. Supabase backend only — no custom API servers
3. Stripe Hosted flows only — no custom card UI
4. Single pricing tier: $299/month
5. Magic links only — no password auth
6. RLS on all tables — zero cross-tenant access
7. Private storage bucket — signed URLs, 1h expiry

Common Issues & Solutions