# How Neople uses Weaviate

**90%**: “90% FASTER SEARCH”

As published on [weaviate.io](https://weaviate.io/case-studies/neople). Captured by usedby on 2026-10-08.

- Company: [Neople](https://www.usedby.ai/companies/neople.md)
- Tool: [Weaviate](https://www.usedby.ai/tools/weaviate.md)
- Industry: [Gaming & Esports](https://www.usedby.ai/companies/industry/gaming-esports.md)

## What the story says

Neople uses Weaviate as the vector database behind its Neople Assistants, digital co-workers for customer service, to query company-specific knowledge quickly and accurately. It replaced a Postgres database and uses Weaviate's hybrid search and out-of-the-box reranking module.

Summary written by usedby from the source page, in English. The figures are those of Weaviate and Neople, not ours.

> The amount of time it takes to receive a search result has been reduced from taking an average of 10 seconds to less than 1 second.

- **1000**: “Compared to their original database, Neople has increased the number of data objects stored in their Weaviate database by a factor of 1000 while improving query response times.”

> We're really eager to learn from other people and to use services like Weaviate that specialize in vector databases to improve our offering. In the end our main goal isn’t to maintain a database, it’s to deliver the best results and user experience for our customers
>
> Job Nijenhuis, co-founder and CTO

Source: [weaviate.io](https://weaviate.io/case-studies/neople), captured 2026-10-08.

## What usedby checked

We compared the story with its live page on 2026-10-08.

- Checked: the figure 90% is printed word for word on the page, near the name of Neople.
- Checked: the passage quoted above is copied word for word from the page, near the name of Neople.
- Checked: Neople uses Weaviate. Confirmed line. Latest check across sources: 2026-10-08.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/neople-weaviate · How we check: https://www.usedby.ai/methodology