
The open-source feature store for high-scale, production-ready AI and LLM applications.
Visit WebsitePros
Cons
Free
No reviews yet. Be the first to review Feast!
Top alternatives based on features, pricing, and user needs.
Feast manages the lifecycle of features, storing historical data for training and serving the latest feature values for real-time inference. It uses event timestamps to retrieve features as they appeared at a specific point in time, ensuring that the data used for training accurately reflects the data available at the time of prediction.
The OpenLineage integration provides end-to-end ML lineage tracking, connecting Feast's feature lineage with upstream data pipelines (e.g., Airflow, Spark, dbt) and downstream model training. This offers unified visibility into the entire ML data flow, helps answer questions about feature origins and model dependencies, and aids in auditing for compliance without requiring code changes.
Yes, Feast can directly consume dbt models. Users tag dbt models intended as features, and then use `feast dbt import` to automatically generate Feast definitions (entities, data sources, feature views) from the dbt project's `manifest.json`. This allows dbt models to become production-ready features for AI without rewriting transformations.
Feast supports RAG applications through its `retrieve_online_documents` function. This allows for retrieving documents or chunks of text, along with their embeddings and associated metadata, using vector similarity search. This capability is crucial for LLM applications that need to fetch relevant context in real-time.
Feast tracks comprehensive metadata for Feature Views (names, types, descriptions, TTL, entities, tags), Feature Services (constituent views, total feature count, descriptions, tags), and Data Sources (type, connection URIs, timestamp fields, field mappings). This metadata is attached as OpenLineage facets, making it queryable and explorable in any OpenLineage-compatible tool like Marquez.
Feast is designed to integrate with a variety of data sources and online stores. While specific examples aren't exhaustively listed, it generally supports common data warehouses, data lakes, and streaming platforms as offline stores, and low-latency key-value stores (like IKV) for online serving. The exact integrations depend on the configured provider and available plugins.
Source: feast.dev