Privacy-first by default
The working point is a local documents folder on your own machine.
LocalRAG is built for the folders people actually keep: PDFs after OCR, mixed formats, multiple languages, and notes that do not belong in a public cloud.
The working point is a local documents folder on your own machine.
The answer is more useful when you can inspect the source context instead of trusting a polished paragraph.
UI language and answer language are separate controls. That matters when the folder itself is mixed-language.
Models, embeddings, and response roles stay in the interface instead of being hidden in setup files.
The current build makes folder path, answer language, retrieval behavior, roles, models, and retrieved context visible in the UI.
The interface currently ships with English, Russian, Dutch, Chinese, and Hebrew. Inside the app, answer language is configured separately.
Everything in this gallery comes from the current LocalRAG build.
Notes, specs, meeting exports, and internal docs that should stay on your own machine.
One folder, several languages, inconsistent filenames, and still a need for a readable answer with evidence.
The supporting fragment matters as much as the answer when you are checking a clause, note, or claim.
LocalRAG is free for individual use, evaluation, and local-first workflows. Corporate work starts when the team needs connectors, enterprise integrations, and operational guarantees around a private deployment.
The public version is designed for personal workflows, technical evaluation, and community-driven use around private folders.
Corporate deployments can extend the same local-first core with enterprise connectors, API surfaces, and integration patterns for internal platforms.
The site is the product-facing layer. GitHub is where the code, release context, and technical history live.