The whole lifecycle of your technical knowledge.
Write, import, organize, search, approve and maintain: every module shares the same documents, the same permissions and the same history.
Library v0.1
The foundation of Lore: spaces for each team or domain, folders, and documents you import, read and download.
- Import PDF, Word, text and Markdown files, up to 50 MB
- Grid and kanban views, filters, sorting and grouping
- Built-in viewer that opens at the right passage from search
- Metadata: category, owner, language, status
| 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 |
Search v0.1
Full-text search designed for technical documentation, which strictly respects everyone’s permissions.
- Technical identifiers found exactly as typed
- Accents and plurals handled, in French and English
- Highlighted excerpts and a direct link to the passage
- Search by meaning, on top of keywords, in v0.2
… 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 …
Permissions v0.1
Permissions are enforced in every query, before sorting and pagination: nothing leaks, not a title, not an excerpt, not a result count.
- Space roles: reader, contributor, owner
- Documents restricted to a few people
- An inaccessible document cannot be found, in the strictest sense
- The same rules for search and for the assistant
- Restore a PostgreSQL database
- Incident INC-2291
- Migration to PostgreSQL 18
- Restore a PostgreSQL database
- Incident INC-2291
- Migration to PostgreSQL 18
- Rotating TLS certificates
Versions and governance v0.1
Know which version is authoritative, who owns it, and since when.
- Every import creates a version you can open
- Statuses: draft, published, outdated, archived
- Audit log of sensitive operations
- Review dates and an approval workflow in v0.2
The thickness of a stratum shows how much changed.
Knowledge base v0.2
Turn an investigation or a resolved incident into a reusable record: problem, symptoms, causes, fix and precautions.
- Structured records, linked to their source documents
- Approval by the space owners
- Created from a document, an incident or an assistant answer
- Problem
- pg_restore fails: the role does not exist on the target server
- Cause
- The grants refer to a role deleted during a cleanup.
- Fix
- Recreate the role, then run the restore again.
- Sources
- Restore runbook, incident INC-2291
Insights v0.2
See what gets read, what is getting old and what is missing.
- Most-read documents
- Overdue reviews and outdated documents still being read
- Searches with no results: the gaps in your documentation
Assistant v0.3
An optional way in, in natural language, that goes through search and inherits its permissions.
- Sourced answers: document, version and passage
- Outdated documents excluded from answers
- Can be turned off at any time, with the model your organization chooses
Connected sources Later
Index documentation where it already lives, without migrating everything.
- Markdown files from GitHub and GitLab repositories
- Your organization’s shared folders
- Confluence, SharePoint, Google Drive and OneDrive, with their permissions
- SyncedGitLab: infra/runbooks42 Markdown files, into Infrastructure
- 3 unreadable filesShared folder: nas011,203 files, into Tier 2 support
- PlannedConfluenceWith its permissions
Lore is on its way to version 0.1.
Accounts, invitations and administration already work. Spaces, import, search and versions are coming. Try the demo, and follow the project on GitHub.