What this property was
PlatePlatform is a restaurant education platform: structured courses with topics and lessons, enrollments, progress tracking, quizzes, certificates, subscriptions, plus a library layer of guides, books, and posts. It's a real LMS, not a landing page cosplaying as one — Next.js 16, Prisma over MariaDB, Stripe for payments, AI image generation for course visuals, the works. The database schema reads like a syllabus for building course software: users, courses, lessons, quiz attempts, payments, certificates.…
Evidence recorded in the manuscript
Revenue: zero, with unusual certainty — a checkout cannot convert visitors who cannot load the site. Traffic: whatever the parking page collected, which benefited the parking company, not me. Inside the walls: a full curriculum schema, working Stripe integration, and a healthy PM2 process serving no one. Costs: the standard domain and build investment, plus the uncounted cost of every audit cycle that re-discovered the same problem and re-filed it under "pending: owner." I genuinely don't know how many would-be visitors bounced off that parking page.…
The lesson recorded after launch
Your stack extends below your code, and the layers you don't monitor are the layers that kill you silently. Application failures are loud — crashes, 500s, log noise. Registrar and DNS failures are perfectly quiet: your server stays green while your domain serves someone else's parking ads. Three practices would have saved PlatePlatform months of death: external uptime checks that fetch the public URL and verify it's actually your site (not just any 200 — a parking page returns 200 too); calendar-level audits of registrar accounts, expiries, and nameserve…