A Firestore document is created for every feature, within the same collection. Variants of features have separate documents. Each document maps entities to their feature value. A metadata table is stored in the same Firestore collection as well to allow the provider to keep track of its own state. Featureform’s scheduler aims to achieve consistency between Firestore’s internal state with the user’s desired state as specified in the metadata service.


First we have to add a declarative Firestore configuration in Python. In the following example, only name and credentials are required, but the other parameters are available. Note: “credentials” refers to the file location of the Firestore Configuration (.json).
import featureform as ff
    name = "firestore",
    description = "Example inference store",
    team = "Featureform",
    collection = "",
    projectID = "",
    credentials = ""

Once our config file is complete, we can apply it to our Featureform deployment

featureform apply --host $FEATUREFORM_HOST

We can re-verify that the provider is created by checking the Providers tab of the Feature Registry.

Mutable Configuration Fields

  • description

  • credentials