Use this simple calculator to estimate the gap between the number of people who can access Confluence and the number of people who actually publish external content.

This is not a pricing quote. It does not estimate any vendor’s actual cost. It is a fit calculator.

The goal is to answer a more useful question: are you buying for the whole Confluence site, or for a small external publishing workflow?

Publishing fit result

0.4%

Only 0.4% of your Confluence users are external publishers. A lightweight publishing workflow may be worth considering.

What this calculator is showing you

The important number is the publishing ratio.

If your company has 1,000 Confluence users and four external publishers, then only 0.4% of your Confluence users are involved in the publishing workflow.

That does not automatically mean a full Confluence publishing platform is wrong. But it does mean you should be clear about what you are buying.

A low publishing ratio means the external publishing job is much smaller than the Confluence footprint.

That is when lightweight publishing can become more attractive than a full publishing-suite decision.

Why user count matters in Confluence publishing

Atlassian says Marketplace apps are generally priced based on the number of users in the Atlassian app. K15t’s Scroll Sites pricing documentation says the cost of Scroll Sites is determined by the number of licensed Confluence users.

That means the size of your Confluence instance can matter when evaluating Confluence publishing tools.

If your publishing workflow is used widely across the business, that may be fine. If your publishing workflow belongs to a tiny team, it is worth asking whether the buying model matches the actual job.

Signs you may need a lightweight publishing tool

A lightweight tool may be a better fit when most of these are true:

  • You only have a few people who publish external content.
  • You only need a small number of public pages or hubs.
  • Your main problem is copy/paste drift, stale PDFs, or ugly public sharing.
  • You want Confluence to remain the source of truth.
  • You do not need a large documentation operations platform.

What to do with the result

If your publishing ratio is high, a full publishing platform may be sensible. Many people are involved. The workflow is broad. The value is spread across the organisation.

If your publishing ratio is low, think carefully. You may not need a heavy platform. You may need a focused way to publish selected Confluence pages as clean external content.

That is the problem Satori Cloud is being built around.

Sources: K15t Scroll Sites pricing documentation and Atlassian Marketplace app billing documentation.