Answers before they have to ask.
A public help center your customers can search, and the block editor your team publishes it from. Grouped navigation, private drafts, custom domain, and instant search — configured in the same workspace that handles your requests.
The help center your customers search — organised by topic, on your own domain.
How it works
One editor, one published site.
Every article is a page in your workspace. You write it on a block canvas — headings, paragraphs, lists, callouts, code, and images — and it stays private to your team until you publish. Publishing writes a new public version of the help center, and nothing else changes.
New pages start in Page Storage, outside the navigation. Dragging one into a group is what puts it in front of readers, so structure stays an explicit decision rather than a side effect of writing. Pages can also stay unlisted: live at their URL, absent from the tree.
The public site is not a separate theme to maintain. Logo, accent colour, and domain are workspace settings; the canvas you write in is the page your customer reads.
What it does
Built for the person who writes the answers.
You already know the answer. The work is putting it where the next person finds it.
Writing
Publish in one sitting
Headings, screenshots, tables, code, video. No markdown, no deploy.
Nothing goes live by accident
Drafts stay internal until you publish.
Start from what you have
Upload PDFs, Word docs, and notes. Edit them into articles.
Organizing
Your tree is their sidebar
Arrange topics once. Navigation, breadcrumbs, and topic pages follow.
Draft without shipping
New pages wait in storage until you drag them into a topic.
Old links never mislead
Addresses are reserved for good, so last month's link never lands on a different article.
Looking like you
Looks like your product
Logo, colours, and fonts are settings. No CSS to maintain.
Lives on your own domain
Publish at help.yourcompany.com. The search traffic stays yours.
A front page that routes
Three cards: getting started, FAQs, or straight to a support request.
Getting found
Answers in two keystrokes
Search on every page, matching as customers type.
Skimmable once they land
Contents, breadcrumbs, reading time, last updated.
Supa answers in their words
The AI agent replies from the articles you have published.
Also included. Unlisted pages, ten-file imports, and unlimited articles, topics, and team members on every paid plan.
Who it's for
Why teams need a knowledge base
The reason differs by team. What they share is a support load that grows with the product and a limit on who can answer.
SaaS support teams
The same twenty questions arrive every week
Answering each one by hand is the single largest cost in the queue, and the answer is only ever seen by the person who asked. A searchable article turns one reply into the reply everyone finds, and the requests that still come through are the ones that actually need a human.
Repeat questions leave the queue
Product and ops teams
No engineering time to spend on a help site
A help center built as a front-end project means a repo, a deploy, and a ticket for every copy change. Here the navigation tree, domain, and branding are settings, so the people who know the answers are the people who can publish them.
No repo, no deploy, no ticket
Solo founders
Every answer currently lives in your inbox
You are the only support channel, so support scales exactly as far as your day does. Five articles and one group is a real help center, and page storage means you can draft the next twenty without publishing a half-finished site.
Ships in an afternoon
Frequently asked questions
Can I import my existing help articles?
Yes. Bring your existing articles over, then organize and refine them in the same place your team manages customer requests.
Can customers see my drafts?
No. A page keeps every saved draft private to your team until you publish it. Readers only ever see the last published version.
Can I use my own domain for the help center?
Yes. Publish your help center on a custom domain so the support experience feels like part of your product.
Is there a limit on articles or pages?
No. Articles, pages, and team members are unlimited on every paid plan.
Do I need engineering to set this up?
No. The workspace is designed for support and product teams to launch and maintain their help center without waiting on an engineering queue.