Feature Request: Firebase Database Support (with Multi-Project Capability)

[TheAwesomeAJ]

Hi Payload Team,

First off, I just want to say how much I appreciate what you’ve built with Payload. It’s an incredibly polished and developer-centric CMS—the flexibility, clean architecture, and excellent TypeScript support make it a real pleasure to work with. Honestly, it’s the kind of tool that gives me confidence when planning long-term projects.

That said, there’s one key feature that’s currently holding me back from adopting it fully: Firebase database support, especially with the ability to connect to multiple Firebase projects.

In my architecture, I use different Firebase projects to segment data by domain—for example, one project handles user auth and profiles, another manages application submissions, and a third holds blog content. This separation is critical for both security and scaling reasons.

If Payload could support Firestore (or Realtime Database) as a primary database—and allow dynamic configuration across multiple Firebase projects—it would unlock huge potential. I’d be able to use Payload’s amazing interface and schema system while keeping the Firebase infrastructure I’ve already invested in.

Even if it started as a community adapter or experimental plugin, I’d love to see something in this direction. Let me know if there’s any way I can help support or test such a feature!

Thanks again for an incredible product. Excited to see what the future holds for Payload.

TheAwesomeAJ