keelapps/Evergreen
For teams whose knowledge base is quietly rotting
A page that was right two years ago still looks right today.
Knowledge bases rot silently — outdated runbooks look exactly as authoritative as current ones, and nobody can tell the difference from the outside. Evergreen gives every Confluence page a freshness status, and gives owners a one-click way to say “I checked, it's still correct” — without editing the page, creating a version, or pinging a single watcher.
The tools in this category are full content-lifecycle suites: archiving workflows, approval chains, automated clean-up jobs. They have proved teams will pay to keep a knowledge base from rotting — and they are a lot of machinery when all that was wanted is a red/yellow/green signal and a button that says it's still fine. Evergreen deliberately stops there.
What it does
A badge on every page
Fresh, Aging or Stale — right in the byline, based on when the page was last edited and when someone last vouched for it. Readers see at a glance whether to trust what they're reading.
Confirm in one click
“Mark as fresh” records who checked and when. It does not edit the page, does not create a new version, and does not notify watchers — the confirmation lives beside the page, not in it.
A dashboard per space
How many pages are fresh, aging and stale; the pages needing attention sorted worst-first; filters by status and owner; and bulk actions for confirming or excluding a whole section at once.
Thresholds that layer
Site defaults (90 / 180 days), overridable per space by space admins, and per page from the byline. The most specific layer wins; everything else inherits.
Exclusions that make sense
A label (evergreen-exempt by default), a whole space, or a single
page from its byline. Templates are never tracked at all.
It will not touch your pages
No archiving, no moving, no deleting, no approval workflow, no email. The biggest objection to lifecycle tools — “it will quietly bury something we need” — cannot happen here.
From install to a trustworthy space, end to end
-
Install and accept the defaults
Aging after 90 days, stale after 180. The nightly scan indexes every space it can see; there is nothing to model and nobody to train.
-
Open the space dashboard
Space settings → Evergreen. The counts say how bad it is; the “Needs attention” list says exactly where to start, worst first.
-
Work the list
Pages that are still right get confirmed — one click each, or two hundred at a time with a bulk action. Pages that shouldn't be tracked get excluded. Pages someone else must judge go on the review list.
-
Let the badge do the talking
From then on, every reader sees the status on the page itself, and every confirmation resets the clock. The dashboard stays quiet until something actually goes stale.
Against what you have today
| Question | Doing nothing | Lifecycle suites | Evergreen |
|---|---|---|---|
| Can a reader tell a stale page from a current one? | No | After configuration | Badge on every page |
| Can an owner vouch for a page without editing it? | Fake edits, “bump” comments | Usually a workflow step | One click |
| Time from install to first insight? | — | Days of setup | One nightly scan |
| Can it archive or delete something you still need? | No | Yes — the top complaint | Cannot; no such code |
| Does page data leave Atlassian? | No | Sometimes — external servers | Never |
Availability
Evergreen is live on the Atlassian Marketplace. It is built and deployed on Atlassian Forge and installs into your Confluence Cloud site straight from the listing.
Licensing is handled by Atlassian. Sites with 10 users or fewer pay nothing at all, with every feature included — there is no feature gate anywhere in the code.
Questions, bug reports and feature requests: raise a support request.
Found a security issue? Please report it privately rather than in a public channel.