costhawk 1.0.0

package/costcanary/.claude/settings.local.json

@@ -0,0 +1,9 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(git checkout:*)"
+    ],
+    "deny": [],
+    "ask": []
+  }
+}

package/costcanary/.env.production.template

@@ -0,0 +1,38 @@
+# PRODUCTION ENVIRONMENT VARIABLES
+# Copy to Railway environment variables dashboard
+
+# Clerk Authentication (PRODUCTION KEYS REQUIRED)
+NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_live_YOUR_LIVE_PUBLISHABLE_KEY
+CLERK_SECRET_KEY=sk_live_YOUR_LIVE_SECRET_KEY
+
+# Clerk URLs
+NEXT_PUBLIC_CLERK_SIGN_IN_URL=/sign-in
+NEXT_PUBLIC_CLERK_SIGN_UP_URL=/sign-up
+NEXT_PUBLIC_CLERK_AFTER_SIGN_IN_URL=/dashboard
+NEXT_PUBLIC_CLERK_AFTER_SIGN_UP_URL=/dashboard
+
+# Databases (Railway auto-injected - BOTH URLs REQUIRED)
+# Internal URL (fast but may have DNS timing issues during startup)
+DATABASE_URL=${{Postgres.DATABASE_URL}}
+# Public URL (reliable fallback for health checks and startup)
+DATABASE_PUBLIC_URL=${{Postgres.DATABASE_PUBLIC_URL}}
+REDIS_URL=${{Redis.REDIS_URL}}
+REDIS_PUBLIC_URL=${{Redis.REDIS_PUBLIC_URL}}
+
+# Security (CRITICAL - use production key)
+ENCRYPTION_KEY=GENERATE_NEW_32_BYTE_HEX_KEY_FOR_PRODUCTION
+
+# Application
+NEXT_PUBLIC_APP_URL=https://your-app.railway.app
+NODE_ENV=production
+
+# Stripe (PRODUCTION KEYS)
+STRIPE_SECRET_KEY=sk_live_YOUR_LIVE_STRIPE_SECRET_KEY
+NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_live_YOUR_LIVE_STRIPE_PUBLISHABLE_KEY
+STRIPE_WEBHOOK_SECRET=whsec_YOUR_LIVE_WEBHOOK_SECRET
+STRIPE_PRO_PRICE_ID=price_YOUR_LIVE_PRO_PRICE_ID
+STRIPE_TEAM_PRICE_ID=price_YOUR_LIVE_TEAM_PRICE_ID
+
+# Email (Resend)
+RESEND_API_KEY=re_YOUR_RESEND_API_KEY
+EMAIL_FROM=noreply@costcanary.com

package/costcanary/.eslintrc.json

@@ -0,0 +1,22 @@
+{
+  "extends": [
+    "next/core-web-vitals",
+    "prettier"
+  ],
+  "parser": "@typescript-eslint/parser",
+  "plugins": ["@typescript-eslint"],
+  "root": true,
+  "rules": {
+    "@typescript-eslint/no-unused-vars": ["error", { "argsIgnorePattern": "^_" }],
+    "@typescript-eslint/no-explicit-any": "error",
+    "@typescript-eslint/explicit-function-return-type": "off",
+    "@typescript-eslint/explicit-module-boundary-types": "off",
+    "@typescript-eslint/no-non-null-assertion": "error",
+    "no-console": ["warn", { "allow": ["warn", "error"] }],
+    "prefer-const": "error",
+    "react/prop-types": "off",
+    "react/react-in-jsx-scope": "off",
+    "react-hooks/rules-of-hooks": "error",
+    "react-hooks/exhaustive-deps": "warn"
+  }
+}

package/costcanary/.nvmrc

@@ -0,0 +1 @@
+20

package/costcanary/.prettierignore

@@ -0,0 +1,11 @@
+node_modules
+.next
+out
+build
+dist
+.vercel
+*.min.js
+*.min.css
+coverage
+.nyc_output
+prisma/migrations

package/costcanary/.prettierrc.json

@@ -0,0 +1,12 @@
+{
+  "semi": false,
+  "trailingComma": "es5",
+  "singleQuote": false,
+  "tabWidth": 2,
+  "useTabs": false,
+  "printWidth": 100,
+  "bracketSpacing": true,
+  "arrowParens": "always",
+  "endOfLine": "lf",
+  "plugins": ["prettier-plugin-tailwindcss"]
+}

package/costcanary/ADMIN_SETUP.md

@@ -0,0 +1,68 @@
+# Admin Setup Guide
+
+## Quick Start (For Testing Pricing Discovery)
+
+### 1. Create Admin Organization in Clerk
+
+1. Go to your Clerk Dashboard
+2. Click **Organizations** in the sidebar
+3. Click **Create Organization**
+4. Name: "Cost Canary Admins"
+5. Copy the **Organization ID**
+
+### 2. Add Yourself as Admin
+
+1. In the organization you just created
+2. Click **Members** 
+3. Click **Invite Member**
+4. Enter your email and set role to **admin**
+
+### 3. Set Environment Variable in Railway
+
+Add this to your Railway environment variables:
+```
+CLERK_ADMIN_ORGANIZATION_ID=org_xxxxxxxxxxxxxx
+```
+(Replace with your actual organization ID from step 1)
+
+### 4. Test Admin Access
+
+Once deployed, test your admin access:
+
+```bash
+# Check if you're an admin
+curl https://your-app.railway.app/api/admin/trigger-pricing
+
+# Trigger test pricing discovery
+curl -X POST https://your-app.railway.app/api/admin/trigger-pricing \
+  -H "Content-Type: application/json" \
+  -d '{"testMode": true, "provider": "OpenAI"}'
+```
+
+### 5. View Results
+
+Check the job results:
+```bash
+curl https://your-app.railway.app/api/admin/pricing-jobs
+```
+
+## Admin Roles
+
+- **super_admin**: Can do everything
+- **admin**: Can trigger pricing discovery and view logs  
+- **viewer**: Can only view admin logs
+
+## Security Features
+
+✅ **Organization-based auth** - No hardcoded user IDs
+✅ **Role-based permissions** - Different access levels
+✅ **Rate limiting** - Max 5 triggers per hour per admin
+✅ **Audit logging** - All admin actions logged
+✅ **Production-ready** - Secure by default
+
+## For Production
+
+1. Change roles in Clerk organization to be more restrictive
+2. Monitor audit logs in your database
+3. Set up alerts for admin actions
+4. Consider IP allowlisting for additional security

package/costcanary/CLAUDE.md

@@ -0,0 +1,228 @@
+You are a Senior Principal Full-Stack Engineer with 30 years of experience across startups and FAANG companies. You think systematically, write clean code, and prioritize security above all else.
+
+## Core Principles
+
+### 1. SECURITY FIRST
+- NEVER commit credentials, API keys, or secrets to GitHub
+- ALWAYS use environment variables for sensitive data
+- CHECK every file before committing: "Could this expose something sensitive?"
+- Use .env.local for local development, never .env
+- Add .env* to .gitignore IMMEDIATELY upon project creation
+- If you accidentally expose a credential, revoke it immediately and generate a new one
+
+### 2. DEVELOPMENT WORKFLOW
+- NIA (Needs Immediate Attention): Security vulnerabilities, broken builds, data loss risks
+- MCP (Mission Critical Priority): Authentication, payment processing, data integrity
+- NEVER push directly to main branch - always use feature branches
+- Commit messages: Keep them simple and professional. Format: "feat:", "fix:", "docs:", "style:", "refactor:"
+  - NEVER mention Claude, AI, or code generation tools
+  - Be concise and descriptive about WHAT changed, not HOW it was created
+  - Example: "feat: add authentication with Clerk" NOT "feat: AI-generated auth system"
+- Test locally before pushing ANYTHING
+- One feature = One commit (atomic commits)
+
+### 3. CODE QUALITY
+- Write code for humans first, computers second
+- Every function should do ONE thing well
+- If you need comments to explain WHAT, refactor the code
+- Comments explain WHY, not WHAT
+- No magic numbers - use named constants
+- DRY (Don't Repeat Yourself) but don't over-abstract
+
+### 4. VISUAL EXCELLENCE
+- This is 2025 - users expect Stripe-level design quality
+- Use Framer Motion for smooth animations
+- Implement micro-interactions (hover states, loading states, transitions)
+- Dark mode is mandatory, light mode is optional
+- Accessibility is not optional - WCAG 2.1 AA minimum
+- Performance matters - lazy load, optimize images, minimize bundle size
+
+### 5. CRITICAL THINKING
+- Question requirements: "Is this the real problem we're solving?"
+- Consider edge cases: "What happens when this fails?"
+- Think scale: "Will this work with 10x the data?"
+- Ask yourself: "How would I attack this system?"
+- Always have a rollback plan
+- Monitor everything that could break
+
+### 6. MODERN STACK DECISIONS
+- Choose boring technology for critical paths
+- Use managed services (Clerk, Railway, Vercel) over self-hosted
+- Serverless first, servers when necessary
+- TypeScript always, JavaScript never
+- Postgres for data, Redis for cache, nothing exotic
+
+### 7. USER EXPERIENCE
+- Every interaction should feel instant (<100ms)
+- Loading states are better than frozen UI
+- Error messages should tell users what to do next
+- Optimistic updates with rollback on failure
+- Progressive enhancement - core features work without JavaScript
+
+### 8. PROFESSIONAL BEHAVIOR
+- Document your decisions in code
+- Write README as if you'll forget everything in 6 months
+- Set up CI/CD on day one, not day 100
+- Monitor production like your salary depends on it
+- Teach through code reviews, don't just critique
+
+Remember: You're building production software that real people depend on. Act accordingly.
+
+## PROJECT: COSTHAWK (Rebranded from Cost Canary)
+
+### Project Overview
+- **Project Name**: CostHawk - AI API cost monitoring and optimization platform
+- **Brand**: CostHawk (UI displays this name, internal code still uses costcanary)
+- **Logo**: Hawk icon with circuit patterns at `/public/costhawk-logo.png`
+- **Purpose**: Track and optimize AI API costs across providers (OpenAI, Anthropic, etc.)
+
+### GitHub Repository
+- **Remote URL**: https://github.com/cdilling/costcanary.git
+- **Branch Strategy**: Always work on feature branches, never push directly to main
+- **Before Pushing**: ALWAYS verify no secrets are exposed with `git status` and `git diff`
+
+### Railway Deployment
+- **Live URL**: Deployed on Railway (check Railway dashboard for URL)
+- **Auto-deploy**: Enabled from main branch
+- **Build Command**: `npm run build` (use `npx prisma generate && npx prisma db push && npm run build` for first-time database setup)
+
+### Database Architecture (Completed Aug 14, 2025)
+- **PostgreSQL**: Hosted on Railway, all tables created and migrated
+- **Redis**: Hosted on Railway, connected and ready for caching
+- **Prisma ORM**: Configured with complete schema including User, ApiKey, UsageLog, Budget, Alert, AuditLog models
+- **Security**: AES-256-CBC encryption for all API keys with unique IV per encryption
+
+### Environment Variables (Set in Railway)
+```
+# Clerk Authentication (CONFIGURED)
+NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_test_ZXF1aXBwZWQtbW91c2UtODYuY2xlcmsuYWNjb3VudHMuZGV2JA
+CLERK_SECRET_KEY=sk_test_dVrwYXJ79GbHiNMpDBsh2w2Lx6bDjtzeSB57E8gRY3
+NEXT_PUBLIC_CLERK_SIGN_IN_URL=/sign-in
+NEXT_PUBLIC_CLERK_SIGN_UP_URL=/sign-up
+NEXT_PUBLIC_CLERK_AFTER_SIGN_IN_URL=/dashboard
+NEXT_PUBLIC_CLERK_AFTER_SIGN_UP_URL=/dashboard
+
+# Databases (Connected via Railway)
+DATABASE_URL=${{Postgres.DATABASE_URL}}
+DATABASE_PUBLIC_URL=${{Postgres.DATABASE_PUBLIC_URL}}
+REDIS_URL=${{Redis.REDIS_URL}}
+REDIS_PUBLIC_URL=${{Redis.REDIS_PUBLIC_URL}}
+
+# Security (CRITICAL - 32-byte hex key)
+ENCRYPTION_KEY=a2ef4f139870d5f1a248107c8e92372513644e204e2c637a0927b4b6e93c0ec0
+```
+
+### Project Structure
+```
+costcanary/
+├── app/
+│   ├── (auth)/          # Clerk authentication pages
+│   ├── (dashboard)/     # Protected dashboard routes
+│   ├── (marketing)/     # Public landing page with animations
+│   └── api/            # API routes (proxy endpoint coming next)
+├── components/
+│   ├── ui/             # shadcn/ui components
+│   ├── landing/        # Hero, Features, Pricing, Testimonials, Footer
+│   └── dashboard/      # Dashboard components
+├── lib/
+│   ├── prisma.ts       # Database client singleton
+│   ├── encryption.ts   # AES-256 encryption utilities
+│   ├── db-utils.ts     # Database helpers (user, API keys, usage)
+│   ├── audit.ts        # Audit logging functionality
+│   └── cost-calculator.ts # Provider-specific cost calculations
+├── prisma/
+│   └── schema.prisma   # Complete database schema
+└── middleware.ts       # Clerk authentication middleware
+```
+
+### Key Files Created
+1. **lib/encryption.ts** - Encrypts/decrypts API keys with AES-256-CBC
+2. **lib/prisma.ts** - Database connection singleton with proper typing
+3. **lib/db-utils.ts** - Helper functions for user management, API key storage, usage tracking
+4. **lib/audit.ts** - Audit logging for compliance and security
+5. **lib/cost-calculator.ts** - Calculates costs for all providers (OpenAI, Anthropic, etc.)
+6. **lib/admin-auth.ts** - Admin authentication and permission checking
+7. **prisma/schema.prisma** - Complete database schema with indexes and relations
+8. **app/api/pricing/models/route.ts** - API endpoint for fetching pricing models
+9. **app/api/admin/fix-pricing/route.ts** - Admin endpoint to repair/update pricing data
+
+### Known Issues & Solutions
+1. **Prisma Json Type Error**: Changed `Record<string, unknown>` to properly typed `JsonSerializable`
+2. **ESLint Errors**: Fixed unused variables with underscore prefix convention, removed unused imports
+3. **TypeScript Strict Mode**: All types properly defined for production build
+4. **Railway HPE_HEADER_OVERFLOW**: Fixed with optimized Node.js settings in package.json
+5. **Build Warnings**: `<img>` tags work fine, Next Image optimization optional
+
+### MCP Servers Configured
+1. **NIA MCP Server**: Installed and configured with API key
+2. **Context7**: For fetching documentation
+3. **Clerk**: Authentication toolkit with publishable key
+
+### Recent Updates (August 2025)
+
+#### Admin System & Pricing Management
+1. **Admin Authentication**: Organization-based admin system via Clerk
+   - Admin organization: "Cost Canary Admins" 
+   - Permissions: trigger pricing discovery, view admin logs, view sensitive data
+   - Admin panel in dashboard sidebar (only visible to admins)
+
+2. **Pricing Data System**:
+   - Database stores pricing for all AI models (GPT-5, Claude 4.1, etc.)
+   - Admin endpoints: `/api/admin/check-pricing`, `/api/admin/fix-pricing`
+   - Pricing discovery worker with Tavily integration
+   - August 2025 models added with correct pricing
+
+3. **Playground Updates**:
+   - Dynamic model loading from database (`/api/pricing/models`)
+   - Real-time pricing display below model selection
+   - Cost calculation using actual database pricing
+   - Support for wrapped API keys testing
+
+#### UI Rebrand to CostHawk
+- All user-facing text updated from "Cost Canary" to "CostHawk"
+- New hawk logo with circuit patterns
+- Updated metadata and page titles
+- Internal code references remain as "costcanary" for stability
+
+### Admin Features
+- **Pricing Status Page**: `/admin/pricing-status` - View all model pricing
+- **Trigger Discovery**: `/api/admin/trigger-pricing` - Force pricing update
+- **Fix Pricing**: `/api/admin/fix-pricing` - Repair/update pricing data
+- **Admin Overview**: `/dashboard/admin` - Admin dashboard
+
+### Next Steps
+- Complete API Proxy implementation with cost tracking
+- Implement real-time usage analytics dashboard
+- Add budget alerts and notification system
+- Integrate Stripe for billing
+
+### Testing Commands
+```bash
+# Verify database connection
+npx prisma studio
+
+# Run locally
+npm run dev
+
+# Type checking
+npx tsc --noEmit
+
+# Linting
+npm run lint
+
+# Format code
+npm run format
+```
+
+### Security Reminders
+- NEVER commit .env.local
+- ALWAYS encrypt API keys before storage
+- Audit log all sensitive operations
+- Use Row Level Security (enforced at application level)
+- Regular backups handled by Railway
+
+### Performance Notes
+- Composite indexes on userId, timestamp, provider
+- Connection pooling handled by Prisma
+- Redis ready for caching when needed
+- Lazy loading on landing page components

package/costcanary/CLERK_SETUP.md

@@ -0,0 +1,69 @@
+# Clerk Setup for Cost Canary
+
+## Current Configuration
+Your app is using these Clerk credentials:
+- Instance: `equipped-mouse-86.clerk.accounts.dev`
+- Publishable Key: `pk_test_ZXF1aXBwZWQtbW91c2UtODYuY2xlcmsuYWNjb3VudHMuZGV2JA`
+
+## If You Can't Find Your Clerk App
+
+### Option 1: Create a New Clerk Application
+1. Go to https://dashboard.clerk.com
+2. Click "Create application"
+3. Name it "Cost Canary"
+4. Choose "Next.js" as your framework
+5. Get your new keys from the dashboard
+
+### Option 2: Use Existing Test Keys (Development Only)
+The current test keys in your environment should work for development:
+```env
+NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_test_ZXF1aXBwZWQtbW91c2UtODYuY2xlcmsuYWNjb3VudHMuZGV2JA
+CLERK_SECRET_KEY=sk_test_dVrwYXJ79GbHiNMpDBsh2w2Lx6bDjtzeSB57E8gRY3
+```
+
+### Option 3: Create New Production Keys
+If you need production keys:
+1. Create a new Clerk application
+2. Go to API Keys section
+3. Copy the production keys (they start with `pk_live_` and `sk_live_`)
+4. Update in Railway environment variables
+
+## Update Railway Environment Variables
+
+Once you have your keys, update them in Railway:
+
+```bash
+# For new test keys
+NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_test_YOUR_NEW_KEY
+CLERK_SECRET_KEY=sk_test_YOUR_NEW_SECRET
+
+# For production keys
+NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_live_YOUR_PRODUCTION_KEY
+CLERK_SECRET_KEY=sk_live_YOUR_PRODUCTION_SECRET
+
+# Don't forget the webhook secret (if using webhooks)
+CLERK_WEBHOOK_SECRET=whsec_YOUR_WEBHOOK_SECRET
+```
+
+## Testing Your Setup
+
+1. Local testing:
+```bash
+npm run dev
+# Visit http://localhost:3000
+# Try to sign up/sign in
+```
+
+2. Check if authentication works:
+- Click "Sign In" button
+- Should redirect to Clerk's hosted sign-in page
+- After sign-in, should redirect back to dashboard
+
+## If Nothing Works
+
+The test keys in your current setup (`equipped-mouse-86`) should still be functional unless:
+- The Clerk application was deleted
+- The keys were revoked
+- You're hitting rate limits
+
+In that case, creating a new Clerk application is the fastest solution.

package/costcanary/DATABASE_SETUP.md

@@ -0,0 +1,136 @@
+# Database Setup Guide
+
+## 🔐 Security First
+
+**CRITICAL**: Never commit database credentials or encryption keys to Git.
+
+## 📦 Railway PostgreSQL Setup
+
+1. **Create Database on Railway**:
+   - Go to your Railway project
+   - Click "New Service" → "Database" → "PostgreSQL"
+   - Railway will automatically provision a PostgreSQL database
+
+2. **Get Database URL**:
+   - Click on your PostgreSQL service
+   - Go to "Variables" tab
+   - Copy the `DATABASE_URL` value
+
+3. **Update Local Environment**:
+   ```bash
+   # .env.local
+   DATABASE_URL="postgresql://postgres:xxxxx@xxxxx.railway.app:xxxx/railway"
+   ```
+
+4. **Add to Railway Environment**:
+   - Go to your app service in Railway
+   - Click "Variables"
+   - Add:
+     - `DATABASE_URL` (from PostgreSQL service)
+     - `ENCRYPTION_KEY` (from your .env.local)
+
+## 🗄️ Database Schema
+
+Our schema includes:
+- **User**: Synced with Clerk authentication
+- **ApiKey**: Encrypted API keys with AES-256
+- **UsageLog**: Detailed API usage tracking
+- **Budget**: Spending limits and alerts
+- **Alert**: Notifications for budget/usage
+- **AuditLog**: Security audit trail
+
+## 🚀 Migration Commands
+
+```bash
+# Generate migration (development)
+npx prisma migrate dev --name init
+
+# Apply migrations (production)
+npx prisma migrate deploy
+
+# Generate Prisma Client
+npx prisma generate
+
+# Open Prisma Studio (GUI)
+npx prisma studio
+
+# Reset database (CAUTION: deletes all data)
+npx prisma migrate reset
+```
+
+## 🔒 Security Features
+
+1. **API Key Encryption**:
+   - All API keys encrypted with AES-256-CBC
+   - Unique IV for each encryption
+   - Keys never stored in plain text
+
+2. **Row Level Security**:
+   - Users can only access their own data
+   - Enforced at application level via Prisma
+
+3. **Audit Logging**:
+   - All sensitive operations logged
+   - IP address and user agent tracking
+   - GDPR-compliant retention policies
+
+## 📊 Performance Optimizations
+
+1. **Indexes**:
+   - Composite indexes for common queries
+   - Timestamp indexes for time-series data
+   - Provider/model indexes for filtering
+
+2. **Connection Pooling**:
+   - Prisma handles connection pooling automatically
+   - Configurable via `DATABASE_URL` parameters
+
+3. **Query Optimization**:
+   - Use `select` to limit returned fields
+   - Batch operations with `createMany`
+   - Aggregate queries for statistics
+
+## 🧪 Testing Database
+
+For local development without Railway:
+
+```bash
+# Using Docker
+docker run --name costcanary-db \
+  -e POSTGRES_PASSWORD=localpass \
+  -e POSTGRES_DB=costcanary \
+  -p 5432:5432 \
+  -d postgres:15
+
+# Update .env.local
+DATABASE_URL="postgresql://postgres:localpass@localhost:5432/costcanary"
+```
+
+## 📈 Monitoring
+
+- Railway provides database metrics
+- Monitor slow queries with Prisma logging
+- Set up alerts for connection issues
+
+## 🆘 Troubleshooting
+
+1. **Connection Refused**:
+   - Check DATABASE_URL format
+   - Ensure Railway database is running
+   - Verify network connectivity
+
+2. **Migration Errors**:
+   - Check for pending migrations: `npx prisma migrate status`
+   - Reset if needed: `npx prisma migrate reset`
+
+3. **Type Errors**:
+   - Regenerate client: `npx prisma generate`
+   - Restart TypeScript server in VS Code
+
+## 📝 Best Practices
+
+1. Always use transactions for multi-step operations
+2. Implement retry logic for network issues
+3. Regular backups (Railway handles this)
+4. Monitor database size and performance
+5. Clean up old audit logs periodically

package/costcanary/DEMO_CHECKLIST.md

@@ -0,0 +1,62 @@
+# Demo Checklist - Cost Canary
+
+## Pre-Demo Verification (5 minutes)
+
+### 1. Landing Page ✅
+- [ ] Visit homepage - animations load
+- [ ] Pricing toggle works
+- [ ] CTA buttons redirect to sign-up
+
+### 2. Authentication Flow ✅
+- [ ] Sign up with test email
+- [ ] Email verification (if required)
+- [ ] Redirects to /dashboard after signup
+
+### 3. Dashboard Core Features ✅
+- [ ] Dashboard loads without errors
+- [ ] API Keys page accessible
+- [ ] Usage page shows data structure
+- [ ] Playground page loads
+
+### 4. Database Connection ✅
+- [ ] No Prisma connection errors in Railway logs
+- [ ] User creation works on signup
+- [ ] API key storage/retrieval functions
+
+## Demo Flow (10 minutes)
+
+### Landing → Sign Up → Dashboard
+1. **Homepage** (1 min)
+   - Show hero animation
+   - Highlight pricing ($0 free tier)
+   - Demonstrate mobile responsiveness
+
+2. **Authentication** (2 min)
+   - Sign up with demo email
+   - Show smooth redirect to dashboard
+
+3. **Dashboard Overview** (3 min)
+   - Point out navigation structure
+   - Show API keys management
+   - Preview usage analytics
+   - Mention playground feature
+
+4. **Key Features** (4 min)
+   - Highlight encryption security
+   - Show provider support (OpenAI, Anthropic, etc.)
+   - Point out real-time monitoring capability
+   - Demonstrate responsive design
+
+## Emergency Fallbacks
+
+If deployment fails:
+- [ ] Use local development (`npm run dev`)
+- [ ] Screen recording of working features
+- [ ] Focus on code quality and architecture
+
+## Railway Deployment Check
+
+Current status: Building static pages (7/28)
+Expected completion: 2-3 more minutes
+
+Post-deployment URL: Check Railway dashboard