> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview-1/gcp-services/gcp-databases/firestore-database.md).

# Firestore Database

Create a Firestore Database from within the DuploCoud platform.

Firestore is a flexible, scalable database for mobile, web, and server development from Google Cloud Platform. It's part of Firebase, a platform for developing mobile and web applications. Firestore is a NoSQL document database that simplifies storing, syncing, and querying data across multiple platforms and devices.

There are two Firestore Database modes to choose from:

* **Firestore Native Mode** is the default mode for Firestore. It provides a richer feature set and supports more advanced querying capabilities, such as compound queries and real-time updates. Use Firestore Native for new projects and applications that require real-time updates and advanced querying features.
* **Datastore Mode** provides a subset of Firestore's features and capabilities, supports a simpler data model, and lacks support for nested subcollections. Use Datastore Mode for migrating existing applications from Google Cloud Datastore to Firestore or for applications that do not require real-time updates or complex querying capabilities.

## Creating a Firestore Database

1. From the **Tenant** list box, select your Tenant name.
2. From the DuploCloud portal, navigate to **Cloud Services** -> **Firestore Database**.
3. Click **Add**. The **Add Firestore DB** page displays.<br>

   <figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FTz0IcxrrKDJM76j3oyws%2Ffirestore%201.png?alt=media&amp;token=f70fe4d2-96bf-4cc3-8b0e-243575494e7c" alt=""><figcaption></figcaption></figure>
4. In the **Name** field, enter a name for your database.
5. From the **Type** list box, select **FIRESTORE\_NATIVE** or **DATASTORE\_MODE**.
6. Select your location from the **Location** list box.
7. From the **Point in Time Recovery Enablement** list box, enable or disable point in time recovery, or lock your resources pessimistically.
8. From the **Delete Protection State list box,** enable or disable delete protection.
9. Click **Create**. Your Firestore Database is created.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FcF27QTBPJSB17KzF3B4B%2Ffirestore%202.png?alt=media&amp;token=636362c5-4965-4b87-9b16-286699519631" alt=""><figcaption><p>The details for the created Firestore Database.</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/automation-platform/overview-1/gcp-services/gcp-databases/firestore-database.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
