Templates & macros
The macros and templates you actually want are either Cloud-only, deprecated, or sold separately via the Marketplace.
What people actually say
✕Typical enterprise Confluence deployments end up running five to fifteen Marketplace apps — advanced diagramming, structured data macros, template libraries, compliance workflows, enhanced search — each with its own per-user fee.
Source: Capable — Confluence app sprawl tax ↗✕Marketplace apps bill on total Confluence user count, not the people who actually use the app, so 500-user instances pay for 500 licenses of a diagramming tool 10 people touch.
Source: Capable — Marketplace per-user billing ↗✕Reviewers point at the WYSIWYG editor offering hundreds of widgets but no font selection, no efficient tabular input and no stylesheets — pushing teams to Marketplace add-ons for basics.
Source: Capterra — Confluence editor limitations ↗
Templates are versioned React components in your repo; macros are server actions you can read. Diagrams render via excalidraw or a self-hosted drawio. No Marketplace app per feature, no per-user multiplier on the diagramming tool ten people actually use.