Satori Cloud
Scroll Viewport transition

Looking for an alternative to Scroll Viewport?

Scroll Viewport Cloud is being replaced by Scroll Sites. If you're deciding what to use next, the real question is whether you need K15t's full publishing platform — or a simpler way to publish selected Confluence pages externally.

Compare your options Try Satori Cloud
Updated August 2026 Confluence Cloud

If you use Scroll Viewport today

Scroll Viewport

Legacy Confluence Cloud publishing product

Official successor

Scroll Sites

Broader K15t publishing platform

Lighter alternative

Satori Cloud

Selected-page external publishing

Important in 2026

Scroll Viewport Cloud reaches end of service on 30 September 2026.

K15t says Scroll Sites is the successor to Scroll Viewport. Existing published Viewport sites remain accessible, but K15t recommends moving existing sites to Scroll Sites.

Confluence publishing advisor

How should you share your Confluence content?

Answer four quick questions to find the best way to share Confluence pages with customers, partners, employees, or the public.

Get a clear recommendation in under a minute

We will compare public links, anonymous access, guest access, manual sharing, and publishing as a simple website.

The decision has changed

There are now two different reasons to look for a Scroll Viewport alternative.

Some teams already use Scroll Viewport and need somewhere to move as the Cloud product is phased out.

Others were considering Scroll Viewport because they need to publish Confluence content externally, but don't necessarily need the breadth of a complete documentation-site platform.

Those are different problems — and they lead to different answers.

Your two main paths

Scroll Sites or a lighter publishing tool?

Start by deciding whether you're replacing Viewport's broader capabilities or simply solving an external-publishing problem.

Path 1

Move to Scroll Sites

This is K15t's official successor and the natural starting point if you want to retain a mature Scroll-based publishing operation.

You already use Scroll Viewport and want K15t's migration path.

You need mature help centres or documentation sites.

Custom domains, search or site authentication matter.

You want themes and deeper site customisation.

Publishing is a substantial documentation operation.

Path 2

Use a narrower publishing layer

Satori Cloud fits when the requirement is smaller: choose some Confluence pages and publish them externally without adopting a broader documentation platform.

You only need selected pages published externally.

Confluence should remain the source.

Readers do not need access to the Confluence workspace.

You want to preview synced content before publishing it.

You don't need Scroll Sites' broader feature set.

Current comparison

Scroll Sites vs Satori Cloud

If you're leaving Scroll Viewport, these are two very different approaches.

Relationship to Scroll Viewport

Scroll Sites

K15t's official successor to Scroll Viewport Cloud.

Satori Cloud

An alternative publishing workflow, not a direct Viewport migration path.

Best fit

Scroll Sites

Full help centres, product documentation sites, knowledge bases and broader publishing operations.

Satori Cloud

Publishing a selected set of Confluence pages externally.

Content model

Scroll Sites

Builds sites from Confluence spaces or Scroll Documents, with broader Scroll content-management capabilities available.

Satori Cloud

Choose the individual Confluence pages you want included on the site.

Site experience

Scroll Sites

Themes, extensive visual configuration, custom domains and advanced customisation options.

Satori Cloud

A simpler branded external site focused on getting selected content published.

Search

Scroll Sites

Search is part of its help-centre experience, with additional AI-search capabilities available.

Satori Cloud

Not positioned here as a search platform. The current focus is selected-page publishing and navigation.

Restricted sites

Scroll Sites

Supports public sites as well as authenticated access options.

Satori Cloud

This comparison focuses on externally published content. Authenticated-reader portals are a separate requirement.

Updating the live site

Scroll Sites

Supports automatic/live updates as well as manual site updates.

Satori Cloud

Sync changes into a draft, preview them, then explicitly publish the new live version.

Product scope

Scroll Sites

Broader publishing platform with significantly more site-management capability.

Satori Cloud

Deliberately narrower Confluence-to-web publishing workflow.

Important distinction

Satori is not a drop-in migration target for an existing Scroll Viewport site.

If you already have a sophisticated Viewport implementation and want to retain its themes, configuration and wider Scroll workflow, Scroll Sites is the obvious product to evaluate first.

Satori makes more sense when the transition gives you an opportunity to simplify the requirement itself.

Need continuity

Evaluate Scroll Sites

Keep the broader Scroll publishing model and move onto K15t's successor.

Want to simplify

Evaluate Satori Cloud

Reduce the problem to selecting, previewing and publishing the Confluence pages you need.

The lighter workflow

What Satori does instead

Satori keeps the publishing workflow deliberately small.

01

Connect Confluence

Connect the workspace where the source content is already maintained.

02

Choose pages

Select the individual pages that should appear externally.

03

Sync and preview

Bring the latest source into a draft and review it before changing the live site.

04

Publish

Explicitly publish the new external version when you're ready.

When lightweight publishing is enough

You may not need another full documentation platform.

If the content is already in Confluence and the external requirement is relatively focused, a smaller publishing layer can be enough.

Product documentation

Publish setup guides, how-to content and customer-facing product information.

Customer knowledge base

Give customers a focused destination for reusable help content.

Customer onboarding

Publish setup and implementation guidance as one onboarding destination.

API guidance

Publish authentication, integration and implementation guidance externally.

Pricing matters too

Scroll Sites pricing follows your licensed Confluence user count.

That model can make sense for a broad publishing operation, but it is another factor to consider when your Confluence organisation is large and your publishing requirement is small.

Scroll Sites pricing guide

Simple decision rule

Don't ask “what replaces Scroll Viewport?” until you've asked what you actually need.

Choose Scroll Sites when

You still need the Scroll publishing platform.

You want K15t's migration path and the broader themes, search, domains, authentication and site-management capability.

Choose Satori when

Your real problem is much smaller.

You mainly need to choose some Confluence pages, preview them and publish them as a separate external site.

Scroll product information

Information about the Scroll Viewport transition and Scroll Sites capabilities is based on K15t's current product and migration documentation. Product functionality and timelines can change, so check K15t's documentation before making a migration decision.

K15t Viewport migration timeline Scroll Sites product information

FAQ

Scroll Viewport alternatives

Is Scroll Viewport being discontinued?

Yes for Confluence Cloud. K15t says Scroll Viewport reaches end of service on 30 September 2026 and is being replaced by Scroll Sites.

What is replacing Scroll Viewport?

Scroll Sites is K15t's official successor to Scroll Viewport Cloud. Existing Viewport customers should evaluate K15t's documented upgrade path first if they want to retain the wider Scroll publishing experience.

Is Satori Cloud a replacement for Scroll Viewport?

Not feature-for-feature. Satori is an alternative when your requirement is narrower: publish selected Confluence pages externally while keeping Confluence as the maintained source.

Can Satori migrate my existing Scroll Viewport configuration?

No direct Viewport migration is promised. If preserving an existing Scroll setup is important, Scroll Sites is the more natural migration path.

When should I choose Scroll Sites instead?

Scroll Sites is likely the stronger fit when you need a mature documentation platform with themes, advanced site configuration, search, custom domains or authenticated site access.

When should I consider Satori Cloud?

Consider Satori when you mainly need to select some Confluence pages, publish them as an external site and keep a simple draft-and-publish workflow.

Do Satori readers need Confluence accounts?

No. External readers use the published Satori website rather than accessing your Confluence workspace.

How does Scroll Sites pricing work?

Scroll Sites pricing is tied to your licensed Confluence user count. See the Scroll Sites pricing guide for a more detailed explanation.

Related guides

Work out whether you need a platform or just a publishing workflow.

Scroll Sites pricing

Understand how the Confluence user-based licensing model works.

Pricing guide →

Publish without giving access

See the core Satori model for making selected Confluence content external.

Publishing guide →

Product documentation

See what the narrower selected-page approach looks like for customer docs.

Product docs →

If your Viewport replacement problem is really just “publish these Confluence pages”, keep it small.

Connect Confluence, select the pages you need, preview the external version and publish when you're ready.

Try Satori Cloud