An open foundation, so you stay in control.
Lore’s code is published under the AGPL-3.0 license. The Community edition is free and complete: you can audit it, host it and adapt it, without depending on a vendor.
License and contributions
The AGPL-3.0 license
- Use Lore for free, without limits.
- Study and modify the code.
- Host it for your organization.
- If you modify Lore and offer it as a service to others, give its users access to the source code of your version.
The contributor agreement
Before your first contribution, you will sign a contributor license agreement (CLA) based on the Apache Software Foundation’s; its text will be published before the first outside contribution. You will keep ownership of your code; the agreement will let the project also distribute it under other licenses, which funds its development.
Free and complete.
The Community edition has no limit on time, users or documents, and no essential feature held back. A hosted offer is being considered after version 0.1, for teams that do not want to run a server.
What does the AGPL-3.0 license mean for my company?
You can use, modify and host Lore freely, for your teams. If you modify Lore and offer it as a service to others, you must give its users access to the source code of your version. If this obligation does not suit you, write to us: a commercial license is possible.
Are my documents used to train models?
No. The assistant, planned for v0.3, is off by default. Once enabled, only the passages needed for an answer are sent to the model chosen by your organization, and only those the person is allowed to read.
Contribute
The project is just getting started: feedback on its direction is the most useful contribution today.
Share your feedback
Where does your team’s documentation live, and how do you search it? Start a discussion.
Start a discussionImprove the documentation
An unclear or incomplete page? The documentation is edited on GitHub, just like the code.
Contribute to the documentationTranslate
The interface is translatable from the start, beginning with French and English.
Planned releases
Each release must be useful on its own. The assistant comes last, once the foundation is solid.
Accounts, organizations, spaces, permissions, PDF, Word, text and Markdown import, viewer, permission-aware full-text search, versions.
Search by meaning, knowledge records, dashboard, review dates and approval workflow.
Optional assistant and conversation history.
Write to us
A question about the project, an interested organization, a partnership: write to us. For a technical question, the documentation and GitHub Discussions are often faster.
Tell us about your organization, the size of your technical team and where your documentation lives today.
Send an email