Build Admin Panels, Dashboards, and Internal Tools on top of your Firestore data with authentication, permissions, and workflows built in.
Generate CRUD screens over your documents so support can fix a record without a developer and without console access.
Add Firestore as a resource and authenticate with a service account key. Jet reads your collections and generates screens automatically. You can scope the service account to specific collections first if you would rather start with a narrower view.
Yes. Jet gives your team a spreadsheet-style editor over your Firestore collections, with search, filters and inline editing on nested fields and subcollections, so people who should never open the Firebase console can still work with the data: support agents, operations, finance and external users, each seeing only what their role allows.
Yes. Writes go straight back to your collections. Forms validate types and required fields before the write, roles decide who can change what, approvals can hold the risky updates, and every change is recorded in the audit log with the person who made it, alongside the security rules Firestore already enforces.
No. Jet reads and writes your collections in place through Firestore's API. There is no export to schedule and no migration to plan, so Firestore stays the single source of truth.
Jet authenticates with a scoped service account rather than a shared login, and access is controlled with SSO plus row and field level permissions on top of the security rules you already wrote. If your data must not leave your network, Jet can run in your own cloud account or fully on-premise.
Yes. Firestore can sit alongside Firebase, a REST API or HubSpot in the same app, and a single screen can read from more than one of them at once.
