Confluence
Atlassian's team wiki with spaces, page trees, Jira links and Rovo AI, built for engineering and IT documentation.
Confluence is a writing and notes tool for productivity, listed under freemium pricing and best suited to companies already on Jira that need a structured, permissioned wiki.
What is Confluence?
Confluence is Atlassian’s wiki. Content is organised into spaces, one per team, project or product, and each space holds a tree of pages with a fixed parent and child hierarchy. Pages are written in a block editor with macros for tables of contents, status labels, decision logs, embedded Jira issue lists and roadmaps. Whiteboards and databases were added in recent years, so a space can hold diagrams and structured tables next to prose. Templates cover the usual corporate needs: meeting notes, retrospectives, product requirements, incident postmortems and onboarding guides.
The Jira relationship is the reason most companies use it. A requirements page can list the Jira issues it spawned, an issue can link back to the design doc, and release notes can be assembled from a sprint. Rovo, Atlassian’s AI, searches across Confluence, Jira and connected tools, summarises pages and comment threads, and drafts content inside the editor. There is a free plan for small teams, paid Standard and Premium tiers per user, an Enterprise tier and a self managed Data Center edition for organisations that cannot use cloud.
Where it shines
Structure and permissions are mature. Space level and page level permissions, restricted pages, audit logs and inheritance rules give large organisations the control they need, and admins can enforce templates and archive policies across hundreds of spaces. Content lifecycle features such as page ownership, archiving and analytics on which pages are actually read help keep a big wiki from rotting.
For engineering and IT documentation the Jira and Bitbucket links are hard to beat. Incident reviews reference the tickets, runbooks link to the services, and the whole record stays in one vendor’s ecosystem with single sign on and consistent administration.
The Marketplace has thousands of apps, from diagramming tools to compliance add ons, and the Data Center edition remains one of the few serious options for a wiki that must run inside a company’s own infrastructure.
Where it falls short
The editor is slower and more rigid than modern competitors. Pages must live in one place in one tree, tables are basic, and the databases feature is far behind the relational databases in Notion or the formula driven tables in Coda. Writing can feel like filling in a corporate form rather than thinking on a page.
Search has historically been the weakest point of the product. Rovo improves it, but results still rank stale pages highly and many teams rely on carefully maintained space home pages instead. Notifications and comments can be noisy, and the mobile app is adequate for reading pages on the move and not much else.
Cost climbs with headcount because every reader needs a seat, and the most useful admin features sit on Premium. Companies that do not use Jira get little of the integration benefit and should consider a lighter wiki such as Slite, which puts its effort into keeping content current rather than into governance.
Conclusion
Confluence is the safe choice for organisations that already run on Jira and need a wiki with real governance: permissions, audit, templates and the option to self host. It is not where you go for a pleasant writing experience or flexible databases. Pick it for the Jira ecosystem and the administrative controls, and accept that the dated editor is the price of admission.