Drydock
Drydock scans a Confluence space you choose for stale pages and lets you archive them with one click. It is admin-gated, runs entirely inside Confluence, and stores no personal data of any kind.
How scanning works
Drydock checks each page's age first. Pages younger than the age threshold are set aside as "too new to judge" and never get an analytics call. Only pages old enough get a Confluence Analytics view-count lookup, so a scan doesn't waste an API call on pages nobody would call stale anyway.
Every scored page lands in one of four staleness bands: too new to judge, fresh, aging, or stale. The bands combine age and view signal so you can see at a glance what needs attention.
Archiving a page
Archive any page directly from the results table in one click. Drydock reads the page's status back from Confluence after the archive call completes, so the table shows a confirmed result, not an optimistic guess. Archived pages stay recoverable through Confluence's own native Restore; nothing about that changes.
Admin-gated
Starting a scan and archiving a page each independently confirm the user is a space admin before doing anything.
Pages you can't see, handled honestly
Confluence's own view restrictions still apply, and Drydock never tries to see around them. If a page becomes view-restricted in the window between a scan enumerating the space and you viewing or archiving its row, Drydock withholds that page's title, age, band, and view count alike and rolls it into a visible summary count instead of silently dropping the row.
That protection covers only that narrow window. A page that was already view-restricted before the scan ran is invisible to Drydock at every layer: it is never enumerated by the scan, never counted anywhere, and never shown in the results at all. If you need a complete inventory of every page in a space regardless of restriction status, this scan is not that inventory, and no summary count in the app claims otherwise.
What Drydock does not do
These are deliberate scope choices, not gaps waiting to be filled.
- No owner assignment.
- No recognition of group-based space-admin grants, only a user's own direct admin grant. The gate fails closed rather than guessing.
- No Jira functionality at all. Confluence only.
- No bulk or multi-page archive. Drydock archives one page at a time, by design.
Data handling
Drydock stores no personal data of any kind. What it stores is non-personal operational data needed to run and resume a scan: page-level metadata (pageId, spaceId, ageDays, staleness band, view signal, view count) plus scan-run bookkeeping such as thresholds, progress, and timestamps. It never persists an accountId, a display name, or page content to storage. For GDPR purposes, Drydock does not act as a data processor: it does not store personal data at any point.
Zero data leaves Atlassian. Drydock makes no calls to any service outside Confluence's own APIs. It runs entirely on Atlassian's Forge platform and is confirmed eligible for "Runs on Atlassian" in both development and production.
Status
Drydock is in final pre-submission preparation and has not yet been submitted to the Atlassian Marketplace.
Support
Questions and bug reports: support@sullinslabs.com
Suspected vulnerabilities: security@sullinslabs.com. See the security page for how Drydock handles your data.