Satori Cloud

Write in Confluence.
Publish for your customers.

Turn your Confluence pages into a branded customer-facing documentation site.

Live in 3 minutes
1. Your team writes in Confluence
Content being edited in Confluence
2. Customers get a branded documentation site
Customer-facing documentation website published from Confluence

Keep writing in Confluence

No second CMS or duplicate content to maintain.

Built for your customers

Branded navigation and search without a Confluence account.

Live in 3 minutes

Connect Confluence, choose your pages and publish.

From Confluence to live site

Publish your customer documentation in three steps.

1

Connect Confluence

Connect the Confluence space where your documentation already lives.

2

Choose your pages

Select the pages or page trees you want your customers to see.

3

Publish

Your branded documentation site is live and ready to share.

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.

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.