Lore brings together your runbooks, procedures, architecture documents and incident reports. Import them, find the right passage in seconds, track their versions and decide exactly who can read them.
docker compose up -dIn most teams, technical knowledge is scattered: a wiki nobody updates anymore, a network share, Markdown files in repositories, incident reports in tickets and, above all, the memory of a few experts.
When something breaks, nobody knows which version to trust.
Search understands technical identifiers, ignores accents and opens the document at the exact passage.
Every document has a status, an owner and a version history. An outdated procedure is flagged as such.
Lessons learned become approved records that stay available when people change roles.
Library, search, versions, permissions and knowledge base share the same documents, the same permissions and the same history.
Spaces, folders and documents in a grid you can filter, sort and group. PDF, Word, text and Markdown are indexed on import.
| Title | Status | Category | Owner | Updated |
|---|---|---|---|---|
| Restore a PostgreSQL database from a backup | Published | Runbook | Yesterday | |
| Incident INC-2291: disk full on pg-prod-02 | Published | Incident report | Nov 3 | |
| Rotating internal TLS certificates | Draft | Security | Oct 29 | |
| Nightly backups with Barman | Outdated | Runbook | Mar 2 |
Technical identifiers are found exactly as typed, and every result opens the document at the right passage.
… if pg_restore reports role "app_rw" does not exist, create the role and run it again …
… the restore fails with pg_restore: error: role "reporting" does not exist …
Every import creates a version. The history stays available, stratum after stratum.
The thickness of a stratum shows how much changed.
A restricted document appears nowhere for people without access: not in lists, not in search, not in excerpts.
An investigation or a resolved incident becomes a structured record, approved by the owners.
Natural-language answers, always sourced, that only read what you are allowed to read.
Lore installs on your server in under five minutes, with Docker, a .deb or .rpm package, or an archive. PostgreSQL is its only dependency: no message queue, no cache, no authentication service to maintain.
pg_dump command and a copy of the files folder.# 1. Download the starter file
curl -LO https://github.com/dada-core/lore/releases/latest/download/docker-compose.yml
# 2. Choose the database password
echo "DB_PASSWORD=$(openssl rand -base64 24)" > .env
# 3. Start both containers
docker compose up -d
# Lore answers on http://localhost:8080# Ubuntu and Debian
sudo apt install ./lore_0.1.0_amd64.deb
# RHEL, Rocky Linux and AlmaLinux
sudo dnf install ./lore-0.1.0-1.x86_64.rpm
# Then, once the database and /etc/lore/lore.env are ready
sudo systemctl enable --now loreLore is open source, under the AGPL-3.0 license, and free: no limit on users or documents. You can audit it, host it yourself and adapt it, without depending on a vendor.
No. Lore is not a chatbot: the library, search, versions, permissions and knowledge base work without any language model. The conversational assistant is an optional module, planned for v0.3 and off by default.
Nothing. The Community edition is free and complete, with no limit on time, users or documents. A hosted offer, with managed updates and backups, is being considered after version 0.1.
PDF, Word (DOCX), plain text and Markdown from v0.1, up to 50 MB per file by default. Scanned PDFs are imported, but their content cannot be searched until text recognition is available.
On your server: in PostgreSQL and in a files folder. Nothing leaves your infrastructure.
Version 0.1 is in progress. It will cover accounts, spaces, permissions, import, the viewer, search and versions.
Accounts, invitations and administration already work. Spaces, import, search and versions are coming. Try the demo, and follow the project on GitHub.