Confluence publishing pricing

Scroll Sites pricing explained

Scroll Sites is a mature Confluence publishing product. Its pricing is based on the number of licensed Confluence users you have — not just the people who publish external documentation.

That can be perfectly reasonable for a broad documentation operation. It can feel different when a large Confluence organisation only needs a small external publishing workflow.

Understand the pricing model Is it a good fit?

Updated August 2026 Based on K15t and Atlassian pricing documentation

The key pricing relationship

Your Confluence licence

Licensed user count

Scroll Sites subscription

Matching app tier

The publishing team's size is not the main licensing unit.

Pricing basis

Scroll Sites pricing follows the number of licensed users in the Confluence instance.

What you get

K15t includes a broad publishing feature set rather than charging per individual published site.

Main fit question

Does your organisation need a full publishing platform, or a narrower selected-page publishing workflow?

Scroll Sites is not expensive or cheap in the abstract. Its pricing model simply needs to match the publishing problem you are solving.

Scroll Sites is built by K15t and turns Confluence content into externally accessible websites. It is designed as a substantial publishing product rather than a single-purpose sharing feature.

The important commercial detail is that the licence follows your Confluence user tier.

Pricing model

How Scroll Sites pricing works

K15t says the cost of a Scroll Sites for Confluence subscription is determined by the number of licensed Confluence users you have.

The app tier therefore needs to match your Confluence licence tier. If your Confluence instance is licensed for 100 users, you need the corresponding 100-user app tier.

K15t also makes an important point explicit: those users count even when not all of them use Scroll Sites or contribute to the external sites you publish.

In plain English

The size of your Confluence population can affect the publishing-app cost, even if only a small team actually publishes documentation.

This is consistent with Atlassian's general Marketplace billing model, where apps are commonly priced according to the number of users in the Atlassian product on which the app is installed.

What the subscription includes

The user-based price comes with a broad publishing capability.

Looking only at the licensing unit misses the other half of the decision. K15t currently describes Scroll Sites subscriptions as including the full feature set rather than tightly restricting the amount you can publish.

Multiple sites

K15t says the subscription allows an unlimited number of Scroll sites.

Unlimited site traffic

Visits to published sites are not metered as a separate traffic allowance.

Content sources and pages

K15t describes unlimited content sources and pages, subject to limits in the underlying Confluence plan.

Custom domains

K15t says each site can be connected to a custom domain.

Site access controls

K15t documents SSO and token-authentication options for published sites.

30-day trial

Scroll Sites currently starts with a 30-day trial before becoming a paid subscription.

Why the user count matters

The mismatch appears when Confluence is large and publishing is small.

Imagine two organisations that both need to publish roughly the same amount of external documentation.

Organisation A

licensed Confluence users

Small Confluence population

The app tier reflects a relatively small organisation.

Organisation B

2,000

licensed Confluence users

Large Confluence population

The required app tier is much larger even if the publishing need itself is similar.

These user counts are illustrative, not price quotes. Use the Atlassian Marketplace pricing calculator for the current cost at your organisation's tier.

Product fit

When Scroll Sites pricing can make sense

A user-based licence is easier to justify when the product is supporting an organisation-wide publishing capability rather than one narrow use case.

Confluence is a major documentation platform for your organisation

A substantial publishing layer can be a natural extension of a substantial Confluence operation.

You need multiple sophisticated published sites

The included site, domain and content capabilities can matter more than the licensing unit alone.

Authentication is an important requirement

Scroll Sites includes access-control options that may be important for non-public documentation.

Publishing is strategically important

A mature publishing product can justify a larger buying decision when documentation is a core customer experience.

When to look more closely

The calculation changes when your publishing requirement is narrow.

The pricing model can deserve more scrutiny when your Confluence organisation is large but the actual external-publishing requirement is small.

Example requirement

“We just need to publish these 20 Confluence pages for customers.”

Your organisation

Hundreds or thousands of people have Confluence licences.

Your publishing team

A handful of people need to maintain one external documentation site.

That does not make Scroll Sites the wrong product. It means the organisation should compare the breadth of product it is buying with the breadth of problem it actually needs to solve.

Buying checklist

Questions to ask before choosing a Confluence publishing tool

How many licensed Confluence users do we have?

How many people actually manage external publishing?

How many sites do we need?

Do we need authenticated or restricted sites?

Do we need a mature documentation platform or selected-page publishing?

Which capabilities are valuable enough to justify the required tier?

Where Satori Cloud fits

A narrower publishing workflow for a narrower problem.

Satori Cloud focuses on selecting Confluence pages, syncing them into a draft, previewing the external version and explicitly publishing them as a separate website.

It is not trying to match Scroll Sites feature-for-feature. Scroll Sites supports a broader and more mature publishing operation. The question is whether you need that breadth.

Try Satori Cloud

Pricing sources

Pricing information on this page is based on K15t's Scroll Sites pricing documentation and Atlassian's Marketplace billing documentation. Pricing and product packaging can change, so check the vendor's current pricing before purchasing.

K15t pricing documentation Atlassian billing documentation

Comparing Scroll publishing tools?

Pricing is only one part of the decision.

Compare the broader product fit if you're looking for an alternative to the Scroll publishing approach rather than just trying to understand its pricing.

Compare alternatives

Related guides

Decide what kind of Confluence publishing problem you actually have.

Alternative to Scroll Viewport

Compare a lighter selected-page publishing model with the broader Scroll approach.

Compare approaches →

Publish without giving access

If the core requirement is simply getting selected Confluence content in front of external readers.

Read the guide →

Publish product documentation

See what a focused customer-documentation workflow looks like with Satori.

Product documentation →

FAQ

Scroll Sites pricing

How is Scroll Sites priced?

K15t says Scroll Sites pricing is determined by the number of licensed Confluence users in your instance.

Do I pay only for people who use Scroll Sites?

No. K15t states that you pay for all users licensed in Confluence, even when not all of those users directly use Scroll Sites or contribute to published sites.

Does Scroll Sites charge for every site?

K15t currently says a Scroll Sites subscription can create an unlimited number of sites rather than charging separately for each site.

Does Scroll Sites include custom domains?

Yes. K15t currently states that one custom domain can be connected for each site you create.

Does Scroll Sites support private sites?

K15t currently documents SSO and token authentication as access-control options for Scroll Sites.

Is Scroll Sites expensive?

That depends on your Confluence user count and how much of the platform you need. A broad publishing operation may justify the model. A small publishing use case inside a very large Confluence organisation may warrant comparing alternatives.

Is Satori Cloud a direct Scroll Sites replacement?

Not feature-for-feature. Satori has a narrower focus: select Confluence pages, sync them into a draft, preview the external version and explicitly publish the site.

Where should I check the exact Scroll Sites price?

Use the current Scroll Sites listing on the Atlassian Marketplace and choose the user tier and billing period that match your Confluence subscription.

Need to publish selected Confluence pages rather than buy a broad publishing platform?

Satori Cloud focuses on a smaller workflow: connect Confluence, choose the pages, preview the draft and publish the external site.

Start publishing