Pay for writes. Never for reads.

Any operation that changes a document: creating, updating, deleting, or a field-level transform such as an increment. Reads — browsing, querying, live mode, schema inference — are never counted, on any plan.

Every Firestore database you touch gets 1,000 free writes per billing period. When you need more than that on a particular database, you mark it premium. That consumes one of your plan's premium slots and unlocks a block of writes for it.

Writes to that database are blocked until you add another lease block or your period rolls over. Reading is unaffected — you keep full access to browse and query everything. FireFetch tells you which of the two situations you are in rather than showing a generic error.

Periods are anchored to the day you signed up, capped at the 28th so every month has one. If you signed up on the 9th, your period rolls on the 9th. It is deliberately not the calendar month.

Yes. Slots release when your period rolls over, so a database you marked premium for a one-off migration does not occupy a slot forever.

Yes, at any time. Moving up gives you more premium slots and larger write blocks immediately.

Your licence is a signed token carrying an offline write allowance, so FireFetch keeps working without a connection to our licensing service. Firestore itself obviously still needs network access.

No. Firestore traffic goes directly from your machine to Google and never passes through us. Our licensing service identifies a database by a salted HMAC computed on your computer, not by its project id, so we cannot enumerate or correlate your projects.