Confluence

What it is

Confluence is Atlassian’s team wiki: spaces, a page tree, templates, databases, whiteboards, and page-level permissions, on the same identity and admin layer as Jira. For most companies that already run Jira, it is where the runbooks, policies, and product decisions live. That makes it the default source that AI search and support agents index, including Atlassian’s own Rovo, Glean, and the Jira Service Management help center, whose knowledge base is a Confluence space.

Every paid plan now includes Rovo Search, Chat, and Agents, metered in credits. So the question in 2026 is no longer “wiki or AI tool”. It is whether Confluence plus bundled Rovo is good enough for support deflection and internal search, or whether you need a dedicated knowledge layer such as Guru or a different workspace such as Notion.

Where it fits

• Engineering-adjacent knowledge. Specs, incident postmortems, and runbooks that link to Jira work items. Nothing else matches the native Jira linking without a sync tool.
• Help-center content for JSM. Articles in a linked Confluence space power the JSM portal’s self-service suggestions and the Rovo agents that answer requests before a human sees them. If your service desk is JSM, Confluence is the low-friction knowledge base.
• Company intranet and policy hub. Premium adds a dynamic intranet, unlimited storage, a 99.9% uptime SLA, and admin insights. Standard includes free guest access, so contractors and outside counsel can read a space without a seat.
• Agent access. The Atlassian Rovo MCP server and the REST API expose pages and search to external agents, so Claude or a custom bot can read the same corpus.

Pricing reality

Free covers 10 users with 2 GB of storage. Atlassian raised Cloud list prices on 13 October 2026, by 7 to 10% on Standard and Premium and 8% on Enterprise. On Atlassian’s pricing page today, monthly billing for up to 100 users is $7.15 per user on Standard and $14.10 on Premium, up from $6.70 and $13.20 in reseller breakdowns of the old list. Per-user rates fall with volume: at 1,000 users the monthly rate is $4.57 on Standard.

Annual billing is priced by user band, and this is what most teams pay:

• 50 users: $3,600 a year on Standard (about $6 per user per month), $7,100 on Premium.
• 200 users: $12,500 on Standard, $24,500 on Premium.
• 1,000 users: $45,500 on Standard, $90,500 on Premium, $137,000 on Enterprise. Enterprise is offered only from 801 users.

The Rovo allowance is where real cost hides. Standard includes 25 Rovo credits per user per month, Premium 70, and Enterprise 150, pooled across the organization. A basic Rovo Chat question or agent run costs about 10 credits, so Standard covers roughly two questions per person per month. Overage is $0.01 per credit, and Atlassian starts billing usage meters on 3 December 2026. Worked example: 200 people on Standard pool 5,000 credits. If each asks 10 questions a month, they use 20,000 credits, and the 15,000-credit overage adds about $150 a month, or $1,800 a year. That is 14% on top of the $12,500 seat bill, still far below a separate knowledge tool.

Best for

Ops, IT, and support leaders at 50 to 2,000-person companies where engineering already works in Jira, who want one wiki for runbooks, policies, and help-center articles, and who would rather tune Rovo on content they already own than buy and migrate to a second knowledge system.

Versus the alternatives

The two largest options besides Confluence are Notion and Microsoft SharePoint. Pick Notion (Business from about $20 per member per month on annual billing, with Notion Agent and enterprise search included) when the team is not on Jira and wants docs, databases, and light project tracking in one fast editor; alternatives to Notion covers that trade. Pick SharePoint when the company lives in Microsoft 365 and plans to use Microsoft 365 Copilot as its assistant.

The fastest-growing pressure comes from AI-first knowledge layers that sit on top of a wiki rather than replace it. Pick Guru when support agents need short verified answers inside Zendesk or Slack and stale content is the main risk. Pick Glean when answers span dozens of systems and you can fund roughly $40 to $50 per seat with a 100-seat floor. Rule: if more than half of what people search for lives in Jira and Confluence, start with bundled Rovo and measure before buying either.

Watch-outs

• The Rovo allowance is small, and overage is on by default. Two questions per person per month runs out fast once Rovo is announced company-wide. Guard: before 3 December, set a usage limit per meter in Atlassian Administration, then run a two-week pilot and multiply the pilot’s credits per user by headcount before you roll out.
• AI answers are only as good as the page tree. Duplicate and outdated pages produce confident wrong answers, and reviewers on G2 and Capterra repeatedly call Confluence search hard to use in large instances. Guard: before pointing an AI agent at a space, archive pages not edited in 12 months, assign an owner per space, and restrict the agent’s knowledge source to curated spaces only.
• Data Center is ending. Atlassian stopped selling Data Center licenses to new customers on 30 March 2026, and subscriptions expire on 28 March 2029. Guard: if residency or air-gap rules keep you self-managed, confirm a Cloud data-residency region (Standard and up cover Confluence) or an alternative before you sign a renewal that runs past 2028.
• Price rises compound across the Atlassian bill. The October increase hit Jira and Confluence together. Guard: at renewal, quote the Teamwork Collection (Jira, Confluence, Loom, and Rovo) against separate licenses, and remove deactivated and inactive accounts before the renewal count, because every licensed user is billed.