Opt-in: --services firestore,datastore

Google's Firestore and Datastore emulators, one flag away.

Documents, entities, collections and kinds on Google's own emulators, opt-in with --services.

Backed by: Google's Firestore and Datastore emulators Google's emulator

In the console

The Firestore query builder in the local console — Captured 2026-09-28 from main @5da2bd0. Product icons hidden.

The Datastore query builder in the local console — Captured 2026-09-28 from main @5da2bd0. Product icons hidden.

What it covers

Firestore and Datastore run on Google’s own emulators and start when you ask for them with --services. Each has an official emulator variable, so an application needs no code change. RPCs a test drives are Verified; every other RPC is Unknown, so nothing is claimed for it.

Firestore documents and collections through the official SDKs
Datastore entities and kinds through the official SDKs
Queries and transactions

Tested snippet

From docs/examples/ at main 82a2eb9. CI runs these blocks against CloudBurrow.

Node.js · Firestore

import assert from 'node:assert/strict';
import { randomUUID } from 'node:crypto';
import { Firestore } from '@google-cloud/firestore';

const db = new Firestore({ projectId: process.env.GOOGLE_CLOUD_PROJECT });
const doc = db.collection(`example-${randomUUID()}`).doc('hello');
await doc.set({ greeting: 'hello' });
assert.equal((await doc.get()).get('greeting'), 'hello');
await doc.delete();
await db.terminate();

This block is run by CloudBurrow's Node.js suite in CI. If it stops working, CI fails. docs/examples/node.md