A Comala Document Management alternative for a small team
We make a small Confluence app in the same corner of the market, so read this knowing who wrote it. We are not going to tell you that the established app is bloated: it is a serious product that does things ours does not do at all. What we can do honestly is describe what it is for, what Confluence already gives you for nothing, and what is left over for a team of five to fifty people who want one thing — to know which pages are overdue for a read-through, and who owns them.
1. What Comala Document Management is
Comala Document Management, by Appfire, is a document-control app: workflows, reviews, approvals and states applied to Confluence pages and spaces. Its Marketplace listing, read on 2 October 2026, describes global workflows applied to pages and spaces, multiple approvals, automated state changes, labels and publishing, e-signature authentication, workflows assigned to users or groups, expiry dates "to keep content current", custom versioning for records, a Document Activity audit trail, and workflow metadata displayed on the page. The same listing showed 5,997 installs and a rating of 4.7 out of 5 from 176 reviews, and carried Atlassian's Enterprise Certified mark. It is a mature app with a long history on Server and Data Center and a documented migration path to Cloud. Its Cloud version is now built on Atlassian Forge (Appfire's Forge FAQ), and one of its three built-in workflow templates, the Content Expiry Workflow, puts an expiration period on the Approved state so that a page moves to an Expired state for re-review when the date is reached (Built-in workflow templates). Periodic review, in other words, is something it already does, as part of a workflow.
One line on that listing deserves repeating, because it is more honest than most marketing in this category: "Appfire does not claim compliance or certification for any of our tools. Beyond technical elements, compliant systems must apply procedural and administrative controls." No app makes you ISO-compliant. The tool records what people did; the procedure is yours.
2. When it is the right tool, and you should stop reading
Pick the workflow engine, theirs or another one of its size, when any of these is true:
- An approval has to be enforced, not merely recorded. A page must not be publishable until two named roles have signed, and the app must hold that gate.
- You need e-signatures — an authenticated act of approval, not a comment saying "looks good".
- You need states on the page: Draft, In review, Approved, Expired, with transitions and conditions, visible to readers and reportable across a space.
- An auditor wants the full activity trail of every edit and every approval, per document, exportable, with versioning you control.
- Your governance is already written in terms of workflows, and the cost of the app is small beside the cost of re-writing the procedure.
If two or more of those describe you, nothing further down this page is an alternative to it. Buy the bigger tool, and budget for the configuration: a workflow engine is only as good as the workflow somebody sits down and designs.
3. What Confluence Cloud already gives you for nothing
Before any app, the native options. Each is genuinely useful and each stops short in the same place.
- Page status — a coloured label on the page, such as Reviewed or Out of date (documentation). It is a label, not a date: nothing becomes overdue and nothing reminds anybody.
- Page owner — Confluence records an owner per page and ownership can be transferred in bulk (documentation). It answers "whose page is this", not "when was it last checked".
- The content manager's activity view (Confluence Premium and Enterprise) — sort and filter the content tree by last activity (documentation). Last edited is not last reviewed: a page nobody has needed to change in a year may be perfectly current, or quietly wrong.
- CQL search —
lastmodified < now("-365d")finds pages untouched for a year (CQL, knowledge-base article). Same limit, plus someone has to remember to run it. - Confluence automation — scheduled rules with conditions and actions, including commenting on a page (overview, triggers, actions). This is the closest a site admin gets for free, and on a small scale it works: a scheduled rule, the Lookup pages action to find pages last updated more than a set time ago (in Confluence the Scheduled trigger takes no query of its own), a comment. What it does not give you is a per-page review date that someone can set from the page itself, a cadence per page, or one list of what is overdue across spaces — because there is no field holding "reviewed on" for a rule to read.
That missing field is the whole of the gap. Everything native measures change; a review is a statement that somebody looked, which leaves no edit behind.
4. The question that decides it
Not "which app has more features". Ask instead: does your process need to be enforced, or recorded?
- Enforced — approvals gate publication, states are mandatory, signatures are required: a workflow engine, and a person to own its configuration.
- Recorded — somebody should re-read this page every quarter, and we want to see what is overdue and who owns it: a single-purpose app, or automation plus discipline.
Teams of five to fifty almost always start in the second row and buy for the first, then configure a workflow nobody follows. The cheaper mistake is the other way round: start with the date and the owner, and move up when an auditor actually asks for signatures.
5. What we make
Northwick Apps makes Review Due, a Confluence Cloud app for the second row and nothing else: a review date and an owner on every page, without putting your pages into a workflow. You set a review date, an owner and a cadence (30, 90 or 180 days, or a year) in the page byline; a page shows as due soon within 14 days of its date and overdue after it; one comment on the page mentions the owner at most once a week while it is due or overdue; and one dashboard lists the tracked pages you are allowed to read, with what is overdue first (one load shows up to 5,000 of them and says so above the table when a site has more). Like Comala's Cloud version, it is built on Atlassian Forge, with no servers of ours; it stores page metadata and the reviewer's account ID, never page content.
What it deliberately does not do, so nobody buys it by mistake: no approvals, no e-signatures, no workflow states, no gate on publishing, and no trail of every edit. It keeps the page's owner and the latest review date — not who performed each review, and not the previous dates: marking a page reviewed overwrites the date rather than appending to a log. If your auditor needs a signed approval, Review Due is not the app, and this page just told you which kind is.
It is available on the Atlassian Marketplace. The documentation describes every screen, the FAQ answers what it does and does not do, and the Security page says plainly what we have and have not got — no SOC 2, no third-party penetration test, no published DPA.
A neighbouring case, if what you actually need is a record that people read a policy rather than a date for re-reading it: we also make Acknowledge, which asks a group to confirm they have read a page and keeps who confirmed which version, and the article on how to see who has read a Confluence page compares the native options for that.
6. Why there is no price table here
Prices on the Marketplace change, and a comparison table copied into a web page goes stale silently. Comala Document Management's pricing for your user count is on its listing; ours is on ours, and Atlassian bills both. The honest comparison is not price per user, it is whether you will use what you are buying.
And if you already run Comala and your team uses the workflows: stay. Swapping an app that holds your approval history for a smaller one is a cost, not a saving.
Questions
Write to support@northwick-apps.com. We answer from the code: if an app cannot do something, we say so.