RelevAI
Technology · WeKnowDB

Graph-native knowledge for applications and agents.

WeKnowDB is a graph-native knowledge system for applications and agents that need more than document retrieval. Relationships, evidence, permissions and time remain part of the knowledge structure itself, so different users and sessions can work against the same connected context.

Applications interact with it through conversational sessions and APIs. Results can remain graph-shaped or continue into structured outputs such as DataFrames and charts when the task calls for them.

Capabilities

Inside WeKnowDB

Explore the capabilities behind collaborative knowledge, provenance, structured data and graph-native operations.

02 · Collaboration

Multiple sessions can work on the same graph.

Independent conversations and users can operate concurrently over shared knowledge without turning the graph into separate copies.

03 · Permissions

Access is scoped inside the graph.

Different users can work against the same knowledge structure while only reaching the branches available to them.

04 · Attachments

Files can become connected knowledge.

Attachments can be processed into the graph instead of remaining detached from the knowledge they contribute.

05 · Provenance

Knowledge keeps its evidence.

Sources and reliability can travel with the facts they support, so answers do not lose where they came from.

06 · Temporal knowledge

The graph can preserve what was true, and when.

Temporal provenance lets the system reason over knowledge that changes instead of flattening every update into a single present state.

07 · DataFrames & charts

Structured results stay useful after the graph.

Queries can continue into tabular and chart-oriented outputs when the answer is better represented as structured data than prose.

08 · API calls

External operations can participate in the flow.

API interactions can sit alongside knowledge operations when an application needs live data or an external action.

09 · Sessions

Many sessions can share one knowledge space.

The graph can remain common while sessions carry their own conversational and operational context.

10 · Composition

Independent graphs can still compose.

Separate knowledge spaces can be connected through higher-level graph structures without collapsing them into one monolith.

See whether WeKnowDB fits your knowledge problem.

We can walk through the architecture, deployment model and current product surface.

Request a demo