What is Guru? Pricing, EU Data Transfer, and Best Alternatives in 2026
Guru is a US knowledge-management platform that has repositioned from a per-seat tool into a bundled platform-plus-services engagement. It publishes no price: its pricing page says it is "not just a per-seat tool" and that "Your investment is tailored to your organization's scale, knowledge complexity, and AI maturity." It offers no EU hosting region, and states in its own privacy policy that EU and EEA personal data is transferred to the United States. It holds SOC 2 Type II, which Ainora does not.
Last updated: 2026-09-06. Every quote on this page was fetched from the vendor on 2026-09-06.
Quick Decision Guide
Guru fits an organisation that wants a knowledge programme rather than a knowledge tool, and that is happy to buy solution engineers and knowledge architecture alongside the software. It is the wrong choice if your data protection policy requires storage inside the EU or EEA, if a tender requires ISO 27001, if you need to size a budget before a scoping call, or if the work you want automated arrives by telephone.
| If you need... | Guru fits | Better alternative |
|---|---|---|
| A knowledge base with a services team attached to design it | Yes | - |
| SOC 2 Type II from your knowledge vendor | Yes | - |
| A price you can size the deal from before a call | No, none published | Dust |
| Customer data stored inside the EU or EEA | No, transferred to the United States | Ainora |
| ISO 27001 for a public-sector or regulated tender | Not claimed on any published page | - |
| Source permissions inherited for every connected system | Some sources only, and admin-connected | - |
| Voice or phone-channel AI for inbound or outbound calls | No | Ainora |
| Small EU languages (LT, LV, ET) as a first-class channel | Not stated | Ainora |
| A self-serve start without a scoping conversation | No | Dust |
How Guru Rates
A six-axis scorecard in the format used across our provider pages. Every note is traceable to a Guru page fetched on 2026-09-06.
| Axis | Rating | Notes |
|---|---|---|
| Pricing transparency | Weak | No figure of any kind on the pricing page. Grep pattern run 2026-09-06: price, pricing, invest, dollar sign, per user, seat, plan. Zero figures returned. |
| EU data residency | Weak | No customer-selectable EU region on any published page. Privacy page states EU and EEA personal data is transferred to the United States, with the EU-U.S. Data Privacy Framework as the safeguard. |
| Certifications | Mixed | SOC 2 Type II audited annually, plus Microsoft 365 Certification and Google Cloud CASA. ISO 27001 is not claimed on security, privacy or pricing. |
| Permission model | Mixed | Inheritance exists but is one of two models, supported for some sources, and requires a source-system admin to connect. The other model indexes as a single connecting user. |
| Services and onboarding | Strong | Solution engineers, knowledge architecture design, rollout playbook and ongoing advisory are bundled into the engagement rather than sold separately. |
| Channel coverage | Weak | Text and knowledge surfaces only. No phone or voice channel. Guru positions itself as powering other AI tools over MCP rather than replacing them. |
What is Guru?
Guru (getguru.com) began as a knowledge base that surfaced verified company answers inside the tools people already worked in. What it sells in 2026 is different, and the vendor says so itself. From the pricing page, verbatim: "Guru is a platform and expertise solution - not just a per-seat tool."
The engagement has three named components on that page: "The Platform / AI Knowledge Layer", "The Expertise / AI & KM Strategy Team", and "The Infrastructure / Enterprise Governance". On the middle one, again verbatim: "Think of it as embedding a KM and AI strategy team into your organization. We design your knowledge architecture, configure and tune your AI agents, build your rollout playbook, and provide ongoing advisory... It's a launchpad, not an ongoing dependency."
It also positions itself against the rest of this field explicitly, which is worth quoting because it tells you what the product thinks it is: "Other platforms connect to your data and retrieve what's there - as-is. Guru structures, governs, and continuously improves your knowledge so it gets more accurate over time. ... And Guru powers your existing AI tools via MCP rather than competing with them."
A naming caution, because the search results are a minefield. Guru.com is a freelance marketplace. Guru Experience Co., Resource Guru, Greenlight Guru and Gurubase.ai are all separate companies. Anything you read about self-hosting Gurubase does not apply to getguru.com.
How much does Guru cost?
Guru publishes no price. Not a starting figure, not a range, not a per-seat rate. The sentence that stands in for one is this, verbatim from the pricing page on 2026-09-06:
"Your investment is tailored to your organization's scale, knowledge complexity, and AI maturity. It includes full platform access, access to a team of solution engineers, knowledge architecture design, and ongoing optimization. Our team will scope the right engagement during your first conversation."
That is a verified absence rather than an oversight, and it is worth stating precisely because trackers and comparison sites keep filling the gap with numbers the vendor does not stand behind. The one number worth reporting comes from the buyer side, and it needs its label attached every time it is used.
| Source | Fetched | Sample and method | What it says | Confidence |
|---|---|---|---|---|
| getguru.com/pricing (the vendor) | 2026-09-06 | The whole page. Grep: price, pricing, invest, dollar sign, per user, seat, plan | No figure of any kind. "Your investment is tailored to your organization's scale, knowledge complexity, and AI maturity." | High |
| Vendr marketplace, median | 2026-09-06 | n=167 purchases, Vendr's own anonymised transaction dataset. Fielding window and buyer-size distribution not published | "Median buyer pays $39,168 per year" and "Based on data from 167 purchases, with buyers saving 18% on average." | Medium. Buyer-side aggregated contract data, not a vendor price |
| Vendr marketplace, narrative about tiers | 2026-09-06 | Prose on a partly templated marketplace page | Describes three named per-user tiers. Guru's own live page publishes no tiers and no list price, so the two sources conflict | Not used on this page |
The Vendr marketplace page is the source of the median, and it is also a warning about how these pages are built. The same page carries a narrative describing three named per-user tiers, which Guru's own live pricing page does not publish. Where a marketplace and the vendor disagree, the vendor's live page wins, so we use only the median, the sample size and the stated average saving, and nothing else from it. If you see a per-seat Guru price quoted anywhere, ask which page it came from and on what date.
Ainora's own answer to the same question is individual pricing, scoped to the work. We do not publish a rate card either, and we are not going to criticise Guru for that. What we will say is that a buyer should get the figure in writing before the pilot, from any vendor, including us.
Does Guru really inherit permissions from your existing systems?
Guru's marketing page states it as an unconditional property of the product. Guru's own documentation qualifies every part of that sentence. Both pages were fetched on the same day, 2026-09-06. Here they are side by side, so you can judge the gap yourself rather than take our word for it.
| Where Guru says it | What it says, verbatim |
|---|---|
| Marketing page, getguru.com/pricing | "Permissions are inherited from your existing systems and enforced in real time." |
| Documentation, on how many models exist | "Guru-level access - After connecting a Source, you control who can search and use that content in Guru by choosing one of two permission models." |
| Documentation, on coverage | "Inherited permissions (this is supported for some sources, for more information see here). Guru automatically respects the native access controls from your Source app." |
| Documentation, on the prerequisite | "How it works: Requires an admin from the Source system (like a Slack Admin or Google Admin) to connect the Source." |
| Documentation, on the other model | "Guru Groups - You manually assign which Guru Groups can access the Source's content. Guru connects as a single user and indexes only what that user can access. Access is controlled entirely within Guru, independent of Source app permissions." |
| Documentation, on the ceiling either way | "Source-level permissions - The person connecting the Source must have permission to access the desired content in the Source app. The content Guru can sync depends on what this connecting user can access." |
Rows 1 from getguru.com/pricing; rows 2 to 6 from help.getguru.com, connecting sources to Guru for AI answers. Both fetched 2026-09-06.
Read together, three qualifications appear that the marketing sentence does not carry. Inheritance is one of two models, not the architecture. It is supported for some sources, not all. And it requires an admin of the source system to be the person who connects it, which in most organisations means a conversation with IT rather than a checkbox.
The default path matters more than the exception. In the Guru Groups model, one account connects the source, Guru indexes whatever that account can reach, and an admin then decides which Guru Groups can see it. The source system's access control list is not consulted when a question is asked. Whatever the connecting account could see becomes searchable by whoever the admin grants.
This is not a Guru-specific defect and we are not presenting it as one. It is the structural property of this whole category: an assistant surfaces what somebody could already technically reach, not what they were meant to see. What is Guru-specific is the distance between the two sentences, and a buyer evaluating any vendor in this field should ask for the documentation page rather than the marketing page.
Where does Guru store European data?
In the United States. Guru's privacy policy says so directly:
"Personal Data that you provide while in the EU or an EAA member state will be transferred to the United States. The General Data Protection Regulation permits such transfer when necessary for the performance of a contract between you and Guru, if Guru obtains your explicit consent to such transfer, or if it is in Guru's legitimate interest to transfer the Personal Data. The laws in the United States may not be as protective of your privacy as those in your location. If we transfer Personal Data from the EU, we will provide an appropriate safeguard such as binding corporate rules, standard data protection clauses, or your consent."
The spelling "EAA" is Guru's own and is reproduced here exactly as served. Anyone re-checking this quote with a search for "EEA" will not find it.
The security page names the mechanism: "Guru complies with the EU-U.S. Data Privacy Framework (EU-U.S. DPF) and the UK Extension to the EU-U.S. DPF, and the Swiss-U.S. Data Privacy Framework (Swiss-U.S. DPF) as set forth by the U.S. Department of Commerce." The same page describes the storage: "Your content is stored and managed in a highly secure AWS database, separated and protected from other client content by a unique team ID."
The absence, with its method. We grepped getguru.com/security, getguru.com/privacy and getguru.com/pricing, all fetched 2026-09-06, for residen|region|us-east|Ireland|Frankfurt|hosted in. The only match across all three pages was a disaster-recovery sentence: "We copy our database daily and save it to a disaster recovery site in an entirely separate region." Guru offers no customer-selectable EU hosting region on any published page.
Relying on the Data Privacy Framework is lawful and common; it is also a policy decision your data protection officer may have already made for you. If your internal rule is that customer content stays inside the EU or EEA, Guru does not clear it at any price, and no amount of contract negotiation moves a hosting region that does not exist.
Does Guru train AI models on your data?
Two sentences, both from Guru's security page, both fetched 2026-09-06. Quoting either one alone misrepresents the vendor, so here are both.
"Your data is never used to train, nor retained by, third-party LLMs."
"Your team's AI model is unique to you and privately trained in your Guru instance based on your team's data and interactions."
So Guru does train something on customer data, a per-tenant model, while asserting that no third-party large language model is trained or retains anything. The security page adds: "Any content submitted to the third party LLM for processing is immediately removed after the output is returned ('zero day retention')", and the pricing page carries the shorter versions, "Your data never trains our AI models" and "your data never trains an AI LLM."
Both things can be true at once, and a comparison table that flattens this to a single tick or cross is wrong either way. The architecture behind "privately trained" is not documented publicly, which is the honest limit of what anyone outside Guru can say about it.
On retention, we publish nothing. Guru states a minimisation principle, verbatim: "Guru will only process what it needs to deliver on its service, and will consequently minimize collection of content and restrict retentions time to the greatest extent possible" (the phrasing is Guru's). No numeric retention period and no admin retention control appears on any of the three pages we fetched. Grep pattern used: retention|retain|delete|deletion|days|purge. Only that sentence, the zero-day-retention clause and backup language returned. We therefore state no Guru retention default, because none is published.
Certifications and compliance, compared honestly
Guru holds more third-party assurance than we do, and the table says so. A comparison a reader can catch out is worth nothing.
| Item | Guru | Ainora |
|---|---|---|
| SOC 2 Type II | Yes, audited annually. Report shared under NDA | No |
| ISO 27001 | Not claimed on security, privacy or pricing pages | No |
| Microsoft 365 Certification | Yes | No |
| Google Cloud App Security Assessment (CASA) | Yes | No |
| EU or EEA hosting region | None published. Data transferred to the United States | EU-native by design |
| Transfer mechanism relied on | EU-U.S. Data Privacy Framework, UK Extension, Swiss-U.S. DPF | Not applicable, data stays in the EU |
| Published price | No | Individual pricing |
| Phone or voice channel | No | Yes |
Ainora holds no SOC 2 report and no ISO certification of any kind. Guru is audited annually for SOC 2 Type II, covering the SOC 2 Common Criteria plus the Confidentiality and Privacy trust services criteria, and shares the report under NDA. If your procurement process requires SOC 2 from the vendor itself, Guru clears that bar and we do not.
On ISO 27001, the precise finding is an absence with a method: a grep for ISO 27001|ISO27001|ISO/IEC across getguru.com/security, getguru.com/privacy and getguru.com/pricing on 2026-09-06 returned zero matches on all three pages. That is high confidence about those pages and medium confidence as a statement about the company, since a certificate could exist and simply not be advertised. It matters for EU public-sector and regulated tenders that name ISO 27001 as a requirement, where neither Guru nor Ainora would clear it.
Guru Pros and Cons
Pros
- SOC 2 Type II audited annually, plus Microsoft 365 Certification and Google Cloud CASA.
- Solution engineers, knowledge architecture design and a rollout playbook are bundled into the engagement, not sold as a separate services line.
- Honest about being a knowledge programme rather than a tool, and about structuring and governing knowledge rather than retrieving it as-is.
- Designed to power the AI tools you already have over MCP rather than replace them, which lowers the switching cost of adopting it.
- Sensitive-data masking at ingestion, so personal, health and financial data can be redacted before it is stored, indexed or surfaced.
- Inherited permissions are available for some sources, which is more than several competitors offer at all.
Cons
- No EU or EEA hosting region on any published page. European data is transferred to the United States.
- No published price of any kind, so the budget cannot be sized before a scoping call.
- ISO 27001 is not claimed on its security, privacy or pricing pages.
- The marketing claim that permissions are inherited and enforced in real time is qualified in three ways by Guru's own documentation.
- The default permission model indexes as a single connecting user and does not consult the source access control list at query time.
- No numeric retention period and no admin retention control is published.
- No phone or voice channel.
Verdict: Who Should Use Guru?
Guru is the right choice for a US or global organisation that has decided knowledge management is a programme rather than a purchase, that wants solution engineers designing the architecture rather than an empty workspace, and that needs SOC 2 Type II from the vendor itself. The services layer is a genuine differentiator and the company is candid that this is what it now sells. It is the wrong choice for any European buyer whose policy requires customer content to stay inside the EU or EEA, because no such region exists to move to. It is the wrong choice for a tender that names ISO 27001. And it is the wrong choice if the bottleneck you are actually trying to fix is the telephone, because Guru has no voice channel and is not trying to build one. That is where Ainora is a different product rather than a competing one.
Best Guru Alternatives in 2026
1. Ainora
"Guru structures what your team already wrote down. Ainora answers the call that would otherwise have gone unanswered, then writes it down for you."
Ainora is a multi-channel AI teammate, EU-native by design. Where Guru transfers EU and EEA personal data to the United States and relies on the Data Privacy Framework, Ainora keeps European data in Europe as a design decision rather than a configurable option. That is the axis on which the two products differ most for a European buyer.
The second difference is the channel. Ainora picks up inbound calls in the caller's language, joins Slack and Microsoft Teams when a colleague mentions it, and executes work across CRM, calendar and ticketing systems. Guru has no phone channel. The third is language: Ainora is multilingual including small EU languages that platforms built for the English-speaking market do not cover, with mid-conversation switching. Deployment is measured in days rather than quarters, and the service runs at 99.9% uptime.
Where we are behind, we say so: Ainora holds no SOC 2 report and no ISO certification, and Guru holds SOC 2 Type II. Pricing is individual and scoped to the work. Hear the product running in production before you talk to anyone: +1 (218) 636-0234 (English) and +370 5 200 2620 (Lithuanian).
2. Dust
The transparency answer to Guru. A Paris company that publishes seat prices, $30 per seat per month for a Pro seat billed monthly and $150 for a Max seat, both excluding VAT, and that offers EU data residency on the self-serve plan. Its own gap is contractual: the DPA is Enterprise-only.
3. Glean
Enterprise search first, agents layered on top, and the deepest connector estate in the category. Like Guru, it publishes no price: its pricing URL now returns a 301 to the homepage and no pricing page appears in its sitemap, checked 2026-09-06. Right answer when the problem really is scale of search.
4. Sana
Acquired by Workday for approximately $1.1 billion, closed 4 November 2025. Its enterprise tier is now sold with Workday HCM or Workday Financial Management through Flex Credits, which effectively rules it out for a company that does not run Workday. Holds SOC 2 and ISO 27001.
5. Lindy
Self-serve US agent platform, Slack-first and English-first, US data residency. A very different buying experience from Guru's scoping call, and the same answer on European data.
6. Relevance AI
Build-your-own agents with a self-serve interface, Sydney and San Francisco. Worth a look if what appeals about Guru is the agent tuning rather than the knowledge programme.
Frequently Asked Questions
Guru is a US knowledge-management platform that has repositioned from a per-seat tool into a bundled platform-plus-services engagement. Its own pricing page, fetched 2026-09-06, says: "Guru is a platform and expertise solution - not just a per-seat tool." The bundle it sells has three named components: "The Platform / AI Knowledge Layer", "The Expertise / AI & KM Strategy Team", and "The Infrastructure / Enterprise Governance".
Guru publishes no price. Its pricing page says: "Your investment is tailored to your organization's scale, knowledge complexity, and AI maturity. It includes full platform access, access to a team of solution engineers, knowledge architecture design, and ongoing optimization. Our team will scope the right engagement during your first conversation." A grep of that page on 2026-09-06 for price, pricing, invest, dollar sign, per user, seat and plan returned no figure of any kind. The only number available is third-party: Vendr, a buyer-side negotiation service, reports a median annual Guru spend of $39,168 based on 167 purchases. That is aggregated buyer contract data, not a Guru price.
No customer-selectable EU hosting region appears on any published Guru page. Guru's privacy page states: "Personal Data that you provide while in the EU or an EAA member state will be transferred to the United States." (The spelling "EAA" is Guru's own, reproduced exactly.) Its security page states that Guru complies with the EU-U.S. Data Privacy Framework and the UK and Swiss extensions, and that content is stored in an AWS database. For a buyer whose policy requires in-region storage, that is disqualifying regardless of price.
Yes. Guru's pricing page states: "Guru is audited annually for SOC 2, Type II, Microsoft 365 Certification and the Google Cloud App Security Assessment framework (CASA)." Its security page adds that the audit covers the SOC 2 Common Criteria plus the Confidentiality and Privacy trust services criteria, and that the report is shared under NDA. Ainora holds no SOC 2 report of any type. On this axis Guru is ahead of us and the comparison table on this page says so.
Not on any page it publishes. A grep for ISO 27001, ISO27001 and ISO/IEC across getguru.com/security, getguru.com/privacy and getguru.com/pricing on 2026-09-06 returned zero matches on all three. That is high confidence about those three pages and medium confidence as a global statement, because a certificate could exist and simply not be advertised. Ainora holds no ISO certification either.
Sometimes, and only if configured that way. Guru's marketing page states it unconditionally: "Permissions are inherited from your existing systems and enforced in real time." Its own documentation qualifies all three parts of that sentence. Inheritance is one of two permission models, it is "supported for some sources", and it "Requires an admin from the Source system (like a Slack Admin or Google Admin) to connect the Source." The other model, Guru Groups, works differently: "Guru connects as a single user and indexes only what that user can access. Access is controlled entirely within Guru, independent of Source app permissions."
Both of the following sentences are on Guru's own pages, and quoting either alone misrepresents the vendor. Security page: "Your data is never used to train, nor retained by, third-party LLMs." Same page: "Your team's AI model is unique to you and privately trained in your Guru instance based on your team's data and interactions." So a per-tenant model is trained on customer data while no third-party LLM is. The architecture behind "privately trained" is not documented publicly.
No. Guru is a text and knowledge product. There is no phone or voice channel. For work that arrives by telephone, that is the structural gap and it is what Ainora is built around.
Founder & CEO, AInora
Building AI digital administrators that replace front-desk overhead for service businesses across Europe. Previously built voice AI systems for dental clinics, hotels, and restaurants.
View all articles