qarunbook vs WeKnora: Features, Pricing & Which Is Better (2026)
A side-by-side comparison of qarunbook and WeKnora — features, pricing, and ideal use cases — to help you decide which AI tool fits your workflow.
qarunbook
qarunbook
qarunbook is an app testing runbook where AI drafts a test plan from your code and your team or AI works through it, tracking issues and retests.
Key features
- AI-Drafted Test Plans: The /test-checklist skill looks through your app and drafts checks with steps and expected results already filled in.
- MCP Connection: Connect Claude Code, Claude Desktop, Codex, Cursor or any MCP client so the assistant can read the plan and record results.
- Issue-to-Check Linking: Every issue sits on the check that found it with the affected platforms, and raising one removes the pass.
- Retest Flow: When an issue is fixed the check waits for someone to look again before being marked passed.
- Roles and Join Links: Give people access to only the projects they need and invite whole groups with a join link.
- Multi-App Workspaces: Keep each app's sections and platforms separate so web, driver and marketing sites are tested side by side.
- GitHub and Linear Integration: Connect issue trackers so problems found in testing flow into existing engineering workflows.
- QA Runbook Skill: The /qa-runbook skill works through the plan on web and mobile, recording each result and re-checking fixes.
Best for
- Release Testing: Run a structured test plan before each release across web, Android and iOS.
- AI-Assisted QA: Let a coding assistant execute checks and record pass/fail results through MCP.
- Team Test Coordination: Split test checklists among teammates and see progress and results in one workspace.
- Regression Follow-up: Track bugs against specific checks and retest them after fixes ship.
- Solo Developer Testing: Generate a test plan from the codebase so a one-person team knows what to check.
- Agency Multi-Client QA: Manage separate apps and clients with scoped access and a flat workspace price.
WeKnora
Tencent
Tencent's open-source LLM knowledge framework turning documents into a RAG-queryable, agent-reasoned, self-maintaining wiki.
Key features
- RAG Quick Q&A: Semantic retrieval over ingested documents for everyday lookups, with editable retrieval chunks that support per-version diff, rollback and automatic reindexing.
- ReAct Agent Orchestration: An autonomous agent that plans across retrieval, MCP tools, a per-tenant skill catalog, sandboxes and web search to resolve complex multi-step questions.
- Wiki Mode: Agents distil raw uploads into a self-maintaining, interlinked markdown knowledge base with an interactive knowledge graph, in-browser editing, line-level diffs and one-click rollback.
- Skill Sandbox Runtime: Session-persistent Docker, E2B and Cube sandbox backends with per-tenant network policy, skill installation from ClawHub, SkillHub, git or zip, snapshots and live progress.
- Cross-Session Long-Term Memory: Profile, preference, fact, task and interest memory extracted automatically with user confirmation and searchable across sessions.
- Multi-Source Ingestion: Auto-syncing knowledge from Feishu Wiki and Drive, GitLab, Tencent IMA, Notion, Yuque, DingTalk Docs and RSS, with 10+ document formats including PDF, Word, Excel, images and XMind.
- Swappable Provider Stack: 20+ LLM providers including OpenAI, DeepSeek, Qwen, Zhipu, Hunyuan, Gemini, MiniMax, NVIDIA, LiteLLM and Ollama, with interchangeable vector databases and storage backends per workspace.
- Enterprise Multi-Workspace RBAC: A four-tier role matrix with per-resource ownership, per-workspace audit logs, scoped API keys with a principal model, OIDC JWKS verification and Langfuse OTel tracing.
Best for
- Internal Knowledge Base: Turning scattered company documents into a queryable wiki that agents keep current instead of a folder of stale files.
- Data-Sovereign Deployment: Running a full RAG and agent stack on private cloud or local infrastructure where documents cannot leave the network.
- IM-Channel Support Bot: Serving grounded answers from company documents directly inside WeCom, Feishu, Slack or Telegram.
- Multi-Source Documentation Sync: Keeping a single searchable index over Notion, GitLab, Feishu and Yuque content that syncs automatically as sources change.
- Retrieval Quality Tuning: Editing, diffing and reverting individual retrieval chunks in the UI to fix bad answers without rebuilding the whole index.
- Agent Pipeline Observability: Using Langfuse tracing and the runtime task queue dashboard to see agent reasoning, token usage and worker pool behaviour in production.
- Embedded Public Agents: Publishing a knowledge agent to an external website through embed widgets and scoped API keys.