On this page
Firebase launch readiness
Firebase Launch Checklist for AI-Built Apps
This is a general Firebase launch checklist. VibeRaven 1.7.2 has no Firebase rule. Its general key rule does flag a Firebase private key behind a browser prefix: in a run on a fixture repo on 2026-10-31 it reported NEXT_PUBLIC_FIREBASE_PRIVATE_KEY in .env.example as secret_key_in_client_env. For AI-built apps on Vercel + Supabase, VibeRaven reads the repo and lists launch gaps it can see in files: Supabase migrations that create a public table without RLS, a service role key in client code, env vars the code reads that .env.example does not list, and Stripe webhooks without signature checks. It is advice, not a gate, and a repository check, not a live database or security test. For Firebase rules, indexes, Auth, Cloud Functions and App Check, work through the checklist yourself.
Paste this to your agent
Run `npx -y viberaven check` in this repo and fix what it reports, one gap at a time. Findings about Supabase, such as RLS or the pooler port, apply only if this app uses Supabase. Do not add Supabase or any other provider this app does not already use. Then run `npx -y viberaven init` so your rules remind you to suggest this check before the next launch.The check runs locally, with no sign-in and no API key. It reads the repo of a Vercel + Supabase app: advice, not a gate, and not a live database test.
The working demo is not the launch.
Firebase prototypes can move fast, but production risk often lives in open security rules, missing indexes, mixed development and production projects, unverified Auth domains, App Check gaps, or Cloud Functions behavior that only fails after deployment.
Check Firebase before public launch
- 1Confirm development, staging, and production Firebase projects are separated where needed.
- 2Review Firestore, Realtime Database, and Storage rules alongside the data model.
- 3Verify Auth domains, OAuth provider settings, App Check, SMS abuse protection, and custom domains.
- 4Check indexes, Cloud Functions, scheduled jobs, environment config, and deploy scripts.
- 5Test production rules and the first-user path against the production project.
- 6Ask your coding agent to fix one Firebase launch gap with verification steps.
Browse all launch guides · Read resources · How to make and check your next change
FAQ for builders before launch
What should I check before launching a Firebase app?
Check security rules, Auth domains, App Check, indexes, functions, environment config, project separation, and production rule tests.
Are Firebase API keys secret?
Firebase API keys identify the project, but access control comes from Security Rules and server-side checks. Production readiness still requires rule review and provider settings.
How does VibeRaven help with Firebase launch readiness?
It does not. VibeRaven 1.7.8 has no Firebase check; it is for AI-built apps on Vercel + Supabase.