Currently, the Firebase Emulator Suite allows running only a single Data Connect service instance locally. For projects utilizing a microservices architecture with multiple isolated Data Connect services, this creates a significant blocking issue during development.

Primary Feature Request: Multi-Service Emulation - Please update the Emulator Suite to support running multiple Data Connect services simultaneously.

Alternative / Interim Solution: Hybrid Cloud Fallback - If full multi-service emulation is technically complex to implement immediately, please introduce a "Hybrid" mode as an alternative.

Current Behavior: When the emulator is running, all calls to Data Connect are forced to look locally. If a specific service isn't emulated, the call fails, even if a live version exists.

Proposed Behavior: Allow an opt-in flag (e.g., --allow-cloud-fallback) that permits the SDK to connect to live/deployed Cloud instances for any Data Connect service not currently running in the emulator.

Why this is critical: Support has confirmed the current "walled garden" approach is intended to prevent accidental costs. However, without multi-service support, this leaves developers in a deadlock: we cannot emulate our full stack locally, and we cannot mix local emulation with cloud resources. We are effectively forced to test entirely in production.