WeKnora: review, pricing, security and alternatives

What WeKnora does

WeKnora belongs to the data and rag family: agents that query databases and company documents to answer questions or produce analyses. On our grid it ranks #6 of the 15 projects of this family listed in the directory.

You use it from: web app and API. Usable models: GPT (OpenAI) and local models (Ollama, llama.cpp, vLLM…). It can run on your own machine or server.

Who is WeKnora for?

It is for teams that want an AI to answer from their own documents or databases. Typical tasks people give it:

• query internal documentation in plain language
• ask a database questions without SQL
• index and summarise large file collections

It is a good candidate if you prefer doing everything in a browser, with no install, your data must stay on your machines, and you want the option of a local model, with no API fees.

Access and human control

Its documentation does not detail the access granted to the agent: check the settings before connecting it to your accounts.

We could not establish whether it asks for human approval before sensitive actions: test it first on an unimportant account or folder.

WeKnora pricing

The code is public but the repository declares no licence: reuse is not formally allowed. The real cost comes from model calls: each loop step sends the whole context back to the model, and a task of several dozen steps can cost far more than a single question. The LLM price calculator estimates it for the chosen model.

Getting started with WeKnora

1. Install it: the project ships as a single Go binary, downloadable from the repository releases. The exact command is in the repository README.
2. Pick the model: an API key from a provider, or a local model if your machine has enough graphics memory (the VRAM calculator tells you).
3. Give it a first playground with nothing at stake: a test folder, a secondary account or a throwaway project. Only open your real accounts once you have seen how it behaves.
4. Give it a short, checkable task, review the result and its action log, then raise the difficulty step by step.

Security: risk level

Give it read-only access and check generated queries before any data change.

Points found for WeKnora:

• No licence: legally shaky for company use.

Three habits: least privilege (minimal rights, dedicated keys), human approval for irreversible actions, a sandbox for code execution. The AI agent security check reviews your setup in a few minutes.

Project activity and releases

Created on July 22, 2025, the Tencent/WeKnora repository has 35,297 stars, 4,748 forks and 419 open issues, with 3,637 commits in total. It received changes this month.

Over the last 52 weeks: 3,414 commits, an average of 65.7 per week.

41 releases in total; 30 in the last twelve months. Latest release: v0.8.3, on October 14, 2026.

WeKnora vs other data and rag

GitHub stars of the best-rated open-source projects in the data and rag family. Stars measure attention, not quality: a heavily promoted project collects them fast, a specialised tool will have few.

WeKnora and other data and rag at a glance

The 7 best-ranked agents in the same family, 7 of them open source. The score out of 100 only applies to open-source projects; for proprietary services we show the published entry price. A dash marks information the documentation does not state.

How we rated it

Score: 76/100, computed only from public, verifiable data, with no subjective testing or partnership:

• Adoption 31/40: 35,297 stars on a log scale (40 points from about 200,000).
• Activity 30/30: last commit less than a month ago, 13 releases in six months, 3,414 commits in a year.
• Framework 15/30: licence, default human approval, self-hosting, model choice and documentation site.

The score does not say whether the agent will succeed at your tasks: it measures how solid the project is. The full grid is on the method page.