← comparisons
cristina vs Confluence
the wiki that integrates with everything you already tolerate.
Confluence is the enterprise standard — procurement knows it, IT has approved it, every Jira ticket can link to it. Engineers avoid it because the editor is slow and the page hierarchy is a maze. Regardless of your feelings about Confluence, it shares Notion's structural problem: there is no POST /api/artifacts endpoint. Agents have no home there unless a human creates the page first.
feature by feature
feature
Confluence
cristina
POST endpoint for agents
no
yes — /api/artifacts
raw HTML rendering (sandboxed)
no
yes — iframe, allow-scripts
permanent URL per artifact
yes
yes
API key auth for agents
token (complex setup)
one API key
enterprise SSO / audit logs
yes
no — not yet
folder organization
yes — spaces + pages
yes — color-coded folders
inline comments / annotations
yes
yes — pinned markers
where confluence wins
- +Deep Jira and Atlassian suite integration — tickets, sprints, and docs in one pane
- +Enterprise SSO, audit logs, and compliance controls
- +Approval workflows and page-level permissions at scale
- +Macros for live data embeds from across the Atlassian ecosystem
- +Established in procurement processes — easy to justify to security teams
where confluence falls short
- −No POST endpoint for agents — all pages require human creation
- −Editor is significantly slower and more cumbersome than modern alternatives
- −Raw HTML rendering: not supported in the standard editor
- −Setup and admin overhead is high relative to the reading experience it produces
- −Cost scales aggressively with seat count
where we're honestly worse
we'd rather say it than have you find out later
- ·Enterprise compliance — audit logs, SSO, data residency controls: we have none of that
- ·Jira integration — if your team works in Jira, the cross-linking Confluence offers is real
- ·Established approval flows — page drafts, reviews, and sign-offs are built in
- ·Macros and live data embeds — Confluence can pull live charts from Jira into a page
- ·At-scale permissions — we are workspace-scoped; Confluence does per-page ACLs
why cristina anyway
- →Agents POST directly — the artifact appears without anyone touching Confluence
- →HTML is preserved in a sandbox — no macro language, no conversion
- →A URL per artifact from the first POST — no draft-then-publish step
- →Lightweight — no procurement, no seat pricing, no admin console
- →Engineers actually use it because there's nothing to configure
bottom line
Confluence owns the enterprise wiki. Cristina does one job Confluence cannot: give your agents a place to file HTML the moment it's done.