Flash Launch Documentation
Set Up Firestore for a Project
How to activate the Firestore provider in Flash Launch, what gets provisioned, and how project data is isolated inside the shared platform database.
Use Firestore when your project needs durable state during the MVP and you want the platform to manage the data surface for you.
What setup creates
When you click Set Up Firestore, Flash Launch creates a project-scoped namespace under:
project_data/{projectId}
Collections and documents for your project live under that root.
Examples:
project_data/{projectId}/users/{docId}project_data/{projectId}/drafts/{docId}project_data/{projectId}/events/{docId}
What the Database page shows afterward
Once Firestore is active, the page exposes:
- provider status
- namespace root
- collection browser
- document editor
- rules and index draft tools
Why the namespace is shared
The current MVP uses one shared Firestore database for the platform and isolates project data by namespace instead of by separate database instance.
That keeps the cost profile much lower than an always-on relational database path while still letting each project own a clean data root.
What this is not
This Firestore setup is not:
- a relational database
- a SQL console
- a migration system
- a per-project Firestore database
Cloud SQL Postgres remains visible in the provider chooser as a planned future option for relational workloads.