Your data
Lore is software you run, not a service you send things to. Your entries live in its database on your computer or your team's server, and each assistant gets only the passages its task needs.
The screenshots are the real app on made-up data: its people, areas and groups are samples.
Where it runs
The same server runs inside an app for one person, or on machines your team runs for everyone.
One app with everything included: its own database, the server, its three local models and the lore command. No Docker, no terminal.
The same server as a container image: a compose file to try it on one machine, a Helm chart for Kubernetes with several replicas.
What leaves it
A brief holds the few passages that answer the task, within the token budget it asks for. Searching, embedding and ranking run on Lore's own local models.
Ask answers from approved entries with the model you set: an open model on your own machine, or a provider such as Claude. It sends what the question needs.
Events go out only where you point them: webhooks, or Kafka and RabbitMQ with the optional plugin, for approved entries, open questions and freshness changes.
Who reads what
Who may read, write and review each area, by person, team, sign-in group or everyone. The rules hold for the app, Ask and every assistant alike.
Slack, Jira, Confluence, Google Drive, Notion and Linear, mirrored read-only and searched like the team's own entries, with access following who may read them at the source.
Several installations searched as one, each answer marked with where it came from. Nothing is copied, and each Lore decides what it returns.
Export, import and backups, and upgrades Lore runs itself.
Settings
Providers lists what Lore talks to, each with its status: who may sign in, where people and teams come from, the sources it mirrors, where approved knowledge is published, where the weekly digest goes, who writes Ask's answers, and the other Lores it searches.
A provider is added in the app, with a test of its connection before it is saved, or comes from the configuration file. Each says which, and one from the file can be taken over in the app.
Pick who writes Ask's answers by name, Claude first, or a model on your own machine. Each says what it may do with what it is sent.
A key given in the app is sealed and never shown again. A reference to an environment variable or a file works too.
Kept safe
A release does not tag unless every gate passes.
lore connect backs up every file before it changes it and keeps the token in the system's keychain, never in a file. The desktop app treats its own page as untrusted.