Firestore

AddisDB reads Cloud Firestore (Native mode) through its REST API. Root collections appear in the sidebar, documents land in the grid with their typed fields decoded to plain JSON, and the driver only ever issues read endpoints — so this connection cannot modify your data even if you try.

Who it is for

Firestore is the database most Firebase apps grow up on: serverless, scaled by Google, with real-time listeners and offline sync built into its client SDKs. Security rules live with the database rather than in your backend, which is what makes direct client access practical.

Its query model is deliberately narrow so that every query stays fast at any size: no joins, no aggregations beyond count/sum/average, and composite indexes required for anything combining an inequality with an ordering. What you cannot express in a query, you denormalize into the document.

It suits mobile and web applications that want live updating data without operating a backend, prototypes that need to ship this week, and products where per-user data isolation is enforced by rules.

Set up access

1. In the Firebase or Google Cloud console, note your project id and confirm the database is Firestore in Native mode.
2. Install the gcloud CLI and run gcloud auth login, then gcloud config set project YOUR_PROJECT_ID.
3. Generate an access token with gcloud auth print-access-token — this is what you paste into AddisDB.
4. Make sure your account has the Cloud Datastore Viewer role (or broader) on the project.

# The token AddisDB needs
gcloud auth print-access-token

Datastore mode is a different product with a different API. If the console calls your database "Firestore in Datastore mode", this engine will not read it.

Connect from AddisDB

1. New Connection → Firestore under Document. Port prefills to 443.
2. Put your GCP project id in the Database field. To target a named database rather than the default, use project/databaseId.
3. Paste the access token into the API key / token field.
4. Test, then Save.

How to query it

Type a collection path to list its documents, or paste a structured query for anything more specific.

// List a collection
users

// Or a structured query
{ "from": [{ "collectionId": "orders" }],
  "where": { "fieldFilter": {
    "field": { "fieldPath": "status" },
    "op": "EQUAL",
    "value": { "stringValue": "shipped" } } },
  "limit": 50 }

A subcollection is addressed by its full path — users/abc123/orders — because it belongs to a document rather than to the root. To query the same subcollection name across every parent at once, set allDescendants on the collection selector.

Security rules do not apply here. They govern the client SDKs; the REST API is governed by IAM, so what you can read is decided by the role on your Google account.

What AddisDB gives you

• Root collections listed in the sidebar.
• Firestore’s typed field values decoded to ordinary JSON, flattened into the grid.
• A connection that is read-only by construction — there is no write path in the driver at all.
• The Chart view, ⌘K search, and AI chat grounded in your collections.
• Query tabs and history for the structured queries you will reuse.