The useful detail is in the repository
The product description may be in Confluence, while the current behavior or exception is already documented in a README or another Markdown file.
Company-wide search with cited sources
Search company knowledge. Open the source behind every answer.
Krynia is being built for company-wide knowledge search with source-grounded answers. The current release starts with one public GitHub repository or bounded Markdown, MDX, text and CSV uploads; after indexing, ask in your own words and open the exact source your team can verify.
One public GitHub repository Markdown, MDX, text and CSV Answers with source links No charge per teammate Runs on Cloudflare infrastructure
Current supported scope
One public GitHub repository or bounded Markdown, MDX, text and CSV uploads, with workspace-shared access and source links.
Not a fit yet
Not a fit yet if you need private repositories or provider-authorized sources. The current release is limited to one public GitHub repository or bounded uploads.
The problem
The answer exists, but nobody knows which source is current.
A team may remember the decision but not the filename, heading or exact wording. A wiki can return a long page while the current explanation is already in the repository documentation you added.
Documentation falls behind the work
The familiar page stays the first place people search even after the useful explanation has been updated somewhere else.
Search returns a page, not the answer
Even the right long document still has to be read. What you need is a short result and a source link you can check.
Chat-first company memory
Answers stay tied to source context.
Krynia keeps chat simple for the team while admins can review the material used, the relationship map, the connected sources and monthly knowledge usage behind every answer.
Source summaries keep answers concise without exposing raw internal documents.
Admins can review sources and graph links before trusting or correcting an answer.
Pricing stays tied to retained indexed knowledge, not seats.
Use cases
Chat is the main UI, but every answer stays tied to sources.
Product, support, engineering and onboarding teams can ask normal questions and still get answers they can verify.
Product and support
Find product context
"What is this product and where is the source?"
Short answer with citations to docs, repositories and decisions.
Engineering
Trace dependencies
"What depends on this service, package or feature?"
Evidence from repositories, tickets, docs and graph links.
People and team leads
Onboard new people
"What should a new teammate read first?"
A scoped reading path based on real company sources.
Founders and managers
Recover decisions
"When did we decide this and why?"
Timeline-style answer grounded in PRs, issues, docs and chats.
Workspace admins
Admin visibility
"What are people searching for and what is missing?"
Topic groups, failed searches, source gaps and traceable citations.
Everyone
Meeting prep
"What context do I need before this discussion?"
KB-first briefing now; calendar-aware preparation can follow later.
Pricing
Pricing people can understand before they connect a single source.
Krynia bills the knowledge still kept at billing close. Regular sync, storage, citations and normal chat are already part of the base product.
Meter
€0.47
per 1M indexed tokens
Minimum
€47.00
product plus 5M indexed tokens
Included
5M
about 7.7k A4 pages
Why the minimum is EUR 47
The monthly base includes product access, sync, citations and the first 5M indexed tokens. Overage starts only after that included volume.
No seat-based tax for quiet users.
Deleted or stale chunks removed before billing close do not count.