Knowledge Base & Wiki
Confluence
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Atlassian Pty Ltd · www.atlassian.com
Compare with Notion Wikis → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Confluence at a glance
- Vendor
- Atlassian Pty Ltd
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates Confluence 3/5, the mean of 6 judges. Confluence Cloud is a mature collaborative wiki whose strength, in the bench's scoring, lies in authoring and search and in access control, both clustering at 7 to 8: live co-editing, full-text search across attached files and into Google Drive and SharePoint, granular space and page permissions, SAML single sign-on and IP allowlisting through Atlassian Guard, and an exportable audit log. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 1 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Confluence Cloud is a mature collaborative wiki whose strength, in the bench's scoring, lies in authoring and search and in access control, both clustering at 7 to 8: live co-editing, full-text search across attached files and into Google Drive and SharePoint, granular space and page permissions, SAML single sign-on and IP allowlisting through Atlassian Guard, and an exportable audit log. Knowledge governance is weakest at 4 to 6, the widest spread and a genuine split: four judges scored 4, declining to count the approval workflow they found — a plugin prototype in developer documentation last updated in 2018 — as governance; two scored 6, crediting its documented states, blocked self-approval and rollback. We found no public information on named page owners, review dates with reminders, or whether search and AI answers honour page permissions. Cloud pricing is unusually public — Free at $0 for 10 users, Standard at $5.78 per user / month, Premium at $11.16 per user / month — but Enterprise is contact-sales, Guard is unpriced on the captured pages, and the self-managed Data Center edition ends life on March 28, 2029.
Speaks for it
- Rich collaborative editor with full-text search that covers attached files and reaches into Google Drive and SharePoint
- Granular per-space and per-page permissions with SAML single sign-on, enforced two-step verification, IP allowlisting and an audit log exportable as CSV or via a REST API
- Cloud pricing published in detail: Free at $0 for 10 users, Standard at $5.78 per user / month, Premium at $11.16 per user / month, with guests free up to five per paid user
- Documented integration plumbing: REST API v2 with a downloadable OpenAPI spec, webhooks with statistics, and a Rovo MCP server endpoint for AI assistants
- A free Cloud Migration Assistant moves space data, users, attachments and Marketplace apps with pre- and post-migration reports
Held against it
- The only documented approval workflow is a plugin prototype last updated in 2018, and we found no public information on named page owners, review dates with reminders or read confirmations
- We found no public information on whether search and AI answers honour each reader's page permissions
- The self-managed Data Center edition has a published end of life on March 28, 2029, when subscriptions and Marketplace apps expire
- The full cost is not computable from public pages: Enterprise is contact-sales and the Atlassian Guard subscription carrying single sign-on is unpriced
- We found no public information on a custom domain, SEO controls or an in-product help widget for externally published documentation
Best for
- You need a real-time collaborative wiki with deep search across pages, attached files and connected tools like Google Drive and SharePoint for day-to-day team documentation
- You administer external collaborators: the guest model is documented in detail, with each guest limited to a single space and free up to five guests per paid user
- You publish support documentation to anyone on the internet and want it connected to Jira Service Management for centralised self-service support
- You want published per-user cloud pricing with a starting point of Free at $0 for 10 users and Standard at $5.78 per user / month
Avoid if
- You need formal document governance — named page owners, expiring review dates, read confirmations and a shipped approval workflow — which the bench scored lowest, at 4 to 6, with the only documented approval workflow being a 2018 plugin prototype
- You must self-host long term: the self-managed Data Center edition's support and subscriptions end on March 28, 2029, with Marketplace apps expiring then
- You need a fully computable enterprise budget: Enterprise is contact-sales and the Atlassian Guard subscription carrying single sign-on is unpriced on the captured pages
- Your procurement requires a European contracting and hosting chain: the contracting entity is Atlassian Pty Ltd under Australian law, the default hosting footprint is global, and data residency is an opt-in feature covering only certain in-scope data
The scores
| Criterion | Panel median |
|---|---|
| Editor, structure & search | 3.5 of 5 |
| Verification, ownership & freshness | 2 of 5 |
| Permissions, SSO & administration | 3.5 of 5 |
| Help-center publishing & integrations | 3.5 of 5 |
| Import, export & self-hosting | 3 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 3 of 5 |
Verification, ownership & freshness
Show reasoningHide reasoning
How this is scored
Whether the content stays true: page owners or experts named per page, verification with a review date and a reminder when it lapses, approval or publishing workflows with drafts and reviewers, read confirmations for mandatory pages, analytics on views, searches without a result and stale pages, duplicate detection, archiving rules, and an audit trail of who changed and approved what.
0 — No way to see who owns a page or when it was last checked beyond the edit date.
3 — Page history and last-edited dates; owners, verification, approvals and content analytics are basic or not described.
5 — An owner or verifier per page, a review interval with reminders, a draft and publish step, page view statistics, and archived pages kept out of search.
8 — Approval workflows with several reviewers, read confirmations for mandatory pages, analytics on failed searches and stale content, duplicate or outdated content flagged automatically, and an exportable audit trail of changes and approvals.
10 — Governance that a regulated organisation runs on: controlled documents with versioned approvals that meet a named standard (ISO 9001, GxP), expiry and review enforced per space, knowledge gaps reported from searches and AI questions, and every published statement traceable to an approved version.
The Operations Lead
Versioning with compare and revert, a draft-to-published step through live docs and schedule publish, view analytics on Premium and an exportable audit log of changes are all documented. But the thing I need most — a named owner per page with a review date and a reminder when it lapses — we found no public information on, and the approval workflow with author and approver groups appears only as a plugin prototype in developer documentation last updated in 2018. 2 6 15 17 20 23
The IT Administrator
Page versioning with comparison and revert, analytics on Premium plans, and a site audit log exportable as CSV are documented. An approval workflow with separate author and approver groups that cannot self-approve appears in developer documentation as a Workflow plugin prototype on a page last updated in 2018, and we found no public information on a named owner or verifier per page, review intervals with reminders, read confirmations, or stale-content and failed-search analytics. 2 6 17 20
The Support Knowledge Manager
Live docs act as drafts convertible to published pages, publishing can be scheduled, page history compares and reverts, Premium adds analytics, the site audit log exports to CSV, and a documented author-and-approver workflow blocks self-approval and rolls back to the last accepted version. We found no public information on per-page owners, review dates with reminders, read confirmations, or reporting on searches that return nothing — the gaps a support team feels daily. 2 6 15 17 20 23
The Engineering Lead
Version history with compare and revert, page analytics on Premium, and a draft-to-published path via live docs cover the basics of keeping pages honest. The approval workflow I found is a 2018 developer prototype with waiting-for-approval, accepted and rejected states plus rollback to the approved version, not a shipped owner-and-review-date system; we found no public information on named page owners, review reminders, read confirmations, or analytics on failed searches and stale content. 2 6 15 17 23
The Quality Manager
The captured developer pages describe an approval workflow with editing, waiting-for-approval, accepted and rejected states, an approver queue, blocked self-approval and rollback to the last approved version — the bones of controlled documents — alongside page versioning, a draft-to-published conversion, view analytics on Premium and an audit log exportable as CSV. That workflow is presented as a plugin prototype on a page last updated in 2018, with a stated limit that without core product changes only a banner can point readers to the most recent approved content, and we found no public information on read confirmations for mandatory pages or review dates that expire a page, which is exactly what our certifier asks for each spring. 2 15 17 20 23
The Skeptic
History with compare-and-revert, audit logs exportable as a CSV capped at 10,000 activities over 180 days, analytics at Premium, and a live-docs-to-published-page step are shown; per-page owners, review dates with reminders, and read confirmations are not described anywhere I read. The approval workflow I did find is a 2018 developer prototype whose own text admits that without core changes the best it can do is show users a banner — I will not count a prototype as governance. 2 15 17 20
Permissions, SSO & administration
Show reasoningHide reasoning
How this is scored
Who may see and edit what, and how the administrator keeps control: roles and permissions per space and per page, restricted or private pages, guest and external access, groups synced from Azure AD/Entra ID, Google Workspace or LDAP, single sign-on (SAML, OIDC), SCIM provisioning, two-factor authentication enforced, an audit log of access and permission changes, and admin controls over sharing and public links. Where the data is hosted and certifications are scored under sovereignty.
0 — Everyone in a workspace sees and edits everything; no permissions of any kind.
3 — Admins, members and guests, or private and shared pages; per-space or per-page rights, SSO and an audit log are basic or not described.
5 — Permissions per space and per page, guest access with limits, single sign-on through Google or Microsoft, two-factor authentication, groups, and admin control over public sharing.
8 — SAML or OIDC single sign-on with any identity provider, SCIM provisioning or LDAP and directory group sync, enforced 2FA, an audit log of views, edits and permission changes, IP or domain restrictions, and permissions honoured by search and AI answers.
10 — Access control an enterprise auditor accepts as documented: granular roles with inheritance explained, just-in-time and external access with expiry, every access and permission change logged and exportable to a SIEM, and the permission model published with its limits.
The Operations Lead
Strong and specific: per-space and per-page permissions, guests limited to a single space and free up to five per paid user, SAML single sign-on with multiple identity providers, enforced two-step verification, automated provisioning via Atlassian Guard, IP allowlisting, and an audit log exportable as CSV or through a REST API and webhooks. Single sign-on comes via a separate Guard subscription on the lower tiers, and we found no public information on whether search and AI answers honour each reader's permissions. 2 3 6 8 19 20
The IT Administrator
Granular permissions per space and page are documented (not on the Free plan), guests are limited to a single space with up to five guests per paid user, and SAML single sign-on, enforced two-step verification, automated user provisioning and IP allowlisting come through Atlassian Guard — a separate subscription on Standard and Premium, included at Enterprise. The audit log exports as CSV with up to 10,000 activities from the past 180 days and is reachable via REST API and webhooks. We found no public information on directory group sync from an identity provider or on permissions being honoured by search and AI answers. 2 6 19 20
The Support Knowledge Manager
Granular space and page permissions, guests confined to one space at up to five per paid user, SAML single sign-on with enforced two-step verification and automated provisioning via Atlassian Guard, IP allowlisting, multiple identity providers, and an audit log that exports and can be forwarded by webhook put this at the enterprise band. The guest permission model is published with its limits in real detail; we found no public information on whether search and AI answers honour page permissions. 2 6 8 19 20
The Engineering Lead
Granular space and page permissions on the paid tiers, guests capped at a single space with unusually detailed admin documentation, SAML SSO with enforced two-step verification and automated provisioning through Atlassian Guard, IP allowlisting, multiple identity providers, and an exportable audit log that also ships through a REST API and webhooks. The catches for my auditors: Guard is a separate subscription on Standard and Premium, the CSV export caps at 10,000 activities over the past 180 days, and we found no public information showing that search results and AI answers honour page restrictions. 2 5 6 19 20
The Quality Manager
Granular permissions over creation, editing and visibility, space-level guest access capped at one space per guest and five guests per paid user, SAML single sign-on with support for multiple identity providers, enforced two-step verification and automated user provisioning through Atlassian Guard, IP allowlisting, and an audit log exportable as CSV or via a REST API are all documented. Guard requires a separate subscription on plans below Enterprise, the Free plan permits no space or page permission settings, and we found no public information on permissions being honoured by search and AI answers. 2 6 19 20
The Skeptic
Space and page permissions, SAML single sign-on with enforced two-step verification and automated user provisioning through Atlassian Guard, IP allowlisting, multiple identity providers, a detailed guest model, and an audit log with CSV export and an API are documented. Two things keep me below the top: single sign-on rides on a separate Guard subscription — the Free plan allows no space or page permission settings at all — and nothing I read shows search and AI answers honouring the permission model. 2 6 19 20
Help-center publishing & integrations
Show reasoningHide reasoning
How this is scored
How knowledge reaches people outside the editor: public or password-protected sites and help centers with a custom domain, branding and SEO controls, an in-app widget or contextual help, ticket deflection in a help desk, multilingual publishing, integrations with Slack, Microsoft Teams, Jira, Google Drive, help desks and CRMs, a browser extension, a documented REST or GraphQL API, webhooks, and an MCP server or connector for AI assistants.
0 — Content cannot be shared beyond the editor and nothing connects to it.
3 — Sharing a page by public link and a few integrations such as Slack; a branded help center, an API and webhooks are basic or not described.
5 — A published site or help center with custom domain and branding, integrations with Slack or Teams and Google Drive or Microsoft 365, a documented API, and embeds of common tools.
8 — A help center with SEO controls, multilingual publishing, access for logged-in customers and analytics, a widget or contextual help inside the customer's product, help desk integration with ticket deflection, webhooks, and a connector or MCP server for AI assistants.
10 — Knowledge delivered wherever it is needed from one source: internal and public audiences served from the same pages with per-audience rules, a complete API with SDKs and rate limits stated, a marketplace of integrations, and every channel measured in one report.
The Operations Lead
Public spaces for support documentation, view-only public links, sharing with outsiders without a Confluence licence, multilingual knowledge base articles and a customer help centre through Jira Service Management cover the outside world; a REST API v2 with a downloadable OpenAPI spec, webhook endpoints with statistics, and a Rovo MCP server for AI assistants cover the plumbing. We found no public information on help-centre SEO controls, a custom domain, an in-product widget or ticket-deflection reporting, which keeps it a step below the top. 2 3 6 8 21 22 23
The IT Administrator
Public links and anonymous access publish entire spaces to the internet, knowledge base articles can be offered in multiple languages, and Jira Service Management provides a customer-facing self-service knowledge base. A documented REST API v2 with downloadable OpenAPI spec and Postman collection, webhooks, and an MCP server endpoint for Rovo are published. We found no public information on a help center with custom domain and SEO controls or an in-app widget, which is what keeps this below the top level. 3 6 8 21 22 23
The Support Knowledge Manager
Anonymous and public spaces publish support documentation to anyone on the internet, articles can be multilingual, Jira Service Management connects the knowledge base to centralised self-service support, and the REST API v2 with a downloadable OpenAPI spec, webhooks, an apps marketplace and an MCP server endpoint for Rovo are all documented. We found no public information on a custom domain, SEO controls, or a widget embedded in our own product — exactly the surfaces a help center is published on. 2 3 6 8 21 22 23
The Engineering Lead
Public links and anonymous spaces get our runbooks and roadmaps outside the firewall, multilingual knowledge-base articles pair with Jira Service Management self-service, and the integration story is the strongest part: a documented REST API v2 with a downloadable OpenAPI spec and Postman collection, webhooks with statistics and SSL verification, a marketplace, and a published Rovo MCP server endpoint for AI assistants. We found no public information on a custom domain or SEO controls for public sites, an embedded help widget, or help-desk ticket deflection numbers. 3 6 8 21 22 23
The Quality Manager
Entire spaces can be published to anyone on the internet as support documentation, knowledge base articles can be offered in multiple languages, specific content such as customer FAQs and release notes can be shared with people outside Confluence, and Jira Service Management provides centralised self-service support; the REST API v2 ships an OpenAPI specification, webhooks are documented, and a Rovo MCP server connects AI assistants. We found no public information on a custom domain, SEO controls or an in-product help widget, so external delivery is solid but not fully dressed. 2 3 8 21 22 23
The Skeptic
Entire spaces can be opened to anyone on the internet, knowledge-base articles can be published in multiple languages, Jira Service Management provides self-service support, and there is a marketplace of hundreds of apps, a documented REST API v2 with a downloadable OpenAPI spec, webhooks, and an MCP server endpoint for AI assistants. I found no public information on custom domains, SEO controls, an in-product widget, or ticket-deflection figures, so I sit just below the top band. 2 3 8 21 22 23
Import, export & self-hosting
Show reasoningHide reasoning
How this is scored
What arriving and leaving would cost: import from Confluence, Notion, Google Docs, Word and Markdown with structure, attachments and links kept, a full export of every space in an open format (Markdown, HTML, XML, PDF) with attachments and history, an API that reaches all content, a stated migration path from Confluence Server or Data Center, open-source code under a named licence, and a self-hosted or on-premise edition with its own documentation.
0 — Content cannot be imported or exported; it can only be read in the vendor's interface.
3 — Single pages export to PDF or Word and some files can be imported; a full export, a Confluence import and self-hosting are basic or not described.
5 — Import from Confluence or Notion and from Word or Markdown, a full workspace export to Markdown or HTML with attachments, a documented API covering pages, and a stated retention of data after cancellation.
8 — A Confluence migration tool or service that keeps hierarchy, permissions and attachments, a full export with history in an open format, a self-hosted or on-premise edition with installation and update documentation, and data returned or deleted on termination under stated terms.
10 — The customer owns the content end to end: open-source code under a named licence that runs fully self-hosted with feature parity stated, a complete export another tool can import without loss, and the deletion of every copy on termination documented.
The Operations Lead
Arriving is well covered: a free Confluence Cloud Migration Assistant that moves space data, users, attachments and Marketplace apps with pre- and post-migration reports, plus the FastShift white-glove service; leaving is covered by documented deletion of all customer personal data after termination. But the self-hosted Data Center edition has a published end of life on March 28, 2029 with subscriptions expiring then, and we found no public information on a full export with page history in an open format — which is what I would need to leave with our history intact. 7 8 13 21 24
The IT Administrator
The free Confluence Cloud Migration Assistant installs on a Data Center instance (Server 5.10.0 or later) and migrates chosen space data, users, attachments and Marketplace apps with pre- and post-migration reports, the REST API covers pages, versions and attachments, and deletion of customer data on termination is stated in the data processing terms. The self-hosted path is time-limited: Data Center support and subscriptions end on March 28, 2029. We found no public information on a full export with page history in an open format, or that the migration preserves page permissions. 7 8 13 23 24
The Support Knowledge Manager
The free Cloud Migration Assistant moves space data, users, attachments and Marketplace apps from Server or Data Center with pre- and post-migration reports, the REST API covers pages and attachments, and the data processing addendum requires deletion of customer personal data after termination. The self-managed Data Center edition carries a published end of life in March 2029, and we found no public information on a full export in an open format with page history. 7 8 13 23 24
The Engineering Lead
The free Cloud Migration Assistant moves space data, users, attachments and Marketplace apps from Server or Data Center with pre- and post-migration reports, the REST API reaches pages, attachments, permissions and versions, and the data processing addendum commits to deleting customer personal data after termination. But the self-managed Data Center edition has a published end of life on March 28, 2029, and we found no public information on a full workspace export with history in an open format, or on Markdown or Word import into the product. 7 8 13 23 24
The Quality Manager
A free Cloud Migration Assistant moves space data, users, attachments and Marketplace apps from Data Center with pre- and post-migration reports, a space export and import path is documented, the REST API covers pages, attachments and versions, and the data processing addendum commits to deleting all customer personal data after termination. The self-managed Data Center edition is documented but the captured pages state its subscriptions and support end on March 28, 2029, and we found no public information on a full export with page history in an open format. 7 8 13 23 24
The Skeptic
The free Cloud Migration Assistant carries space data, users, attachments and Marketplace apps with pre- and post-migration reports, a space export and import path exists, the REST API v2 covers pages, spaces, versions and attachments, and deletion of customer data after termination is contractual. But no captured page states what a full export contains or in what format, and the self-managed Data Center edition has a published end of life on March 28, 2029, when subscriptions and Marketplace apps expire — I have lived through exactly that notice, and it changes what self-hosting here is worth. 7 8 13 24
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where pages, attachments and search indexes are stored and processed, and who the subprocessors are (hosting, CDN, search, email, support, payment, and the AI model provider that reads pages for answers and summaries, with whether content is used for training). Independently sourced by the sovereignty pipeline; a wiki holds internal processes, customer data and trade secrets, so the whole chain counts, not only the database. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU data residency available and an EU contracting entity or EU representative, but parts of the chain (CDN, search, email, support, AI model) run through non-EU providers without a stated safeguard, or EU residency is limited to the higher tiers.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations including the AI model provider, no training on customer content stated, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every page on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including AI, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Operations Lead
The chain is unusually transparent: a published data processing agreement with EU standard contractual clauses under Irish law, and a subprocessor list naming locations including the generative AI providers (OpenAI in the USA, AWS Bedrock and Google Vertex AI partly in the EEA) and the Cloudflare CDN processing traffic globally. But the contracting entity is Atlassian Pty Ltd under Australian law with the EU representative care-of a San Francisco address, and residency is an opt-in feature covering only certain in-scope data over a default footprint spanning the EEA, the USA and other non-EU regions. We found no public information on a no-training commitment for customer content or on ISO 27001 or SOC 2 certifications; the privacy policy reserves use of collected information for machine learning and AI model training under legitimate interests. 11 12 13 14
The IT Administrator
The contracting entity is Atlassian Pty Ltd incorporated under Australian law, the default hosting footprint is global spanning the EEA, Switzerland, the UK, the USA and other regions, and data residency is an opt-in feature covering only certain in-scope data. The subprocessor list is public with locations, naming OpenAI in the USA, AWS Bedrock and Google Vertex AI spanning EEA and USA, and Cloudflare processing customer traffic globally, with standard contractual clauses governed by Irish law and an EU representative published. The privacy policy reserves use of information for machine-learning model training under legitimate interests, while the data processing addendum permits only de-identified, aggregated use of customer data. 11 12 13 14
The Support Knowledge Manager
The contracting entity is Atlassian Pty Ltd under Australian law with an EU representative in Atlassian B.V., the data processing addendum publishes SCCs governed by Irish law, and a sub-processor list names locations including the AI providers. Residency is an opt-in feature covering only certain in-scope data while the default footprint spans the EEA, UK, USA and beyond, with OpenAI, Mailchimp, Snowflake and Zendesk located in the USA; we found no public information on ISO 27001 or SOC 2 certification, and the captured pages do not state that customer content is kept out of AI model training. 11 12 13 14
The Engineering Lead
Atlassian Pty Ltd contracts from Australia under a US-listed parent with global default hosting; EU residency exists but is opt-in and covers only certain in-scope data. In its favour there is a published DPA with SCCs governed by Irish law, an EU VAT number, an EU representative, and a subprocessor list with locations including the AI providers — OpenAI in the USA, AWS Bedrock and Google Vertex with EEA regions — while Cloudflare processes traffic globally, the privacy policy states data may be used to develop, train or fine-tune machine learning and AI models, and we found no public information naming ISO 27001 or SOC 2 certifications. 11 12 13 14
The Quality Manager
A published data processing addendum with EU SCCs governed by Irish law, a published sub-processor list naming locations including the AI providers OpenAI in the USA and AWS Bedrock and Google Vertex with EEA regions, an EU representative in Atlassian B.V., and an opt-in data residency feature hosting certain in-scope data in a chosen region make the chain unusually visible. The contracting entity is Atlassian Pty Ltd under Australian law with a stated global default footprint, the privacy policy states training and fine-tuning of machine learning models on a legitimate-interests basis, and we found no public information on ISO 27001 or SOC 2 certifications on the captured pages. 11 12 13 14
The Skeptic
The contracting entity is Atlassian Pty Ltd, incorporated in Australia and addressed in San Francisco, processing is global by default, and data residency is an opt-in feature covering only "certain (in-scope) data". Credit where due: a data processing agreement with Irish-law clauses is published, and the sub-processor list names the AI providers — OpenAI in the USA, AWS Bedrock, Google Vertex — alongside Cloudflare and a long, US-heavy tail, while the privacy policy reserves machine-learning model training under legitimate interests. That is transparency about a non-European chain, not a European chain. 11 12 13 14
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user and tier, readers or guests free or charged, minimum seats, which features (SSO, SCIM, audit log, verification, help-center publishing, custom domain, AI answers, EU data residency) cost extra, the free tier and its limits, storage limits, the self-hosted edition's licence and support price, minimum term and setup or migration fees.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with users, readers or features is unclear.
5 — Tiers are public with their price per user and main inclusions, but at least one commonly needed piece (SSO, AI, readers or guests, EU residency, the self-hosted edition) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (editors, readers, guests, storage), add-ons priced, the self-hosted edition's licence and support cost stated, minimum seats, term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of editors and readers and a feature set, with every add-on, AI credit, setup, migration and support fee and the cancellation and data-return terms published.
The Operations Lead
The cloud tiers are public to an unusual level of detail — Free at $0 for 10 users with 2 GB, Standard at $5.78 per user / month with 250 GB, Premium at $11.16 per user / month, each with automation steps and Rovo credits per user spelled out, and guests free up to five per paid user, which settles my workshop-read-access worry. But the pieces an operation like ours has to budget for are not priced: Enterprise is contact-sales, single sign-on comes via Atlassian Guard as a separate subscription without a shown price, and the self-hosted Data Center licence is not priced on these pages — so the full annual cost for a feature set with single sign-on or self-hosting is not computable from public pages alone. 3 6 19
The IT Administrator
Cloud tiers are public with prices quoted exactly — Free $0 for 10 users with 2 GB storage, Standard at $5.78 per user / month, Premium at $11.16 per user / month — together with storage limits per plan, guests free at up to five per paid user, and Rovo credits and automation steps per tier. Enterprise pricing is available only by contacting sales, the Atlassian Guard subscriptions that carry single sign-on are unpriced on the captured pages, and we found no public information on the licence price of the Data Center edition, on data residency pricing, or on the FastShift migration service. 2 6 7 19
The Support Knowledge Manager
Free, Standard at $5.78 per user / month and Premium at $11.16 per user / month are published with storage tiers, automation steps, Rovo credits, user limits and free guests at up to five per paid user, with annual billing saving up to 17 percent. Enterprise is sales-only, the Atlassian Guard subscriptions that carry single sign-on are unpriced on these pages, and we found no public information on the self-managed edition's licence cost, minimum seats or term, or VAT treatment. 2 3 6 19
The Engineering Lead
Three tiers are public — Free forever for 10 users at $0, Standard at $5.78 per user / month, Premium at $11.16 per user / month — with storage from 2 GB to unlimited, automation steps and Rovo AI credits quantified per tier, and guests free of charge at up to five per paid user, with annual billing saving up to 17%. Enterprise is contact-sales only, SSO and provisioning sit in a separately priced Guard subscription whose price the captured pages do not show, and we found no public information on the Data Center licence cost, minimum seats, VAT treatment or setup and migration fees. 2 6 19
The Quality Manager
Free forever for 10 users at $0, Standard at $5.78 per user / month, and Premium at $11.16 per user / month are public, together with storage limits (2 GB, 250 GB, unlimited), automation steps and Rovo credits per tier, up to 250,000 users per site, and guests free of charge at up to five per paid user. Enterprise pricing is not public, the Atlassian Guard subscription that carries the SSO and enforced two-step verification is unpriced below Enterprise, and we found no public information on the price of additional Rovo credits, minimum seats or minimum term. 2 6 19
The Skeptic
Free ($0, up to 10 users, 2 GB), Standard at $5.78 per user / month and Premium at $11.16 per user / month are public, with storage tiers, Rovo credits, automation steps per plan, annual savings of up to 17%, and guests free up to five per paid user — better detail than most. But Enterprise pricing is contact-sales, single sign-on sits in a separately sold Guard subscription whose price I never saw, and I found no public information on the self-managed edition's licence or support cost or on VAT treatment. 6 19
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined ⚠ unverified | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Confluence
Is Confluence European?
No. whats-best.ai classifies Confluence as Rest of world.
Where does Confluence store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Confluence have a free plan?
Yes. Confluence has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to Confluence?
As of 1 Nov 2026, the panel rates Document360 (3.5/5), BookStack (3/5) and XWiki (3/5) highest among the other 13 Knowledge Base & Wiki products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Document360 (UK / wider Europe). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Confluence alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location, Hosting options, Data processing agreement. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 16 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 13 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 10 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (24)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor product page www.atlassian.com Checked 1 Nov 2026 Details →
- 2 Features page www.atlassian.com Checked 1 Nov 2026 Details →
- 3 Features page (knowledge base) www.atlassian.com Checked 1 Nov 2026 Details →
- 4 Features page (AI) www.atlassian.com Checked 1 Nov 2026 Details →
- 5 Features page (enterprise) www.atlassian.com Checked 1 Nov 2026 Details →
- 6 Pricing page www.atlassian.com Checked 1 Nov 2026 Details →
- 7 Migration page (Server and Data Center to Cloud) www.atlassian.com Checked 1 Nov 2026 Details →
- 8 API documentation developer.atlassian.com Checked 1 Nov 2026 Details →
- 9 Trust center www.atlassian.com Checked 1 Nov 2026 Details →
- 10 Data protection and residency www.atlassian.com Checked 1 Nov 2026 Details →
- 11 Legal notice www.atlassian.com Checked 1 Nov 2026 Details →
- 12 Privacy policy www.atlassian.com Checked 1 Nov 2026 Details →
- 13 Data processing agreement (dpa) www.atlassian.com Checked 1 Nov 2026 Details →
- 14 Subprocessor list www.atlassian.com Checked 1 Nov 2026 Details →
- 15 Editor, structure & search — found from sitemap www.atlassian.com Checked 1 Nov 2026 Details →
- 16 Editor, structure & search — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →
- 17 Verification, ownership & freshness — found from sitemap developer.atlassian.com Checked 1 Nov 2026 Details →
- 18 Verification, ownership & freshness — found from sitemap www.atlassian.com Checked 1 Nov 2026 Details →
- 19 Permissions, SSO & administration — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →
- 20 Permissions, SSO & administration — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →
- 21 Help-center publishing & integrations — found from sitemap developer.atlassian.com Checked 1 Nov 2026 Details →
- 22 Help-center publishing & integrations — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →
- 23 Import, export & self-hosting — found from sitemap www.atlassian.com Checked 1 Nov 2026 Details →
- 24 Import, export & self-hosting — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →