VERITASGRAPH
Enterprise GraphRAG · Provenance · Governed AI
initializing graph runtime0%
● SYSTEM ONLINE / governed graph intelligence

AI that can show you why it knows.

VeritasGraph combines knowledge-graph reasoning, hierarchical tree search, retrieval and verifiable provenance to turn enterprise information into grounded, auditable AI answers — with governed agents on your infrastructure.

View architecture ↓ GitHub ↗
Simulation mode runs entirely in this page — no API key required.
VERITASGRAPH / KNOWLEDGE FABRIC● LIVE SIMULATION
RELATIONAL CONTEXT ENGINE
nodes · typed edges · evidence · multi-hop traversal
0
Indexed nodes
0
Relationships
5-hop
Reasoning path
100%
Traceable demo claims
LOCAL
Deployment option

Watch a question
become evidence.

Run a simulated GraphRAG request and watch semantic retrieval, graph traversal, multi-hop reasoning and provenance resolve in sequence.

veritasgraph / query console
READY
GRAPH TRACE / IDLE00.000s
✓ VERIFIED ANSWER

The incident is associated with a gateway timeout introduced during deployment v4.8 in the APAC environment.

Gateway timeoutAPACDeployment v4.8Incident #4821
✓Semantic retrieval —
✓Graph entry points —
✓Multi-hop traversal —
✓Tree context fusion —
✓Evidence collection —
✓Provenance verification —
Evidence / source spans
incident_report_4821.md
chunk: 07 · relation: CAUSED_BY
deployment_log_v4.8
chunk: 19 · relation: INTRODUCED
apac_gateway_metrics
chunk: 03 · relation: CORROBORATES

Structure + semantics
beats similarity alone.

VeritasGraph can combine graph relationships, hierarchical document context and retrieval signals instead of treating every chunk as an isolated island.

01
⌁
Ingest
Documents become structured knowledge.
02
◇
Extract
Entities and typed relationships emerge.
03
◎
Retrieve
Graph, tree and retrieval signals combine.
04
↯
Traverse
Relevant subgraphs are explored hop by hop.
05
◌
Reason
The model receives relational context.
06
⌁
Verify
Claims map back to source evidence.
07
✓
Answer
A grounded, auditable response.
Baseline

Traditional RAG

Query →
Embedding →
Top-K chunks →
LLM →
Answer
Relationship context can be implicit, fragmented or difficult to audit.
VeritasGraph

GraphRAG

Query →
Retrieval + tree context →
Graph entry points →
Multi-hop traversal →
Evidence + provenance →
Verified answer

Navigate hierarchy.
Reason across relationships.

A document tree answers “where is the relevant context?” while a graph answers “what is connected to what?” The two views can cooperate during retrieval.

DocumentAnnual Report
NodeIncident #4821
SectionReliability
EdgeCAUSED_BY
Chunk#07
EntityGateway

Every important claim
has a trail.

Instead of presenting citations as decoration, the interface makes provenance a first-class object: claim → source span → graph relationship → evidence.

✓
Gateway timeout
incident_report_4821.md · chunk 07
98.7%
✓
Deployment v4.8
deployment_log_v4.8 · chunk 19
96.2%
✓
APAC environment
regional_metrics · chunk 03
94.8%
✓
Incident #4821
incident_registry · record 4821
99.1%

AI that is
allowed to act.

Studio-style orchestration can place guardrails, memory, knowledge, context budgeting, tools and data logging around every agent turn.

01 / CONTROLGuardrails
02 / CONTEXTMemory
03 / KNOWLEDGEKnowledge Graph
04 / BUDGETHeadroom
05 / ACTIONTools
06 / AUDITData Log
OUTPUTGoverned response ✓

Run a governed turn.

The simulation shows how an agent request can pass through explicit control boundaries before it reaches tools or produces an auditable response.

veritasgraph://studio/orchestrator
awaiting request...

Guardrails are
part of the path.

Show a recruiter that governance is not an afterthought: policy checks, PII redaction and audit events can be visible in the same execution trace.

Block unsafe input before action.

Click the simulation to watch a sensitive payload get detected, redacted or blocked before the agent reaches a tool.

policy://ready
no active events

Make decisions inspectable.

12:41:07 PII detectorDETECTED
12:41:07 Policy engineBLOCKED
12:41:08 Audit storePERSISTED
12:41:08 Agent runtimeSAFE EXIT

From citizen report
to verified case.

A concrete workflow from the repository: incident reporting, computer-vision validation, knowledge-graph routing, evidence fusion and case registration.

● INCIDENT INTELLIGENCE

Overflowing waste near market

Citizen report · photo attached · location resolved · graph context available

Evidence fusion, not guesswork.

01
Citizen reportphoto + description + location
READY
02
CV validationYOLO / VLM-style evidence check
WAIT
03
Graph routingmatch place, category and history
WAIT
04
Evidence fusioncombine independent signals
WAIT
05
Case registrationcreate auditable incident record
WAIT

Connect the graph
to agent ecosystems.

VeritasGraph includes an MCP bridge pattern so compatible clients can discover and invoke graph capabilities through explicit tools.

Agent surfaces

VS Code
Cursor
Cline
Custom agents
VeritasGraph
MCP Server
JSON-RPC · tool discovery · graph access
querysearch_entitiesget_graphingest

Explicit tools

Knowledge search
Graph traversal
Document ingest
Evidence retrieval

Under the hood.

A recruiter-friendly view of how the system moves from raw information to an answer that can be traced, governed and inspected.

VERITASGRAPH / SYSTEM MAPSIMULATION TELEMETRY
01 / INPUT

Documents

PDF, text, structured or application data.

02 / PARSE

Extraction

Entities, relations, sections and evidence.

03 / KNOWLEDGE

Graph Store

Nodes, typed edges and grounded source links.

04 / RETRIEVAL

Hybrid Search

Graph + tree + semantic retrieval signals.

05 / REASONING

Multi-hop Context Engine

Find entry points, traverse relevant relationships, fuse hierarchy and assemble evidence-aware context for the model.

06 / CONTROL

Guardrails

Policy checks, redaction and governance boundaries.

07 / ACTION

Agents + Tools

Memory, tools, MCP and governed orchestration.

08 / OUTPUT

Verified answer + provenance + audit trace

The interface exposes the path so users can understand not only what the system answered, but which entities, relationships and source spans supported it.

Built as an
engineering system.

Technology grouped by responsibility so a recruiter can scan the engineering surface without wading through a giant logo wall.

Language
Python3.10+ · async services · data pipelines
Backend
FastAPIAPIs · orchestration · local studio
AI
GraphRAGLLM reasoning · retrieval · citations
Knowledge
Knowledge Graphsentities · typed relations · traversal
Graph DB
Neo4j / native graphgraph storage and exploration
Local AI
Ollamaprivacy-first local inference
Agents
MCPtool discovery · agent connectivity
Deployment
Docker / Cloudlocal, on-prem or cloud workflows
Retrieval
Tree + Graph + Vectorhybrid context assembly
Governance
GuardrailsPII redaction · policy controls
Observability
Traces + Logsstage-level execution visibility
Research
Clinical KGde-identification · contradictions · coding

Query playground.

What caused the APAC payment incident?

Run a query to see a simulated grounded answer with an inspectable reasoning trace.

veritasgraph://playground status: ready mode: simulation evidence: waiting provenance: waiting -------------------------------- Tip: click a query above or run the main demo.