Custom domain publishing

Publish Confluence on your own domain

Keep writing in Confluence. Publish selected customer-facing pages at docs.yourcompany.com as a branded website built for readers outside your workspace.

Publish on your domain See how it works
Use a subdomain you own Confluence stays the source Publish only selected pages
docs.yourcompany.com
Confluence documentation published on a custom domain
Your domain
Your branding
Your Confluence content

A customer-facing destination

Your documentation should feel like part of your product, not a link into your workspace.

Confluence can remain exactly where your team writes, reviews and maintains documentation. Your customers do not need to consume that content in the same environment.

With Satori Cloud, selected pages are published to a separate site on a subdomain you own, such as docs.example.com or help.example.com.

That gives customers a recognisable destination for documentation while your internal Confluence workspace stays focused on authoring and collaboration.

Why use your own domain?

Make your Confluence content look like a deliberate part of the customer experience.

Give customers a URL they recognise

Put documentation under your own web presence instead of making the destination feel disconnected from your company or product.

Keep the authoring workflow unchanged

Writers keep editing the source pages in Confluence. The customer-facing site is an output, not another CMS your team has to maintain.

Separate what customers see from Confluence

Publish the pages intended for customers with focused navigation and branding instead of exposing the structure of the internal workspace.

One source. Two audiences.

Confluence for your team. Your domain for your customers.

You are not moving the source content or renaming the internal workspace. You are publishing a separate customer-facing version from it.

Authors
yourteam.atlassian.net/wiki/...

Keep working in Confluence

Write, collaborate and maintain the source pages using the workflow your team already knows.

Customers
docs.yourcompany.com/getting-started

Publish a dedicated docs site

Give external readers a clean destination containing only the pages you have chosen to publish.

How Satori Cloud works

From Confluence to docs.yourcompany.com

Keep Confluence as the source, choose what becomes public, connect your domain and publish when you are ready.

01

Connect Confluence

Connect the Confluence workspace containing the content you want to publish externally.

02

Choose the pages

Select the pages customers should see while keeping unrelated internal content out of the published site.

03

Connect your subdomain

Use a subdomain you control, such as docs.example.com or help.example.com, and point it to your Satori site.

04

Publish

Preview the external version and publish when the content and customer experience are ready.

Two different jobs

Do you want a custom URL for Confluence itself, or a separate site for customers?

They sound similar, but they solve different problems.

A custom domain for the Confluence product

Atlassian offers custom domains for eligible Confluence plans. That changes the branded URL used to access the Confluence application itself.

A customer-facing site published from Confluence

Satori leaves the authoring workspace alone and publishes selected content as a separate external site with its own domain, navigation and branding.

What can live on your domain?

Give customer-facing Confluence content a proper home.

The same publishing model works wherever customers, partners or developers need to read content maintained by your team in Confluence.

Product documentation

Publish guides and product information at a docs domain that matches your company.

Explore product docs →

Customer onboarding

Put implementation guidance and getting-started content somewhere customers can recognise and return to.

Explore onboarding →

External Confluence pages

Publish selected pages for customers and partners without making the internal workspace their destination.

Explore external sharing →

A home you control

Keep the customer-facing URL with your brand.

A custom domain gives published documentation a stable, recognisable home under your company’s web presence.

Satori also supports the basics needed for public documentation to be discoverable, including canonical URLs, sitemaps and search-engine visibility controls.

Branded URL

Use a subdomain such as docs.example.com or help.example.com.

Canonical pages

Give public pages a clear canonical destination on the published site.

Search engine visibility

Control whether public documentation is indexable and expose it through a sitemap.

FAQ

Publishing Confluence on a custom domain

Can Confluence use a custom domain?

Yes. Atlassian provides a native custom-domain option for eligible Confluence plans if you want to change the URL used to access the Confluence application itself. Satori solves a different problem: publishing selected Confluence content as a separate customer-facing site on your domain.

Can I use docs.mycompany.com?

Yes. Satori supports a subdomain you own, such as docs.mycompany.com or help.mycompany.com, provided you control the DNS settings for that subdomain.

Does Satori replace Confluence?

No. Confluence remains the place where your team creates and maintains the source content. Satori publishes the customer-facing version.

Do I have to publish the whole Confluence space?

No. You choose the pages that belong on the external site, so internal or unrelated content can remain in Confluence only.

What happens when a Confluence page changes?

Sync the latest content into the Satori draft, review the customer-facing version, and publish when you want the live site to change.

Do customers need a Confluence account?

Not for a public Satori site. Readers visit the published website on your domain rather than signing in to your Confluence workspace.

Can the published pages appear in Google?

If you enable search-engine visibility, Satori can expose the published site for indexing with canonical URLs, robots controls and an automatically updated sitemap.

Your team writes in Confluence. Your customers visit your domain.

Publish selected Confluence pages as a branded customer-facing site at docs.yourcompany.com.

Publish on your domain