Always on
AI does the upkeep.
Structure messy docs, flag conflicts, and surface knowledge that needs attention.
A new home for your knowledge.
For teams considering a move from Guru
Your knowledge.
A new home.
More possibilities.
AI-native knowledge, connected to your work. Cited answers with sources and context.
Knowledge card · example
One answer. The context behind it.
A living home for the policies, processes, and expertise your team comes back to. Organized in collections, connected to the people who know.
Owned knowledge. A source you can trace.
Meet NuHQ Knowledge
Knowledge that keeps itself current.
AI-native from the start, not a chatbot added on. One shared context layer connects your company’s knowledge, so AI can do the upkeep and your team can trust the answers.
Why NuHQ is different
Docs & SOPsUpdates & Q&ADecisions & context
One shared context layer.
Current, sourced, permission-aware knowledge that your people and AI can work from.
When you ask
Answers come with receipts.
Get an answer grounded in company knowledge, with the source and its context attached.
SOPs are messy and inconsistent
Turn rough docs into structured cards
Give your team clear, sourced knowledge instead of another document to decipher.
Two documents say different things
Flag contradictions and draft the fix
Owners review and verify before the wrong answer spreads.
Answers get lost in private chats
Bring sourced answers into the work
Permission-aware answers in Slack and on the web, with a source people can check.
You can’t tell what landed or went stale
See what reached people and needs attention
Read tracking and ownership make knowledge gaps visible.
From information to understanding
Explore NuHQ Knowledge
Cited answers
Follow the answer back to its source
Ask a question and see a grounded answer alongside the knowledge that supports it. Open the source to understand the context, not just the conclusion.
InfoStream
Updates reach the right people
A personalized feed brings relevant updates and conversations together. Consumption benchmarks help teams understand what has reached people and where gaps remain.
Groups
Teams share the right context
Rule-based membership keeps the right people included. Each group brings its resources, updates, tasks, surveys, dates, and files into one shared home.
Collections
Knowledge stays organized
Organize trusted knowledge by department or group. A shared glossary defines company terminology, while selected public collections can serve audiences outside the company.
Content editor
Expertise becomes reusable
Create living documents with collaborative authoring, autosave, version control, comments, and verification. Review and publish with contributors while keeping permissions in place.
Questions
Questions become trusted answers
Route questions to the right people and recommend grounded answers from existing knowledge. Resolved questions become searchable FAQs, ready for the next person.
My Team
Leaders see where help is needed
See team consumption, group exposure, and open posts. Navigate reporting hierarchies and compare against company benchmarks to spot where support is needed.
01 / 07
The results · an actual customer move
Their knowledge moved.
Their whole company moved forward.
A 950-person B2B software company
Year-one Knowledge cost compared with legacy Guru, including AI usage and migration. Activity as of October 2026.
A fair look, side by side
Keep the strengths. Choose the better fit.
Guru and NuHQ share important foundations. The decision is about the experience, the context, the migration, and the economics that fit your team.
 Guru | ||
|---|---|---|
| Cited AI answers | ||
| Automatic video transcription | Relies on a call tool | |
| Knowledge verification | ||
| Immediate duplicate detection | ||
| Built-in RAG optimization | ||
| Permission-aware answers | ||
| Public knowledge portal | ||
| Slack integration | ||
| MCP | ||
| Work context | ||
| Pricing approach | Published Knowledge plans + expected AI usage | Custom quote |
A real tool. A considered transition.
Bring the knowledge.
Leave room to get it right.
Keep the tools. Connect the knowledge.
Bring knowledge from Guru, Notion, Confluence, Google Drive, OneDrive, and SharePoint.
Ask in Slack or through MCP for permission-aware answers with sources. See the FAQs for import behavior and sync schedules.
Know your costs
Compare your total costs
Every plan includes all Knowledge features. Add expected AI usage and any scoped migration cost, then compare with your Guru quote on the same scope.
Before you make a move
Good questions. Straight answers.
Will all of our Guru content transfer?
Choose the Guru collections you want to import and preview the mapping before bringing them into Knowledge. Guru permissions and groups do not carry over: access follows the destination folder in Knowledge.
Cards import as published. Draft status, archive status, full version history, and verification intervals do not carry over. Attachments, embeds, and card links mostly transfer, but need review.
Review destination-folder access, content, ownership, and verification before your team relies on the imported knowledge.
How long will migration take?
That depends on your card volume, permissions, taxonomy, and review needs. We agree on timing after looking at your environment. There is no one-size-fits-all migration duration.
Can Guru stay connected during the transition?
Ongoing sync is available where supported. We confirm which content can sync, how it behaves, and what your team needs to review before agreeing on a transition plan.
Can people ask questions in Slack?
Yes. Ask by slash command, mention, or direct message and get a permission-aware answer with sources. Slack notifications are separate: mentions, tasks, posts, and questions are delivered as direct messages to linked users, not to configured channels.
Can our AI tools use Knowledge through MCP?
Yes. MCP is available for read and search access. Each user signs in with OAuth, and responses respect that user’s permissions. It does not provide write access.
Which tools can we connect, migrate from, or sync with?
Bring your existing knowledge and everyday tools into the conversation:
- Microsoft 365: Sync selected group events to Outlook and tasks to Microsoft To Do, and open Word, Excel, and PowerPoint attachments in Microsoft 365. Each person connects their own account.
- Slack: Ask by slash command, mention, or DM for permission-aware answers with sources. Notifications for mentions, tasks, posts, and questions go as direct messages to linked users.
- Okta: Use OIDC single sign-on and SCIM 2.0 provisioning to create, update, and deactivate users, with role and group mapping.
- Guru: Import selected collections using the migration tool, with ongoing sync where supported. Access follows the destination folder; Guru permissions and groups do not transfer.
- Notion: Import your knowledge and keep it current with one-way daily sync. Notion permissions do not transfer.
- Confluence: Bring content into Knowledge with a one-time import. Imported content lands as drafts for review.
- Google Drive: Import content with hourly one-way sync into Knowledge.
- OneDrive, SharePoint: Import content with hourly one-way sync into Knowledge.
- MCP: Read and search Knowledge from connected AI tools. Each user authenticates with OAuth, and access respects their permissions.
We’ll review permissions, configuration, and supported sync behavior with you before connecting your tools.
Should we expect the same 69% savings?
Your total depends on your plan, usage, migration scope, and Guru quote. We can help you compare those numbers fairly.
What happens when I request a test drive?
Share your name, company, and email so we can discuss your Knowledge needs and what a move from Guru could involve.
Your knowledge deserves the right home