WeKnora

Use WeKnora when your task is grounded in a collection of documents rather than a general model’s memory. The repository describes document, FAQ and Wiki knowledge-base workflows as well as agents and integrations. You do not need to activate every available service to evaluate a single-document question. Official overview.

Choose a source that has an unambiguous answer, such as a short internal-style test policy containing a date, a named owner and a numeric threshold. Keep it synthetic or public for the trial. Ask both an answerable question and one the document cannot support.

The official quick start requires Git, Docker and Docker Compose. Its shell sequence is:

git clone https://github.com/Tencent/WeKnora.git
cd WeKnora
cp .env.example .env

Edit .env for the intended environment before starting. Do not commit credentials. Review the configuration guide, especially model endpoints and embeddings. Then the documented core launch is:

docker compose pull
docker compose up -d

The README directs you to http://localhost after startup. Use your deployment’s actual host mapping if you changed it. The commands are presented for a compatible shell; on a different shell, use its normal file-copy operation for .env.

Confirm the path to an answer

1. The application and required services are reachable.
2. The intended model configuration works.
3. The uploaded document finishes parsing.
4. Retrieval finds the passage containing your known answer.
5. The response cites that passage.

If parsing failed, changing the wording of the question will not repair the missing source. If retrieval succeeded but the answer is wrong, preserve the retrieved passage and response when diagnosing it.

Create a tiny test document containing: “Trial support hours are 09:00–17:00 UTC on weekdays. The escalation owner is the Example Operations Team.” After uploading it and confirming parsing, use this editorial prompt:

Use only the selected test document.
What are the trial support hours and who owns escalations?
Cite the exact supporting passage.
Then tell me whether this document specifies a weekend response time.
If it does not, state that the document does not provide that information.
Do not use web search or infer a service commitment from other sources.

The first answer should match the document’s hours, timezone and owner. The second should identify the missing weekend information rather than inventing a promise. Open the cited passage and confirm that the citation points to the uploaded file, not an unrelated source.

This is a small retrieval check, not a benchmark. Before connecting real knowledge sources, also test the access permissions and update behavior required by your team.

The README describes model, storage and retrieval integrations. A locally deployed application can still send content to the external providers you configure. Inspect those routes before importing sensitive files.

Generated Wiki pages and fluent answers still need source verification. Keep original documents available so you can resolve stale, unsupported or conflicting statements. A citation label alone does not prove that a passage supports the answer.

The documented stop command is docker compose down. Do not append destructive volume-removal flags as routine cleanup. Stopping services is separate from deleting data, revoking provider credentials or removing copies held by an external service.

For upgrades, the README distinguishes pulling the selected images from recreating containers. Preserve data and follow the project’s release-specific upgrade instructions; this guide has not tested a production migration.