Rich document types
In development
PDF, DOCX, and image ingestion with OCR so slides, contracts, and scans join your knowledge base without manual paste.
Memraiq
Hosted knowledge workspace in private beta: text documents today, graph-augmented answers with citations, and a clear roadmap for richer files and developer tools.
01 / Chat
Every answer is tied to your indexed documents. The model can't make things up — if it can't find supporting context, it says so. Each response includes the specific sources it drew from, so anyone on your team can verify the answer.
Chat trace
You
What does our onboarding doc say about access provisioning?
Memraiq
According to your onboarding guide, access is provisioned within 24 hours of account creation. New members receive an email invite with a temporary password...
↳ onboarding-guide.md · §3.2 (0.94)
↳ access-policy.md · §1 (0.81)
Pipeline run
02 / Indexing
Currently supports Markdown and plain text uploads. A structured pipeline chunks, embeds, and extracts entities for the knowledge graph. Background workers keep ingestion from blocking chat. Re-index when documents change.
03 / Retrieval
Vector similarity finds chunks that look like your question. Graph traversal finds related entities and their connections — people, projects, dates, concepts. Both paths run on every query and their results are merged for richer context.
Retrieval paths
vector path
query → embeddings → top-k chunks
4 chunks · avg relevance 0.87
graph path
entities extracted → graph traversal
related nodes → additional context
+3 nodes · 2 hop depth
Org structure
owner alice@acme.com
admin bob@acme.com
member carol@acme.com
member dave@acme.com
12 documents · 847 chunks indexed
last activity · runbook.md uploaded · 2h ago
04 / Workspace
Organisations, members, and roles. Each workspace is isolated — documents, chat history, and settings belong to the organisation, not individual users. Invite members, manage access, and control who can upload or delete documents.
05 / Trust
Every answer shows which passages supported it so teams can verify claims. Workspace roles and invites keep knowledge inside the right group; document uploads are scoped to your organisation.
Answer trace
question → SLA for enterprise support?
↳ support-policy.md · §2 (cited in answer)
↳ customer-handbook.md · §4.1 (cited in answer)
recent uploads
alice@acme.com · playbook.md · indexed
bob@acme.com · faq.txt · embedding…
Workspace snapshot
ingestion queue
policy-update.md · chunking
onboarding.md · complete
06 / Activity
See how many sources are in your workspace, follow ingestion as new text lands, and understand how plan limits apply. Grounded answers stay tied to what you've actually indexed.
Roadmap
In development
PDF, DOCX, and image ingestion with OCR so slides, contracts, and scans join your knowledge base without manual paste.
In development
Drop search and chat into internal portals and tools so teams stay inside the systems they already use.
In development
Automate uploads, queries, and integrations with documented APIs and scoped credentials for builders.
Ready to see these features in action?