The open-source
Firebase CMS
A real content management system on top of the Firebase project you already have. Your Firestore documents, your Storage files, your Auth users — edited in place, never copied anywhere.
My demo app
/
Products
256
FireCMS editing a Firestore products collection — the same documents your app reads.
What is a Firebase CMS?
A Firebase CMS is a content management system that stores its content in your Firebase project rather than in a vendor's database. Editors get structured forms, validation and permissions; your application keeps reading the same Firestore collections it always did.
That is the difference between a Firebase CMS and a conventional headless CMS. Contentful or Strapi own the content and hand it back over an API — a second database, a sync problem, a migration. A Firebase CMS sits on top of the database you already have.
Why the Firebase Console is not a CMS
The console is an excellent operations tool for developers. It was never meant to be handed to the people who write your content.
| Task | Firebase Console | FireCMS |
|---|---|---|
| Data entry | Raw key/value editor | Typed forms, 20+ field types, validation |
| Rich text | Plain strings | Notion-style editor, markdown |
| Files | Separate Storage tab, manual URLs | Upload fields wired to Firebase Storage |
| References | Copy and paste document paths | Searchable reference pickers |
| Non-technical access | Full project access, or nothing | Per-collection roles and permissions |
| Custom logic | None | onSave / onDelete callbacks, custom views |
Longer breakdown:FireCMS vs the Firebase Console.
A CMS across the whole Firebase stack
Not just Firestore documents — the services around them too.
React, all the way down
When the generated form is not enough, you are not stuck. Any React component can become a form field, and whole custom views can be added as tabs on a document or as new entries in the navigation.
- Cloud Functions
- Trigger your own logic from the CMS with
onSaveandonDelete. - Security rules
- FireCMS talks to Firestore as the signed-in user, so the rules you wrote keep applying.
products/B000ZHY0JK
A custom React view mounted as a tab on the entity, beside the generated form.
References resolve to real records, Storage files preview inline, and row actions run your own code.
Storage and Auth, already wired
Image and file fields upload straight to your Storage bucket and preview in the table. Editors sign in through Firebase Authentication, and what each of them can see is decided per collection.
- Firebase Storage
- Upload fields with previews and generated paths.
- Firebase Auth
- Roles and per-collection create / edit / delete permissions, resolvable per user or per document.
Hosted, or hosted by you
FireCMS Cloud
Connect your Firebase project and have a working CMS in minutes. Automatic updates, custom React views still supported, free trial.
Start buildingSelf-hosted
MIT-licensed source deployed in your own infrastructure, with custom auth, SSO and whatever compliance story you need.
See self-hosted optionsFirebase CMS FAQ
- What is a Firebase CMS?
- A Firebase CMS is a content management system that reads and writes directly to your own Firebase project — Firestore documents, Firebase Storage files and Firebase Auth users — instead of storing content in a third-party database. It gives editors a structured, permissioned interface over data your application already owns, so there is no migration and no second source of truth.
- Is there an open-source Firebase CMS?
- Yes. FireCMS is open source under the MIT licence. You can self-host the framework in your own infrastructure with full source access, or use the managed FireCMS Cloud if you would rather not run it yourself.
- Can a Firebase CMS generate itself from my existing Firestore collections?
- FireCMS infers a schema from the documents already in your Firestore collections and generates the CRUD views, forms and validation from it. You can then refine field types, labels and validation in the visual schema editor or in TypeScript.
- Firebase CMS vs building a custom admin panel — which should I choose?
- A custom admin panel costs weeks of build time and then never stops needing maintenance as your data model changes. A Firebase CMS gives you the CRUD layer, field types, validation, permissions and file handling on day one, and stays extensible: in FireCMS you can drop in your own React components or entire custom views wherever the defaults are not enough.
- Does FireCMS support custom field components?
- Yes. Any React component can be used as a form field, and you can add entirely new top-level views to the navigation. Custom views are supported both in the self-hosted framework and in FireCMS Cloud.
- How does user management work in a Firebase CMS?
- FireCMS builds on Firebase Authentication. You define roles and per-collection permissions (create, edit, delete) and can resolve permissions dynamically per user or per document, so editors, marketers and admins each see only what they should.
- Does FireCMS store or access my data?
- No. Your content stays in your own Firebase project. FireCMS runs against your Firestore instance using your own security rules and credentials, which is why there is no vendor lock-in and no data migration when you adopt or leave it.
