Used by
OpenAna + Confluence
Team documentation and knowledge base.
Live connectionWork management & docs
Ana + Confluence
What Ana does with it.
Tickets Ana picks up and closes with evidence, and docs it reads for context and keeps current.
- 01
Reads architecture docs and runbooks for context
- 02
Publishes post-incident reviews and plans
- 03
Updates runbooks after incidents
Setup
Connected in four steps.
- 1
Connect
Open Integrations in Ana and connect Confluence with a scoped token, OAuth app or service account.
- 2
Scope it
Start read-only and choose which projects, repositories or accounts Ana can see.
- 3
Set the rules
Decide which actions need approval and who approves them - Ana’s guardrails enforce it.
- 4
Put it to work
Ana uses Confluence in investigations, fixes and reports, and every action is logged.
In practice
Playbooks that use Confluence.
SRE / DevOps
From a 3 a.m. page to root cause and fix
An alert pages the on-call engineer. By the time they open the laptop, Ana has correlated metrics, logs, traces and recent deploys, named the likely cause, and drafted the remediation for approval.
Read the playbook →Software
Extracting a service from a legacy monolith
A module inside the monolith needs to become its own service. Ana documents what the module really does, defines the contract, builds the service behind a strangler route, and proves parity before any traffic moves.
Read the playbook →Governed
Every action, approved and logged.
Ana’s guardrails decide what it may do with Confluence, route sensitive actions to named approvers, and keep evidence for each decision. OpenAna is SOC 2 Type II, ISO 27001, HIPAA and GDPR compliant.
FAQ
OpenAna and Confluence.
No. Ana works with Confluence - it uses the tool as a source of context and a place to act - so you keep the tool you already run.
See it connected
Ana on your Confluence.
Thirty minutes, your real setup, one real problem.