krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-03 01:48:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1775 from qdrant/case-study-alhena

Browse Source 
Update case-study-alhena.md
This commit is contained in:
daniel-azoulai
2025-07-10 10:19:16 -07:00
committed by GitHub
parent fc24b4ddce 154567c302
commit bf6389313b
1 changed files with 0 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/blog/case-study-alhena.md
-3
View File
@@ -82,9 +82,6 @@ Multi-tenancy played a critical role in Alhena’s ability to scale while keepin
*“Multitenancy is a feature we find highly beneficial. It allows us to scale to hundreds of thousands of customers while managing only a few collections, thereby avoiding challenges in collection management. Additionally, we benefit from searching within their own search space. For each company, we implemented a delicate version control to ensure zero downtime after a new training finishes.”*
— Kang-Chi Ho, Founding AI Engineer, Alhena AI
![Architecture Diagram](/blog/case-study-alhena/diagram-alhena.png)
*Alhena’s retrieval and agentic stack. Qdrant powers vector search and filtering.*
## Simplifying global deployment through Qdrant Cloud
Alhena serves customers in both the US and EU, and data residency is a growing concern. Before Qdrant, hosting and scaling regional instances with FAISS or Pinecone required custom Kubernetes deployments and persistent storage management. Now, with Qdrant Cloud, the team can spin up managed clusters in any region with a few clicks.