Confluence Premium already finds inactive pages. What it doesn't give you: accountable owners, enforced review cycles across every space, and the disposition evidence an ISO 9001/27001 or SOC 2 auditor asks for. Evercurrent turns "we should clean up the wiki" into a documentation-control system.
A single governance dashboard for the whole site, not one space at a time. Staleness by last-updated and last-viewed, orphans with no incoming links, near-duplicate clusters that confuse both people and AI search.
Ownership that survives reorgs. Bulk-assign owners by space, label or author; set review cadences (90/180/365 days); when an owner leaves, their pages route to their manager or a fallback group instead of rotting silently.
| Page | Owner | Review by | Status |
|---|---|---|---|
| Incident Response Runbook | MKM. Keller | 2026-07-20 | Due soon |
| API Auth Standards | JTJ. Tanaka | 2026-06-01 | Overdue |
| Onboarding Guide v4 | ASA. Silva | 2026-09-14 | Current |
| Deploy Checklist (2023) | ?Unowned | — | Needs owner |
Declare policy once — "docs in /Legal expire after 24 months unless re-approved" — and Evercurrent enforces it: notify owner → grace period → archive with full context → optional purge date. Every step logged.
Exceptions: label keep-forever · legal hold · re-approved by owner
One click: a controlled-document register with owners, review history, approval dates and disposition records — mapped to ISO 9001 §7.5 (documented information) and SOC 2 / ISO 27001 documentation-control expectations. Export to PDF/CSV for the audit binder.
| Control | Evidence | Status |
|---|---|---|
| ISO 9001 §7.5.2 — review & approval | Review log, 1,842 events | Covered |
| ISO 27001 A.5.1 — policy review | 12 policies, all current | Covered |
| Retention & disposition | Archive + purge log | 2 pending |
Rovo and every AI assistant reading your Confluence is only as good as the pages underneath. Evercurrent keeps stale and duplicate content out of the corpus, so AI answers cite the current runbook — not the 2021 one.
The planned first-run experience, frame by frame. (Storyboard for the demo video — see it as a static strip until the beta build exists.)
Simple, flat, per-user via Atlassian billing. No tiers to decode, no "contact sales."
Built for the people whose job is to say "no" to new vendors.
100% Forge-hosted. No external servers, no egress: your page content never leaves Atlassian's infrastructure. The badge your security review actually cares about.
Inherits your Atlassian data-residency settings automatically — EU data stays in the EU because there is nowhere else for it to go.
No PII stored outside your instance. Processing is limited to metadata (page age, links, owners) inside Forge storage. DPA folds into your existing Atlassian agreement.
We commit to the Cloud Fortified program requirements (security self-assessment, SLA support, reliability checks) as beta exit criteria before GA.
Honesty note: badges above describe the committed architecture and program path, not certifications already granted. The app is pre-release; Cloud Fortified is earned after Marketplace launch.
We are recruiting 10 Confluence Cloud admins at 250+ seat orgs and a handful of Atlassian Solution Partners. You get the product free for 12 months and a monthly call where your governance headaches become the roadmap. We get the truth about what an audit-ready wiki actually requires. Pre-build stage: your input decides what v1 looks like — and whether it gets built at all.
Request an invite Book a 30-min design-partner callNo spam, no list. One email thread with a founder.