The pricing-opacity problem
A VP of IT we spoke with last quarter described her Glean evaluation like this: three sales calls, a custom quote on PDF, no list price anywhere, and a procurement team that wanted a spreadsheet by Friday. She built one. It had question marks in half the cells.
That's the whole problem with pricing-opacity sales. A buyer can't compare what isn't published. So they reach for whatever number a third party leaked, anchor on it, and lose months in back-and-forth before they even know if the platform fits.
This piece doesn't pretend to have Glean's rate card. Nobody outside Glean has it. What we can do is collect what's been reported publicly, walk through the TCO components that don't show up in any seat-license headline, and put four pricing shapes next to each other so you can argue with your CFO from a stronger position.
What we (think we) know about Glean's pricing
Glean closed a Series F in 2025 at a roughly $7.2B valuation and has reported 1M+ daily active users across its customer base. The company does not publish pricing on its website. It does not list on AWS Marketplace or Azure Marketplace with public SKUs (as of this writing).
What's been reported, with sources we can name:
- $40-80 per seat per month for enterprise contracts is the band that procurement intermediaries and RFP-leak aggregators most often quote. This is third-party reporting, not a Glean disclosure.
- Annual floors around $100,000 appear in multiple analyst notes and reseller summaries when discussing mid-market deals. Again — reporting, not vendor confirmation.
- Connector add-ons, premium support, and what some sources are calling the "agentic" tier (when it ships) are negotiated separately. Nobody outside Glean knows the deltas.
Read that twice. The $40-80 number isn't wrong, but it isn't Glean's number either. If you cite it back to a Glean AE in a negotiation, expect a polite redirect. The honest answer is: ask for a quote, then benchmark it against the alternatives below.
TCO components people miss
Seat license is the line item everyone fixates on. It's also the smallest line item in year one. The expensive parts:
Implementation hours. Enterprise federated search rollouts run 60-200 hours of professional services for the initial deployment. That's connector configuration, identity wiring, permission-mirror testing, content tuning. At a partner blended rate of $250/hr you're looking at $15K-$50K before anyone sends a query.
Connector maintenance. Every SaaS you connect — Salesforce, ServiceNow, Confluence, Notion, GitHub, Slack — has API changes, auth-flow updates, and rate-limit quirks. Glean owns this for connectors they support. For anything custom you build on top, you own it. Plan one FTE-quarter per year of internal effort on the connector layer if you're serious.
Governance retrofits. Permission mirroring is the silent killer. If your source systems have inconsistent ACLs (and they do), the federated index will surface things your CISO doesn't want surfaced. Cleanup work is real. Budget for it.
SSO and IdP integration. Trivial if you're already on Okta or Entra. Painful if you're on a homegrown setup or migrating. Either way, it's not in the seat price.
Agentic upsell. When the agent tier ships in its full form, it almost certainly costs more per seat than the search tier. Microsoft's pattern (Copilot at $30 on top of M365) is the template the whole industry is copying. Plan for a 30-50% uplift on whatever your search-only number lands at.
Three pricing shapes, walked through
The market has settled into three rough archetypes. Each has tradeoffs.
1. Federated enterprise — high-flat-seat (Glean). You pay a healthy per-seat fee. In exchange you get years of connector engineering, a mature permissions model, and a product that works on day 30 instead of day 300. The bet is that your time-to-value beats the seat math. For companies with 50+ source systems and a real knowledge-fragmentation problem, the bet sometimes pencils out. The federation breadth here is genuine — we'll concede that point cleanly. The opacity is the friction.
2. Bundled platform — included in the suite (M365 Copilot, AgentCore). Microsoft 365 Copilot is $30 per user per month, but only on top of a Microsoft 365 baseline — E3 at $36, E5 at $57. So your real all-in cost is $66-87 per user per month for Copilot-eligible seats. The pitch: it's "free" because you're already paying for M365. The reality: you're paying twice and your CFO will eventually notice.
AWS AgentCore went GA on October 13, 2025 with consumption-based pricing — per invocation plus per tool call. Great for variable workloads. Hard to budget for if your usage curve hasn't stabilized. Azure AI Foundry, which went GA June 16, 2025, follows a similar consumption shape.
Salesforce Agentforce takes a per-action approach — roughly $2 per action in the published guidance, varies by action type. Predictable if you have a clear automation use case. Surprising if your action volume spikes.
3. Published unit pricing (Jarvis Registry). The Jarvis Registry is listed on AWS Marketplace and Azure Marketplace with three published SKUs: Starter at $1,500/month, Pro at $2,500/month (bundles Jarvis Chat), and Custom Enterprise for governed deployments. This is platform-level pricing, not per-seat — meaning a 1,500-seat org pays the same Pro tier as a 150-seat org for the core platform. Your variable cost is the underlying model spend on AWS or Azure, billed by your cloud provider, not us.
The point of naming this contrast: we publish, most don't. That's the editorial differentiator. Whether $2,500/month + cloud variable beats Glean's $40-80/seat for your scenario depends on seat count, governance posture, and which source systems you actually care about. Run the math below.
Four-option pricing comparison
| Dimension | Glean | M365 Copilot | AWS AgentCore | Jarvis Registry (★) |
|---|---|---|---|---|
| Published list price? | No — quote-only | Yes — $30/user/mo add-on | Yes — consumption-based | Yes — $1,500 / $2,500 / Custom on AWS & Azure Marketplace |
| License model | Per-seat enterprise, ~$40-80/seat/mo (third-party reporting), $100K+ floor | Per-seat, requires M365 E3 ($36) or E5 ($57) baseline | Per invocation + per tool call (consumption) | Platform tier + cloud-billed model usage |
| Connectors out of the box | Leader — 100+ mature enterprise connectors, years of integration work | Microsoft estate (Graph, SharePoint, Teams, Outlook) plus growing third-party | AWS-native + open via MCP | MCP-native via the MCP Gateway; BYO connector inventory |
| Governance plane | Permission mirroring across federated index | Microsoft Purview integration | IAM-based, AWS-native | Governance-first design, audit logs, policy hooks |
| Best fit | 5,000+ seats, complex enterprise content sprawl, budget for opacity | Heavy M365 shops already on E3/E5 | Variable workloads, AWS-native estates | Mid-market through enterprise wanting transparent unit costs |
(★) Jarvis row published by ASCENDING. We're naming it so you can discount accordingly. Glean's connector breadth advantage is real — that's not a vendor concession, it's a market fact.
Methodology — where these numbers came from
Pricing-comparison content is only useful if you can audit the sources. So:
- Glean $40-80/seat/month: aggregated from three third-party RFP-aggregation reports, two procurement-intermediary blogs (Vendr, Spendflo style), and analyst commentary from late 2024 through early 2026. Glean has not confirmed these figures publicly. We flag them as third-party throughout. $100K annual floor: same source set, reported consistently enough across independent sources that we include it, but it remains reporting.
- M365 Copilot $30/user/month and the E3/E5 baselines: Microsoft's published pricing pages and licensing documentation, current as of Q1 2026. These are official.
- AWS AgentCore: AWS Marketplace listings and the AWS Bedrock pricing page following AgentCore's GA on October 13, 2025. Consumption rates change — check the live page before signing.
- Azure AI Foundry (referenced in passing): Azure pricing pages following GA on June 16, 2025.
- Salesforce Agentforce $2/action: Salesforce's published Agentforce pricing communications, fall 2024 onward. Action types vary.
- Jarvis Registry $1,500 / $2,500 / Custom: AWS Marketplace and Azure Marketplace public listings, ASCENDING's own pricing pages. These are first-party and verifiable.
- Moveworks acquisition $2.85B by ServiceNow in Q4 2025: ServiceNow press release and SEC filings. Included for market-context only.
Where we say "third-party reporting," we mean exactly that. If Glean publishes a rate card next quarter, this article gets a correction note.
The 1,500-seat scenario
Same company, four paths. Annual cost ranges only — we're skipping implementation services to keep the comparison clean.
"Don't sign anything per-seat for 1,500+ users without first quoting a platform-priced alternative on the same workload. The seat-license math collapses fast above 1,000 seats."
- Glean at $40-80/seat/month × 1,500 seats × 12 months = $720K - $1.44M/year. Plus implementation, plus the agentic tier when it lands. Plus a $100K+ floor that doesn't matter at this scale but bites mid-market shops below 250 seats.
- M365 Copilot at $30/user/month × 1,500 seats × 12 = $540K/year just for Copilot, sitting on top of a $648K-$1.03M M365 baseline you may already be paying. If you're not, the all-in is $1.19M-$1.57M/year.
- AWS AgentCore consumption: genuinely depends on usage. A typical knowledge-agent workload at 1,500 seats with moderate query volume lands somewhere in the $200K-$600K/year band based on early customer data, but variance is high. Get a usage model before committing.
- Jarvis Registry Pro at $2,500/month flat = $30K/year platform, plus your cloud-billed model spend. Mid-volume model spend for 1,500 seats typically runs $100K-$300K/year on AWS or Azure depending on which models you route to. All-in $130K-$330K/year.
The Jarvis number is lower because it's structurally different — platform + variable model cost, not per-seat. That's not always the right shape. If you need 100+ federated connectors working on day 30, Glean's price is the price of getting there fast. If you can stage rollout, route through MCP, and accept that you'll own more of the integration glue, the math shifts hard.
Frequently asked
-
Does Glean publish official pricing anywhere?
No. As of May 2026, Glean has not published a price card on their website or any marketplace. All figures in circulation are third-party. -
Is $40-80/seat/month a reliable benchmark?
It's the consensus band across independent reporting, but it's reporting — not a Glean disclosure. Treat it as a starting point for negotiation, not a fact. -
How does Microsoft 365 Copilot's $30 compare to Glean?
$30 is the Copilot add-on price; you also need E3 or E5 underneath. All-in per seat lands in the $66-$87 range, broadly comparable to the reported Glean band but with the M365 baseline included. -
Why does Jarvis Registry publish pricing when others don't?
Editorial choice by ASCENDING. We list on AWS and Azure Marketplace with three SKUs because buyers told us they were tired of quote-only sales cycles. Whether that's the right model for every vendor is a separate question. -
What's the single biggest hidden cost in any of these?
Connector maintenance and governance retrofit work. Plan for one FTE-quarter of internal effort per year on the connector layer regardless of which platform you pick.