Kora
Knowledge Orchestration & Retrieval Assistant
Your team asks a question where they already work. Kora answers from your own documents, cites what it used, and says so plainly when the answer is not there.
The answer already exists. Nobody can find it.
It is in a PDF somebody wrote two years ago, or on a page of the site nobody reads, or in a document three folders deep. So instead of finding it, people interrupt the one colleague who remembers.
Search does not help, because search matches words and questions are asked in different words than the answer was written in.
Where the question gets asked
Answers where you work
Mention Kora in Slack or Teams, or use a slash command in Discord. It replies where you asked, so the answer stays with the question.
Shows its sources
Every answer links the documents it used. If something looks wrong, you open the source and usually find the document itself is out of date.
Follows the conversation
Reply in the thread and it keeps the context. "What about digital goods?" resolves against what was already asked.
Ana 9:14
@kora how long is the refund window?
Kora APP 9:14
30 days from the date of purchase, refunded to the original payment method, and it takes 5 to 7 business days to appear [1].
Digital goods are non refundable once downloaded [1].
Sources
1 Support Handbook — Refunds, Exceptions
Ana 9:15
what about enterprise contracts?
Kora 9:15
Those override the standard policy entirely and are governed by their own terms [1].
Illustration of a Kora answer. The follow-up carries no subject of its own; Kora resolves it against the thread before searching.
It tells you when it does not know
Most assistants answer confidently either way, which means you cannot tell the reliable answers from the invented ones. Kora scores every passage it finds and throws away anything below the line.
“How long is the refund window?”
relevance
- Refunds and returns0.926
- Exceptions and edge cases0.359
- Service credits0.305
- Escalation policy0.248
- Support hours0.231
Two passages cleared the line, so those went to the model and the answer cites them. The other three were discarded. When nothing clears it, Kora replies that it could not find the answer and never asks the model at all.
Set up once, then forget about it
Add what it should know
Connect Confluence, Jira, Zendesk or Guru, upload documents, or point it at a website. An upload is searchable within seconds; a connection or crawl runs in the background and keeps itself up to date.
Connect your chat
Slack, Microsoft Teams, Discord or your own Mattermost server. Channels can be pointed at different knowledge bases, so each team gets answers from the right place.
Ask
Anyone on the team asks in plain language. No syntax, no keywords, no training.
Watch the gaps
Questions it could not answer are logged. That list is the best content backlog you will get, written by the people who needed something.
Indexed sources re-check themselves every day, so a page you edit is reflected without anyone remembering to press a button.
See what it retrieved, not just what it said
Test any question and inspect the passages behind the answer. When something is wrong, this tells you whether the content is missing or the document is stale.
Your own space, not a shared one
Your own workspace
Your knowledge bases, your chat connections, your API keys. Other clients on the same installation cannot see any of it.
Your own people
Add colleagues as editors who curate content, or administrators who also manage settings. Roles are per workspace.
A web interface
Upload and reindex content, test questions and see exactly which passages were retrieved and how they scored.
An API
Authenticated endpoints so your other applications can ask the same questions and push in new content.
Connects to where your knowledge already lives
Point Kora at the systems your team already writes in. It reads only the spaces, projects and collections you pick, and re-reads them as they change.
Confluence
Spaces you choose, page by page
Jira
Issues and their comments
Zendesk
Published help centre articles
Guru
Cards, by collection
And answers where people ask
Slack
Mention Kora in a channel or thread
Microsoft Teams
Mention Kora in a channel
Discord
Ask with a /kora slash command
Mattermost
Your own server, self-hosted
Uploads and website crawls work the same way, with no connection to set up.
Confluence, Jira and Atlassian are trademarks of Atlassian Pty Ltd. Zendesk is a trademark of Zendesk, Inc. Guru is a trademark of Guru Technologies, Inc. Slack is a trademark of Slack Technologies, LLC, a Salesforce company. Microsoft Teams is a trademark of Microsoft Corporation. Discord is a trademark of Discord Inc. Mattermost is a trademark of Mattermost, Inc. All product names, logos and brands are the property of their respective owners and are used here only to identify the services Kora can connect to. Lunixa does not own these marks and is not affiliated with, endorsed by, or sponsored by any of these companies.
What it can read
- Word documents
- Markdown
- Plain text
- CSV and JSON
- Your website
Website crawling stays on your own domain, respects robots.txt, and strips navigation and footers so they do not pollute the answers.
Handled carefully
- Your content is separated from every other client at the data layer, not just hidden in the interface.
- Uploaded documents are never reachable from the public internet.
- Credentials Kora holds on your behalf, such as its chat bot tokens, are encrypted where they are stored.
- Kora only answers from what you gave it, so it cannot leak something it was never shown.
Five people or five hundred
The same Kora throughout. What changes is how much you point it at.
A small team
One knowledge base and one channel. Upload the handbook, point it at your website, and it is answering the same afternoon.
A growing team
A knowledge base per area, with each channel pointed at the right one so answers stay relevant. Editors curate the content without being able to change settings.
A larger organization
As many knowledge bases as you need, administrators kept separate from editors, and an API so your own systems can ask the same questions. The question log shows where the content is thin.
Nothing to migrate as you grow, and no capability held back for a bigger plan. Tell us what your team needs and we will price it to that.
Put it in front of your team
Tell us what your team keeps asking each other, and we will show you Kora answering it from your own documents.
Slack is a trademark and service mark of Slack Technologies, Inc., registered in the U.S. and in other countries. Kora and Lunixa are not affiliated with, endorsed by, or sponsored by Slack Technologies, Inc. or Salesforce, Inc.