← Index
Discontinued after pilotAug — Dec 2025· Founder

VectralQ

AI enterprise search — built, piloted, and deliberately shut down

The problem

Enterprise search that answers questions rather than returning ten links has to do two things that pull against each other: cite its sources exactly, and come back fast enough to replace someone's Ctrl-F habit.

What I built

  • Combined BM25 and dense embeddings into a hybrid retriever, so exact-term matches and semantic matches both surface instead of trading one off against the other.
  • Put the vector index in Postgres with pgvector and pushed the retrieval logic down into PLpgSQL, keeping ranking next to the data rather than round-tripping it into Python.
  • Multi-tenant from the start, scoped by tenant header, with a streaming SSE query endpoint so answers rendered token-by-token rather than arriving all at once after a wait.
  • Shipped a developer API and an embeddable widget with a two-line integration, because the adoption bottleneck for search is installation, not quality.
  • Ran the entire stack against a local Ollama model in Docker Compose, so the whole system could be developed and demoed with no external API dependency or per-token cost.

Outcome

  • Selected for McGill TechAccel within a month of starting.
  • Ran pilots with real users, then shut the product down on weak demand signals.

Stack

PythonFastAPIPostgreSQL + pgvectorPLpgSQLTypeScriptReactDockerOllama

Note

Shutting it down was the right call and the most useful thing the project taught me. The retrieval worked; the demand did not. I would rather have four months of evidence that a market is not there than a year of hoping it is.

Next

DocuMint

Paste a GitHub link, get a README that describes the repository. The hard part is deciding what to read.