Comparison · Attestation Flow
Attestation Flow compared with Confirm and Chase (Paperlatch)
Attestation Flow for Confluence 3.1.0 is the production version (30 October 2026). Last updated 1 November 2026. On the Atlassian Marketplace.
We make Attestation Flow for Confluence. This page is neutral by rule: we take no commission from any app we compare, every statement about the other app comes from its own Marketplace listing or documentation with the date and link, and where we could not check something we say so.
Confirm and Chase by Paperlatch is a new read-confirmation app for Confluence. Its developer published a Community article with three tests to run on any app in this category. This page uses their tests, on their terms, against Attestation Flow, and says where our answer is partial.
Everything about Confirm and Chase comes from its Marketplace listing and the Community article, read on 30 October 2026. We did not install or test it. Everything about Attestation Flow is from our documentation, a live Confluence Cloud test site, or the released code.
In numbers
#| Confirm and Chase | Attestation Flow | |
|---|---|---|
| Installs on the Marketplace | None | see the listing |
| Reviews | 0 | 0 |
| Latest version | 5.0.0 (2026-10-21) | 3.1.0 (2026-10-30) |
| List price per year, 10 users | $0 | $0 |
| List price per year, 50 users | $500 | $375 |
| List price per year, 100 users | $1,000 | $750 |
Prices are the first-year annual user-tier prices from the Marketplace REST, read by the script facts.py. "None" for installs means the listing shows no install count yet.
What their listing says
#| Topic | Confirm and Chase |
|---|---|
| Purpose | "Add a confirmation button to any Confluence policy or SOP and pick the group that must acknowledge it." |
| Dashboard | "One dashboard shows who confirmed and who is outstanding across every space." |
| New versions | "Change the policy to start a new round; earlier rounds stay on record." |
| Hosting | "There is no server of ours, and the app makes no outbound network calls." |
| What is stored | "a confirmation record holding an Atlassian account ID, the policy version and a timestamp" |
| Permissions | "The app cannot write to your Confluence and cannot act on a user's behalf" |
| Language | "Language: English." |
Their three tests, applied to Attestation Flow
#The article is Proving who read the policy: what an auditor actually asks for in Confluence, dated 2026-10-21. Its author discloses that they develop Confirm and Chase. The tests, in the article's words, each followed by our answer.
1. The denominator
The article's test: "The useful output is not the list of people who confirmed. It is the list of people who have not." It asks what an app shows when it could read only part of a large group.
Attestation Flow: the compliance report shows for each page who has and has not acknowledged the current version, and the audit export includes outstanding readers, not only completed receipts. If a group cannot be resolved, for example because it is too large to read in full, the app marks it as unresolved, and a page with an unresolved group is never shown as fully acknowledged (documentation). Partly shown live: the outstanding readers in the space report. The unresolved-group case is described in the documentation and covered by tests; we have not shown it live.
2. Version locking
The article's test: when a policy changes, "the new version starts a new round, and the old round stays on record exactly as it was given."
Attestation Flow: a receipt is bound to one page version. An edit creates a new version, receipts for earlier versions no longer count for the current one, and they are kept as history. The space report keeps earlier versions in view. Shown live: the "needs your acknowledgement" message after an edit and the earlier-versions column.
3. What the export contains
The article's test: "Check that it includes people who have left the group, rounds that are no longer current, and the version each confirmation belongs to."
Attestation Flow: the export has one row per receipt with the version acknowledged, and receipts for earlier versions are kept, so confirmations by people who later left a group stay in it. What it does not have: a record of who was required on a past date. A person who was required, never confirmed and then left the group does not appear as a separate line, and there is no "as of 30 June" view. If you need that, ask us before you buy. We have not built it.
Permissions and where the data lives
#Their listing says "read access to pages, users, groups and content permissions, plus Forge app storage". Attestation Flow asks for more, because it does more: it posts reminder comments, can add a policy pack's starter text as the person who asks, and reads page bodies as the signed-in user to compute a checksum. Each scope with its reason is on the Trust page. Both state that they run on Forge with no outbound calls; ours is checked from the manifest, theirs we have only from the listing.
Where Confirm and Chase leads
#- Fewer permissions. The app cannot write to your Confluence, by its own listing. If you want the smallest permission list in this category, that is a real advantage.
- Simplicity. The listing is short and the model is simple: a button, a group, rounds.
Where Attestation Flow differs
#- A quiz and a minimum reading time before confirming, a PIN or authenticator code, and approval of a version before readers are asked (paid).
- A checksum of the exact page version in each receipt, a hash-chained log you can export and verify, and an audit evidence pack PDF.
- A periodic review recorded without a new page version (paid).
- Erasure of a person for data-subject requests.
How to choose
#If you want the narrowest app, Confirm and Chase may be enough. If your auditor asks for version checksums, a verifiable log or a recorded review, look at Attestation Flow. Either way, run the three tests above on both, in a trial, with a real group.
Atlassian, Jira, Confluence and Jira Service Management are trademarks of Atlassian. Other product names are trademarks of their owners and are used only to identify those products. Stanki Guild is not affiliated with, endorsed or sponsored by Atlassian or by any vendor named on this page.