Haystack Core Integrations

This repository contains integrations to extend the capabilities of Haystack. The code in this repo is maintained by deepset, see each integration's README file for details around installation, usage and support.

Quick start

You will need hatch to work on or create new integrations, open this link and follow the install instructions for your operating system and platform.

All the integrations are self contained, so the first step before working on one is to cd into the proper folder. For example, to run the tests suite for the Chroma document store, from the root of the repo:

sh $ cd integrations/chroma $ hatch run test:all

Hatch will take care of setting up an isolated Python environment and run the tests.

Please check out our Contribution Guidelines for all the details.

Inventory

| Package | Type | PyPi Package | Status | |----------------------------------------------------------------------------------------------------------------|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | amazon-bedrock-haystack | Embedder, Generator, Ranker, Downloader | | | | amazon-sagemaker-haystack | Generator | | | | anthropic-haystack | Generator | | | | astra-haystack | Document Store | | | | azure-ai-search-haystack | Document Store | | | | chroma-haystack | Document Store | | | | cohere-haystack | Embedder, Generator, Ranker | | | | deepeval-haystack | Evaluator | | | | elasticsearch-haystack | Document Store | | | | fastembed-haystack | Embedder, Ranker | | | | github-haystack | Connector | | | | google-ai-haystack | Generator | | | | google-genai-haystack | Embedder, Generator | | | | google-vertex-haystack | Embedder, Generator | | | | hanlp-haystack | Preprocessor | | | | jina-haystack | Connector, Embedder, Ranker | | | | langfuse-haystack | Tracer | | | | llama-cpp-haystack | Generator | | | | llama-stack-haystack | Generator | | | | mcp-haystack | Tool | | | | meta-llama-haystack | Generator | | | | mistral-haystack | Embedder, Generator | | | | mongodb-atlas-haystack | Document Store | | | | nvidia-haystack | Embedder, Generator, Ranker | | | | ollama-haystack | Embedder, Generator | | | | openrouter-haystack | Generator | | | | opensearch-haystack | Document Store | | | | optimum-haystack | Embedder | | | | pinecone-haystack | Document Store | | | | pgvector-haystack | Document Store | | | | qdrant-haystack | Document Store | | | | ragas-haystack | Evaluator | | | | snowflake-haystack | Retriever | | | | stackit-haystack | Embedder, Generator | | | | together-ai-haystack | Generator | | | | unstructured-fileconverter-haystack | File converter | | | | watsonx-haystack | Embedder, Generator | | | | | weaviate-haystack | Document Store | | | | weave-haystack | Tracer | | | | instructor-embedders-haystack | Embedder | | Staged |

Releasing

[!NOTE] Only maintainers can release new versions of integrations. If you're a community contributor and want to release a new version of an integration, reach out to a maintainer.

To release a new version of an integration to PyPI tag the commit with the right version number and push the tag to GitHub. The GitHub Actions workflow will take care of the rest.

1. Tag the commit with the right version number

   The tag needs to have the following format:

   git tag integrations/<INTEGRATION_FOLDER_NAME>-<version>

   For example, if we want to release version 1.0.99 of the google-vertex-haystack integration we'd have to push the tag:

   git tag integrations/google_vertex-v1.0.99

2. Push the tag to GitHub

   git push --tags origin

3. Wait for the CI to do its magic

4. Review the changelog PR

   If the release is successful, the HaystackBot will open a pull request to generate the changelog. Add yourself as the reviewer. If there are any issues, edit the changelog manually.

[!IMPORTANT]
To ensure the changelog is accurate, it's recommended to tag a commit that includes the actual changes for the integration (usually the PR merge commit). Tagging a commit that doesn't contain those changes can lead to an incorrect changelog.