Comma vs Confluence
TL;DR
Confluence is the wiki. Comma is where a report that already exists as HTML gets rendered and reviewed. The overlap is narrow: Confluence Cloud has no way to render arbitrary HTML on a page at all, and Comma has no wiki, no page tree, no space permissions model. What sends people looking for a comparison is the same recurring workflow — a generated report needs to land somewhere the team already comments, and Confluence wasn't built to hold it.
The workflow this page is actually about
A build produces a coverage report, an eval harness produces a scored run, a notebook produces a chart-heavy summary — all as HTML. The team's docs live in Confluence, so someone tries to get it there. Confluence gives three options, and none of them render the report: attaching the file serves a download, not a page, and drops the assets folder that came with it; the HTML macro doesn't exist in Cloud and is disabled by default in Data Center, correctly, since it would let arbitrary markup run inside the wiki's own origin; pasting a screenshot is what most teams actually do, which is why the page says "as of March" and nobody's sure if it still is.
At a glance
| Comma | Confluence | |
|---|---|---|
| Category | HTML report workspace | Wiki and documentation platform |
| Renders arbitrary HTML? | Yes — faithfully, sandboxed | No HTML macro in Cloud; disabled by default in Data Center |
| Embeds a hosted HTML page? | N/A — it's the host | Only via a Marketplace iframe app, once hosted elsewhere |
| Anchored comments on the HTML | Yes — text selections and table cells | No — page comments attach to the wiki page, not iframe content |
| Comment without an account | Yes — anyone with the link | Needs Confluence/Atlassian access |
| Refresh model | Revisions — re-run the source, PATCH the report | Manual re-attach or re-embed |
| Scheduled refresh | Routines, any cadence, every plan | Not a native concept |
| Agent posting (MCP) | Yes — scoped comma_sk_… tokens |
Confluence has an API; no HTML-render or comment-anchor surface |
| Spaces, page trees, permissions | No — Comma is not a wiki | Yes — this is Confluence's core product |
| Price | Free — pay only for routine AI compute | Per-user pricing, free tier for very small teams |
What Confluence is good at
Being the team's documentation system of record. Spaces, page hierarchies, permission schemes, macros for Jira and other Atlassian tools — Confluence is the default wiki for a lot of engineering orgs, and it does that job well. If the deliverable is written documentation, Comma has nothing to offer here; keep it in Confluence.
What Comma is good at
Rendering and reviewing the artifact Confluence structurally can't hold. Comma starts exactly where the three workarounds fail:
- The HTML renders as generated — sandboxed, untouched, no macro, no stored-XSS tradeoff to make.
- Comments anchor to the actual rendered content — a chart, a table cell — not to a page-level comment box under a screenshot.
- When the source re-runs — nightly build, weekly eval, a fixed notebook — the new HTML lands as a revision at the same URL instead of a re-attach that orphans the existing thread.
- An agent is a first-class collaborator: publish, read comments, reply, and resolve over MCP under one scoped, revocable token.
Where each one wins, in detail
Wiki, specs, runbooks, project docs
Confluence wins, outright. Comma has no page tree, no space permissions, no macros. Not a real comparison for that use case.
Reviewing a generated HTML report
Comma wins. The report is already HTML; Comma renders it directly and anchors comments to it, with none of the macro tradeoffs Confluence Cloud doesn't even offer.
Recurring reports
Comma wins. "This regenerates every build" has no clean native answer in Confluence beyond re-attaching or re-embedding and losing continuity. Comma's model — one URL, a revision per run, persistent threads — is built around exactly that, with routines to run the schedule.
External and casual reviewers
Comma wins. Anyone with the link can comment with no account. Confluence commenting generally assumes Atlassian access.
Using them together
Keep specs, runbooks, and project docs in Confluence, and publish generated HTML reports to Comma. When a report needs a home on a Confluence page too, embed it via iframe — the page stays live, and Comma still owns the comment layer on the actual content.
Try Comma
Comma is free, and meant to be enough to use honestly: unlimited reports, unlimited commenters, unlimited routines, full anchored commenting, full MCP access.