Frequently Asked Questions

Usage Instructions

This page compiles common questions and answers from community discussions. If you encounter any issues not covered here or discover a bug, please feel free to submit an Issue. We will address it promptly and continuously improve the platform.

❓ What core features does qKnow support?

Answer: qKnow supports knowledge categorization, file management, structured and unstructured data extraction, concept and relationship configuration, knowledge graph construction, and visual exploration. Advanced features such as question answering, reasoning, and knowledge fusion will be continuously added.

❓ Is qKnow open-source? Can it be used commercially for free?

Answer: Yes, qKnow is fully open-source under the MIT license and can be freely used in commercial projects. We also offer a commercial enhanced edition—please contact us for more information.

❓ What environment is required to deploy qKnow?

Answer: The backend requires JDK 8+, Maven, MySQL, Neo4j, Redis, etc. The frontend is built on Vue3 and Vite, and can be locally built or served via the built-in page server (port 80). Linux or Windows Server environments are recommended for deployment.

❓ How can I get started with qKnow quickly?

Answer: We provide detailed installation and user manuals, available on both GitHub and Gitee. After launching the service, access http://localhost:8080. The default login credentials are: username qKnow, password qKnow123.

❓ What types of data extraction are supported?

Answer: Currently, qKnow supports knowledge extraction from structured sources (e.g., databases) and unstructured sources (e.g., PDFs, Word documents, plain text). Support for additional sources such as web pages, APIs, and multilingual data will be added in the future.

❓ Does the graph visualization support interactive operations?

Answer: Yes, the knowledge graph supports interactive operations including drag-and-drop, zooming, node search, relationship filtering, and detailed information viewing, helping users intuitively explore the knowledge network.

❓ Can qKnow integrate with large language models (LLMs)?

Answer: Yes. qKnow supports integration with LLMs (such as ChatGPT, Qwen, etc.) to enable semantic-enhanced question answering, reasoning, and natural language interfaces using your knowledge graph.

❓ Does qKnow support permission management and multi-user collaboration?

Answer: Yes. qKnow provides user, role, organizational structure, and permission configuration, meeting enterprise-level needs for team collaboration, access control, and audit logging.

❓ Can qKnow be customized or integrated into existing systems?

Answer: Absolutely. qKnow uses a frontend-backend separation architecture with open APIs and clean code, supporting flexible customization and system integration. We also offer integration services.

❓ Are there community groups or contact methods?

Answer: You are welcome to join our official QQ group (scan the QR code at the bottom-right of the page), or contact us via Gitee/GitHub issues, email, etc. We will respond to your inquiries as soon as possible.

❓ How can I contribute or report issues?

Answer: You can submit Issues or Pull Requests (PRs) via the GitHub or Gitee repository. We also welcome you to join our community group to discuss and collaborate.

❓ Are the features in the Gitee and GitHub repositories the same as the demo environment after local deployment? Thank you!

Answer: Yes, the code in the open-source repositories matches the functionality of the demo environment. After local deployment, you can experience the full feature set. If you encounter environment-related issues, please report them via an Issue.

❓ Are some features not yet completed? I noticed some modules are labeled as "In Development".

Answer: Yes, qKnow is currently under continuous iteration. Some features are still being developed and optimized, and will be gradually released in future open-source versions—stay tuned!

❓ I couldn't find some common features in the system. Are they not implemented yet?

Answer: Some features may still be under development, or might not be in the current roadmap. If you have suggestions or specific requirements, we warmly welcome you to submit them via the Feature Request form. We will carefully evaluate them and prioritize features with broad applicability for future releases.