Required
Real Supabase environment
Paste the anon key, service-role key, and production URL, then migrate every demo-mode action to database-backed writes.
Production readiness
What FansVibes needs to reach 100%
The local site is now wired for demo-mode testing. This checklist shows what must become real, secure, monitored, and compliant before a public paid launch.
Browser Supabase key
Configured
Service role key
Demo mode
Launch posture
Local MVP functional, production wiring required
Required
Payments and payouts
Closed beta uses sandbox credits. Live Paystack/Flutterwave needs reconciliation, webhooks, refunds, chargebacks, and payout approvals.
Required
Storage and delivery
Use private Supabase Storage buckets, signed URLs, upload limits, virus scanning, thumbnails, and watermark rendering.
Required
Identity and safety
Add KYC provider integration, age checks, consent evidence, DMCA workflow, report escalation, and audit-ready moderation trails.
Important
Messaging and realtime
Connect DMs, mass messages, read receipts, paid unlocks, calls, live tickets, notifications, and abuse controls to realtime data.
Important
Creator business tools
Persist campaigns, subscriptions, tiers, vault collections, PPV analytics, affiliate referrals, custom requests, and earnings exports.
Important
Fan lifecycle
Persist rewards, referrals, follows, saved purchases, receipts, subscription renewals, cancellation, blocks, and delete requests.
Required
Operational controls
Make feature flags, settings, admin roles, fraud rules, disputes, audit logs, and support actions write to protected tables.
Required
Compliance docs
Finalize terms, privacy, creator agreement, refund policy, content moderation policy, cookie policy, and local market tax rules.
Important
Email and notifications
Add transactional email, in-app notifications, payout alerts, security alerts, campaign reminders, and webhook retry alerts.
Required
Observability
Add error tracking, analytics, uptime checks, webhook logs, wallet reconciliation alerts, and admin activity monitoring.
Required
Security hardening
Run Supabase advisors, review RLS, lock SECURITY DEFINER functions, rotate secrets, set rate limits, and add abuse detection.
Recommended launch order
Do not jump straight from local demo to public launch.
Demo complete
All local pages, buttons, and test APIs should respond on localhost.
Private beta
Invite 5 creators and 20 fans with test payouts, manual moderation, and support review.
Paid pilot
Enable live payments for one market with low wallet limits and daily reconciliation.
Scale rollout
Enable feature flags by market, creator risk score, KYC status, and admin capacity.