Why this matters

Right now, the fastest path is the Docker setup wizard + self-hosting docs — which is great, but it’s still “infra first”. For a lot of Next.js teams, the fastest win is: deploy the monitor app on Vercel in minutes, then plug in an external ClickHouse (self-hosted or ClickHouse Cloud).

Less “where do I run this?”, more “I’m already seeing data.”

Proposed solution

1. Add a Vercel deployment guide (e.g. DEPLOYMENT_VERCEL.md or a section in DEPLOYMENT.md)

   • Target: deploying the monitor app to Vercel (monorepo-friendly)
   • Storage: connect to external ClickHouse (self-hosted / ClickHouse Cloud)
   • Auth/secrets: document required env vars + secure defaults

2. Add a “Deploy to Vercel” button in the README

   • Preselect the correct root directory (monitor app)
   • Pre-fill required env var names (values added by the user)
   • Include a short note: “ClickHouse must be external (not on Vercel)”

Acceptance criteria

• A new contributor can go from “open repo” → “live dashboard” on Vercel in <15 minutes
• Docs include:
  • Vercel project settings for a pnpm monorepo
  • Exact env var list + where to get each value (from setup/docker/env example)
  • A small troubleshooting section (build errors, missing env vars, ClickHouse connectivity)

Suggested checklist (implementation)

• Identify the monitor app directory used for the hosted demo (next-cwv-monitor-monitor-app.vercel.app) and document it as the Vercel root :contentReference[oaicite:2]{index=2}
• Add vercel.json (optional) to make monorepo deploy smoother
• Add README section: “Deploy on Vercel”
• Add Vercel button + clone URL
• Add a minimal “Works with ClickHouse Cloud” note (optional but super helpful)

Bonus (nice-to-have)

A tiny diagram: Vercel (Monitor App) ↔ ClickHouse (External) — so it’s instantly clear what runs where.

Thanks! This would massively reduce “setup friction” and make the project feel instantly usable for the average Next.js team.