Can I vibecode Pirsch?

Build a full-stack, production-ready web application that replicates the core functionality and value proposition of Pirsch. This should not be a generic tool, but a highly specific implementation tailored for its core audience.

### 1. App Specifics & Value Proposition
**Core Value:** Privacy-friendly, real-time analytics without cookies.
This is what makes the app specifically worth paying for. You must prioritize these features and ensure they are highly polished, accurate, performant, and reliable. The user experience must mirror the premium feel of Pirsch.

### 2. Specific Screens & Exact UX
- **Real-time Dashboard:** Active visitors, current pages.
- **Audience:** Referrers, devices, countries.
- **Events:** Custom tracked actions and conversions.
The UX should include dynamic micro-animations, loading skeletons, and interactive hover states to feel extremely responsive. Use modern design tokens (Tailwind or similar) to ensure aesthetic excellence.

### 3. Data Model & Schema (Specifics)
Implement the following database schema (using PostgreSQL or a suitable NoSQL alternative). Ensure strict typing (e.g., Prisma or Drizzle ORM):
- `pageviews` (id, session_id, url, referrer, browser, os, timestamp)
- `sessions` (id, visitor_hash, duration, bounce)
- `events` (id, session_id, event_name, metadata)
Include proper indexes on frequently queried fields and foreign keys for relational integrity.

### 4. Core User Journeys (Step-by-Step)
1. User installs lightweight tracking snippet.
2. Dashboard populates instantly as visitors arrive.
3. User analyzes traffic spikes from specific referrers.
Ensure each step is frictionless and handles edge cases (like empty states or network errors) gracefully.

### 5. Technical Specifics (APIs, Protocols, Algorithms)
- ClickHouse for fast analytical queries on massive event data.
- Go or Rust for high-throughput tracking API.
- WebSockets for real-time dashboard updates.
Ensure you implement proper rate limiting, caching (Redis), and background job processing (e.g., BullMQ, Celery) for any heavy computational or network-bound tasks. The architecture must support horizontal scaling for these workloads.

### 6. Implementation Requirements
- Tech Stack: Use modern frameworks (e.g., Next.js, React, Node.js, or similar) as appropriate.
- UI/UX: Implement a premium, responsive design with clear data visualization where necessary.
- Security & Auth: Implement robust user authentication and authorization (e.g., NextAuth, Supabase).
- Error Handling: Ensure graceful error states, especially for data fetching or scraping tasks.
- Monetization: Scaffold Stripe integrations for recurring subscriptions reflecting the real app's pricing tiers.