Apps for Confluence

Know which pages
to trust.

Pagecycle shows whether a Confluence page is approved and still current. PageCheck shows how much is AI-written.

Sold and billed through the Atlassian Marketplace

Rovo and MCP

Built for humans and agents

People work in Confluence. Agents work in Rovo, or from Claude, Codex and Cursor over MCP. Same moves, same rules, same History.

ConfluencePages, the board and settings, for people
RovoAtlassian's agents, asked in plain words
MCPClaude, Codex, Cursor and any MCP client, through Atlassian's Rovo MCP server
Pagecycle

Still the
approved version?

Pagecycle gives Confluence pages a workflow: your own statuses, the moves allowed between them, review dates, and a history of who moved each page and why.

PageCheck Coming soon

AI, Human
or Mixed?

PageCheck tells every reader whether a page was written by a person or by AI, down to the passage.

Q4 platform roadmapProduct Docs · By Sam Park AI
Release strategiesEngineering Handbook · By Sam Park Mixed
Code review guidelinesEngineering Handbook · By Maya Chen Human

Made for the people who answer for the wiki

Three questions every Confluence owner gets, and where each answer lives.

A team member asksWho signed off this page, and when was it last reviewed?

Pagecycle keeps the answer on the page: its status and review date under the title, and a history of every move with the person, the time and their comment. Export it as CSV for the audit file.

A reader asksCan I rely on what this page says?

The top of the page answers before they read a line: whether the page is approved and current, and how much is AI-written.

Security asksWhere does our content go?

Nowhere outside Atlassian. Both apps run entirely on Atlassian's platform, so your pages, statuses and AI checks stay in your site. Both are drawn below.

Trust and security

Where your pages go, answered for each app before you install.

Pagecycle
YOUR ATLASSIAN SITE
Confluence pagesStatus is Confluence's own, so search and reports keep working
Pagecycle on ForgeWorkflows and history in Forge storage, which follows your site's data residency
  • No external services and no remote back end
  • Page content and titles are never stored
PageCheck
YOUR ATLASSIAN SITE
Confluence pagesThe published version of each page, in the spaces an admin chooses
PageCheck on ForgeRuns the AI check and keeps results and passages in Forge storage, in your site
  • No external services and no remote back end
  • Each result checks the reader's view permission first

Questions admins ask

For the Confluence admin rolling the apps out.

How long does setup take?

Minutes. Install from the Atlassian Marketplace and turn an app on in one space. Nothing changes anywhere else until you add more spaces.

Will our people need training?

No. Both apps add a label under the page title, where readers already look, and Pagecycle uses Confluence's own status menu. Page owners move a page with one click.

Who controls what?

You do. Confluence admins choose the spaces each app runs in, and space admins set Pagecycle's statuses and the moves allowed between them. Everyone sees only the pages they can already view.

Does our content stay in Atlassian?

Yes. Both apps run entirely on Atlassian, with no remote back end and no external services. Pages, statuses and AI checks stay in your site.

Can our agents use the apps?

Yes, in Rovo, or from Claude, Codex and Cursor over Atlassian's Rovo MCP server. Agents act as their user, with the same permissions and rules, and every move they make is in History.

How do we buy, and where do we get help?

Through the Atlassian Marketplace, billed by Atlassian with your other apps. Support runs through our help portal, answered by the people who build the apps.

Try it on
your own pages

Pagecycle installs from the Atlassian Marketplace in minutes. PageCheck is coming soon.