About

We are building a product that separates WikiLLM, Retrieval, and Graph-LLM cleanly

EigenVertex exists to make knowledge systems feel reliable, inspectable and useful in real product workflows. It is not just a chat wrapper, and not just a vector pipeline. It is a knowledge product platform with a persistent WikiLLM mode, a Retrieval mode, and a Graph-LLM path for relational reasoning.

Product posture

  • Grounded by default
  • WikiLLM and Retrieval are separate modes, not a vague hybrid
  • Designed for apps, not demos
  • Built around traceability, control and durable memory

Why it exists

Most knowledge products break at the operational layer

Documents get parsed one way, media another way, search lacks provenance, chat loses context, and product teams are left stitching the experience together by hand. EigenVertex is meant to close that gap.

What it is

A knowledge workspace engine with two primary modes

The platform ingests documents, images, audio, video, web sources and inline notes, then either maintains a persistent wiki or runs retrieval-first evidence paths, depending on the workspace mode you chose at creation time.

What it is not

Not a magical black box

We want sources, locators, status, progress and cleanup actions to stay visible. The product should feel powerful because it is legible, not because it hides complexity behind vague AI copy.

Platform philosophy

Grounded answers should feel native to the product

Citations, human sources, note types, timecodes, page labels and structured outputs are not afterthoughts. They are part of the user experience from the beginning, whether the answer comes from a persistent wiki or a retrieval-first path.

Integration philosophy

Developers should be able to consume EigenVertex like infrastructure

That means native routes for workspace creation, ingestion, search, wiki maintenance, conversations and admin flows, plus an OpenAI-compatible facade when teams want to integrate it as if it were a model.