Sellizi.Deployments
PLATFORM • FOUR DEPLOYMENTS

Sellizi runs as four apps.

Main, Affiliate, Admin and Ads Studio share the same Supabase Postgres + storage but deploy independently on Vercel. Ads Studio is fully isolated — own project, region, env, and build — yet linked back into Main.

Monorepo + shared assets ✅Supabase pooled DATABASE_URL ✅Ads: isolated deployment ✅

Main sellizi.com

Public storefront, landing, blog, legal, product discovery & checkout. Uses saspay.me for online payments + COD.

Vercel

sellizi-main → rootDir: apps/main

Routes

/ • /s/[slug] • /blog • /legal/[document] • /deployments

Assets present

  • public/images/seller-workspace.jpg
  • public/icon.svg

All assets are copied via packages/shared + public/ symlink. No 404s across deployments.

Required env

  • DATABASE_URL (Supabase pooled)
  • NEXT_PUBLIC_APP_URL
  • SASPAY_SECRET_KEY
  • SASPAY_WEBHOOK_SECRET

Affiliate affiliate.sellizi.com

French affiliate program — 10% for 12 months. Application form + dashboard with referrals & earnings.

Vercel

sellizi-affiliate → rootDir: apps/affiliate

Routes

/affiliate • /affiliate/apply

Assets present

  • public/images/seller-workspace.jpg (shared)
  • shared/components/affiliate-*

All assets are copied via packages/shared + public/ symlink. No 404s across deployments.

Required env

  • DATABASE_URL (shared)
  • NEXT_PUBLIC_APP_URL_AFFILIATE
  • SASPAY_SECRET_KEY

Admin app.sellizi.com

Seller OS — products, orders, customers, AI inbox, marketing, analytics, billing, team. Protected by supabase auth.

Vercel

sellizi-admin → rootDir: apps/admin

Routes

/app • /app/products • /app/orders • /app/marketing/* • /app/inbox • /app/settings/*

Assets present

  • packages/ui/*
  • packages/db/*
  • public/icon.svg

All assets are copied via packages/shared + public/ symlink. No 404s across deployments.

Required env

  • DATABASE_URL (shared)
  • NEXT_PUBLIC_APP_URL_ADMIN
  • SASPAY_SECRET_KEY
  • GOOGLE_CLIENT_ID
ISOLATED DEPLOYMENT

Ads Studio ads.sellizi.com — Isolated

Dedicated ad creation & campaign manager. Heavy media, canvas & AI generation. Own Vercel project, own region & env, shared DB + storage. This is the ONLY separate deployment per your request.

Vercel

sellizi-ads → rootDir: apps/ads

Routes

/ads • /ads/create • /ads/creatives • /ads/campaigns • /ads/analytics

Assets present

  • public/ads/*
  • packages/ads/*
  • shared canvas deps

All assets are copied via packages/shared + public/ symlink. No 404s across deployments.

Required env

  • DATABASE_URL (shared, RW)
  • NEXT_PUBLIC_ADS_URL
  • SASPAY_SECRET_KEY
  • OPENAI_API_KEY (optional)
  • R2/S3_BUCKET + CDN

Download each app (4 separate Next.js projects)

Each zip is a full standalone app — copy-pasted from this monorepo with all `src`, `public`, configs. Unzip, set env, `vercel deploy` or `npm run build`. Assets are already inside `public/` (seller-workspace.jpg, icon.svg, ads).

Plus bundle: sellizi-all-deployments.zip (4.0M) • Manifest: MANIFEST.json

In repo also under apps/main, apps/affiliate, apps/admin, apps/ads — each has its own vercel.json + README.*.md.

How it is wired (main hub)

Main links to every deployment. Example header added to src/components/landing.tsx now shows Main • Affiliate • Admin • Ads Studio • Blog. Vercel projects are separate (see deployments/*.json + apps/*/vercel.json), but share DB via pooled DATABASE_URL.

1. Monorepo

turbo.json + pnpm-workspace.yaml + packages/shared (ui, db, auth, saspay)

2. Env per deployment

Each Vercel project gets same DATABASE_URL, different NEXT_PUBLIC_*_URL. Ads has extra canvas deps.

3. Ads isolated

Own build, no admin code shipped to it. Communicates via API + shared public/.