> For the complete documentation index, see [llms.txt](https://docs.feast.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feast.dev/v0.13-branch/getting-started/concepts/overview.md).

# Overview

The top-level namespace within Feast is a [project](/v0.13-branch/getting-started/concepts/overview.md#project). Users define one or more [feature views](/v0.13-branch/getting-started/concepts/feature-view.md) within a project. Each feature view contains one or more [features](/v0.13-branch/getting-started/concepts/feature-view.md#feature). These features typically relate to one or more [entities](/v0.13-branch/getting-started/concepts/entity.md). A feature view must always have a [data source](/v0.13-branch/getting-started/concepts/data-source.md), which in turn is used during the generation of training [datasets](/v0.13-branch/getting-started/concepts/feature-retrieval.md#dataset) and when materializing feature values into the online store.

![](https://1761717571-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LqPPgcuCulk4PnaI4Ob%2F-MaKKN_g2YldHEVf-XmU%2F-MaKTnYQG9kFhl8yPNTM%2Fimage.png?alt=media\&token=1db54ccd-cb92-4239-b4a9-2db77d4ff626)

## Project

Projects provide complete isolation of feature stores at the infrastructure level. This is accomplished through resource namespacing, e.g., prefixing table names with the associated project. Each project should be considered a completely separate universe of entities and features. It is not possible to retrieve features from multiple projects in a single request. We recommend having a single feature store and a single project per environment (`dev`, `staging`, `prod`).

{% hint style="info" %}
Projects are currently being supported for backward compatibility reasons. Projects may change in the future as we simplify the Feast API.
{% endhint %}


---

# 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.feast.dev/v0.13-branch/getting-started/concepts/overview.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.