Skip to main content
Connect a vector database (Qdrant, Pinecone, and others) to Raily. Once connected, Raily can search its collections with access control and usage tracking on top. The steps are similar for every provider. Pick your provider in the tabs below for its connection fields and steps.

What you can do

Once a vector store is connected, Raily searches it with:
  • Semantic search - find content by meaning, not just keywords.
  • Metadata filtering - narrow results by date, author, category, or any field in your Data Catalog.
  • Hybrid search - combine semantic similarity with keyword matching.
  • RAG - feed retrieved passages to an LLM so its answers are grounded in your content.
Access control and usage analytics apply to every search, whichever provider you connect.

Before you start

  • Admin access to the tenant.
  • The connection details for your vector store (URL, API key, or connection string).
  • At least one collection (or index/table) that already holds embeddings.

Steps

In the sidebar, open Search Rail (under Rails) and click Connect source.
Connect a data source in Search Rail

Pick where your data lives

Then pick your provider and follow its steps.
1

Open Qdrant

Click the Qdrant card.
2

Enter the connection details

  • Name for the integration.
  • Qdrant URL, for example your-project.europe-west3-0.gcp.cloud.qdrant.io:6333.
  • API Key. Required for Qdrant Cloud, optional for local Qdrant.
Qdrant connection form

Qdrant connection form

3

Add collections

Click Fetch Collections and enable the ones you want, or add a collection by name (lowercase letters, numbers, and underscores).
4

Set an embedding config

Pick an embedding config for each collection. It must match the model that created the vectors.Don’t have one yet? Open the embedding config picker and click Create New.
Embedding config picker with Create New

Create a new embedding config

Enter a Name, pick a Provider, and set the Model Name and Dimension to match the model that created your vectors. Add an API Key if the provider needs one, then save.
Embedding config form fields

Embedding config form

5

Save

Click Create Integration. Raily then configures agentic search for each collection automatically. This can take a few minutes, after which the integration appears under My Integrations with an Active status.
Once it finishes, open Inventory → Data Catalog to see the generated configuration for each collection.
6

See it in the Data Catalog

After generation finishes, Raily opens the collection in Data Catalog.
Collection configuration in the Data Catalog

Collection configuration in the Data Catalog

Best practices

Match the embedding config

The embedding config must match the model that created the vectors.

Design useful metadata

Index the fields people filter by so the agent can use them.

Keep embeddings current

Re-embed when content changes so search stays accurate.

Use access control

Apply policies so each endpoint exposes only what it should.