Ask your company why.
KnowWhy connects GitHub, Slack and Notion into one searchable knowledge base. Ask why a decision was made or what shipped last week — and get a straight answer that cites the commit, thread or page it came from.
Free plan · Read-only access · You choose what gets indexed
Example: asked “Why did we move card capture to a hosted checkout?”, KnowWhy answers in plain language with numbered citations to Payments decision record, #payments thread, #482 Hosted checkout.
One answer, drawn from where the work actually happens
On the roadmap: GitLab, Jira, Linear, Confluence, Google Drive, Google Meet transcripts, Microsoft Teams, SharePoint, Zoom, Sentry, Zendesk, Intercom.
The problem
Knowledge is scattered. The context behind it disappears.
Decisions are argued in Slack, implemented in GitHub and written up — sometimes — in Notion. KnowWhy brings them together so the next person doesn't have to dig.
Answers you can verify, line by line.
Every claim carries a numbered citation. Click it to read the exact excerpt, then jump to the original commit, thread or page. Citations that don't map to real evidence are stripped before you ever see them.
Card capture moved to a hosted checkout after mobile 3-D Secure failures1, agreed in #payments2.
Understands “last week”
Relative dates resolve in your organization's time zone, and the searched range is shown above every answer.
Meetings, next
Transcripts are on the roadmap. Today, notes captured in Notion or Slack are fully searchable.
Engineering
Commits, pull requests, reviews and issues — who changed what, when, and the reasoning in the description and review thread.
Communication
The Slack discussions where decisions actually happen, kept together with their thread replies.
Documentation
Specs, decision records and meeting notes in Notion, with page history and links back to the source.
How it works
From scattered tools to a straight answer in three steps.
- 01
Connect your tools
Install the GitHub App, add KnowWhy to Slack, or share pages from Notion. You choose exactly which repositories, channels and pages are indexed.
read-only · least privilege - 02
KnowWhy indexes in the background
Content is normalized, chunked and embedded incrementally. Edits and deletions are picked up through webhooks and scheduled syncs — deselect a source and it leaves retrieval immediately.
acme/api · pull requests#payments · threadsEngineering wiki · pages - 03
Ask in plain language
Get a concise answer with numbered citations. Click any citation to see the excerpt and open the original commit, thread or page. If your sources don't say, KnowWhy says so.
“The retry loop was removed in #4823after the team agreed in #payments2…”
3
tools, one answer
GitHub, Slack and Notion searched together
90 days
of GitHub history
indexed by default, configurable per connection
256-bit
AES-GCM encryption
for every stored integration credential
0
Slack DMs read
direct messages are never accessed
Integrations
Plugged into the tools you already use.
Connected with OAuth and least-privilege, read-only permissions. You pick every repository, channel and page.
GitHub
Commits, pull requests, reviews and issues
Index repository activity so KnowWhy can answer who changed what, when, and why — with links back to the exact commit, pull request or issue.
Slack
Channel discussions and threads
Index the channels you choose so KnowWhy can find the discussion behind a decision, including thread replies, with links to the original messages.
Notion
Pages, docs and decisions
Index the Notion pages shared with KnowWhy so answers can cite specs, meeting notes and decision records, with links back to each page.
Planned: GitLab, Jira, Linear, Confluence, Google Drive, Google Meet transcripts, Microsoft Teams, SharePoint, Zoom, Sentry, Zendesk, Intercom.
Security
Built for confidential information.
Treat every connected source as confidential — so we do too. Here is how KnowWhy is designed.
Isolation in the database
Every record carries its organization, and PostgreSQL row-level security enforces tenant boundaries — not just application code.
Source-level access
Workspace membership doesn't unlock everything. Private repositories, channels and pages stay restricted until an admin grants access.
Encrypted credentials
Integration tokens are encrypted with AES-256-GCM using keys kept outside the database, and are never sent to the browser.
Answers you can verify
Citations map to real indexed sources the asker is allowed to see. When the sources don't contain an answer, KnowWhy says so.
Least-privilege integrations
Read-only permissions, minimal scopes and revocation on disconnect. We document exactly what each integration can access.
Audited administration
Connections, role changes and access grants are recorded in an audit log available to owners and admins.
Stop searching five tools for one answer.
Create a workspace, connect your first tool and ask your first question in minutes.