Use Confluence to communicate with your customers.

Keep writing and maintaining your documentation in Confluence. Publish selected pages as a customer-facing knowledge base with clear navigation, search and no Confluence account required.

Get started free See a published site ↗

Confluence stays your source of truth. Satori Cloud becomes the customer-facing layer.

Your team works in Confluence

Customers get their own documentation site

Customer-facing documentation website published from Confluence

✓

One source of truth

Write, review and update in Confluence.

✓

Customers stay out of Confluence

No Confluence account or workspace access required.

✓

Your structure comes with you

Keep page hierarchy and navigation instead of rebuilding it.

Your documentation is already written

The hard part is giving customers a good way to use it.

Making Confluence public can leave you dealing with anonymous-access settings, confusing links, missing navigation and customers landing inside a workspace that was designed for authors.

Satori Cloud lets Confluence stay where your team manages the content while giving customers a separate site built for reading it.

A better experience on both sides

Keep Confluence for authors. Give customers a site built for readers.

✓

Authors keep their existing workflow

Create, review and update documentation in Confluence as usual.

✓

Readers get only what they need

Publish selected pages without exposing internal content or navigation.

✓

Changes stay connected to the source

Stop maintaining a second copy in another CMS, document or help-centre tool.

Your team works in Confluence

A documentation page being written and edited in Confluence

Write, review and update internally

Customers get their own site

A customer-facing documentation and knowledge-base website

Navigate, search and read without Confluence

Built for customer-facing documentation

Everything customers need. Without turning Confluence into the customer experience.

↳

Preserve page hierarchy

Turn your existing parent-and-child page structure into clear site navigation automatically.

⌕

Search published documentation

Let customers search the content you publish without needing a Confluence licence or login.

✓

Choose exactly what is public

Publish selected pages instead of opening an entire Confluence space to anonymous access.

◎

Separate sites for different audiences

Use one Confluence source to publish different content for customers, partners, products or user groups.

↻

Keep the published site in sync

Update the source in Confluence instead of maintaining another copy of the same documentation.

↗

Publish on a customer-friendly URL

Start on a Satori Cloud site and use your own documentation domain when you are ready.

The outcome, not another content job

Give customers better documentation without giving your team another system to maintain.

Satori Cloud closes the gap between where your team manages knowledge and where customers need to use it.

Customers find answers more easily

Give them focused navigation and search across the documentation you chose to publish.

Your team stops republishing the same content

Confluence remains the place to write and maintain the source.

Your internal workspace stays internal

Customers get the approved documentation without needing access to the workspace behind it.

How it works

From Confluence to customer documentation in three steps.

Connect Confluence

Connect the Confluence content your team already owns and maintains.

Choose what to publish

Select the pages or page trees that belong in the external customer experience.

Publish your site

Share a customer-facing destination with its own navigation, search and URL.

Not sure you need another publishing layer?

Compare the native ways to share Confluence externally first.

Public links and anonymous access can be enough for simpler use cases. Our guide explains where each option works well and where teams tend to hit limitations.

Read the comparison →

Frequently asked questions

What teams usually want to know.

Does Satori Cloud replace Confluence?

No. Confluence remains the place your team creates and maintains content. Satori Cloud is the publishing layer that turns selected content into a customer-facing site.

Do customers need a Confluence account?

No. Published documentation is read from the customer-facing site rather than your internal Confluence workspace.

Can we publish only part of a Confluence space?

Yes. Choose the customer-facing pages and page trees you want to publish rather than exposing everything in the source space.

What happens when we change a page in Confluence?

The published version stays connected to the Confluence source, so you keep maintaining the documentation in one place rather than updating a separate copy.

Can customers search the published documentation?

Yes. Search is part of the customer-facing experience, so readers can find published content without using Confluence search or holding a Confluence licence.

Your documentation is already in Confluence

Give your customers a better way to read it.

Connect Confluence, choose what you want to publish and turn it into a customer-facing documentation site.