Nexus Knowledge Base

Beta

Customer help and team runbooks, one tool.

Markdown-first authoring with live preview, a public help center at /help/your-workspace, and a per-article public/private toggle so your customer-facing FAQs and your internal SOPs share an editor — but never a reader.

Start free for 7 days Open in Nexus →

$8 / user / mo · included in the Suite · 7-day trial of every product

Markdown-first — no WYSIWYG fight

/help/:slug

Public help center, indexed by search engines

1-toggle

Public ↔ private, per article, no separate tool

Why it feels different

Most knowledge tools force you to pick a side: customer or internal.

Which is exactly the wrong shape. Half your "internal" runbook is just the public answer with one extra paragraph. Half your help center is just the internal answer with the rough edges sanded off. Nexus Knowledge Base is one editor, one search, one publishing pipeline — with a single toggle that decides who can see each article.

The lifecycle

Draft → Review → Publish → Iterate.

Articles move from a teammate's head to the public help center on a path you can trust — with the version history, draft state, and review step you'd expect from a content tool, not a wiki.

Draft

Markdown editor with live preview. @-mention teammates for review, paste in code blocks, drop in screenshots. Drafts are private to the workspace by default.

Review

Mark "ready for review" — reviewers get a notification. Inline comments on a draft, resolve-as-thread when fixed. No "let me Slack you the suggested edit".

Publish

Toggle public, publish to /help/your-workspace/article-slug. SEO-clean URL, metadata pulled from the article frontmatter, redirect from older slugs handled automatically.

Iterate

Articles have version history. Update once, see who edited what when. The customer always reads the latest; you can roll back if the latest broke something.

The good parts

Ten ideas that make the difference.

Markdown-first

Plain text, fast keyboard, no surprises

No WYSIWYG soup, no "why did the bullet list nest itself again?" Markdown gets out of your way and renders the same on screen as in the database.

Per-article toggle

Public ↔ private, one switch

Toggle "public" and the article appears at /help/your-slug; toggle off and only your workspace sees it. No separate "internal wiki" SaaS — the runbooks and the help center share an editor.

Public help center

Branded, indexed, fast

Your help center renders at /help/your-workspace-slug with your logo, brand color, and SEO metadata. Static-rendered, indexed by Google, embedded in Helpdesk autoreply emails.

Finds things on the first try

Full-text + tag search across all articles you can see. Results respect public/private — internal teammates see internal articles; logged-out visitors only see public ones.

Lightweight grouping that does not turn into a graph

One level of categories: "Billing", "API", "Onboarding". Articles can belong to multiple. No 7-level nested folders that nobody can navigate.

Inline help

Drop an article into a Helpdesk reply

Pick an article from a slash menu while replying to a ticket — the agent sends a link, the customer reads the article, the same article anchors three more tickets next month.

Version history

See who changed what, roll back if needed

Every save is a version. Compare two versions side-by-side, restore a previous version with one click. No "git knowledge required" but the safety is the same.

Code blocks

Syntax-highlighted, copy-button-ready

Fenced code blocks render with syntax highlighting and a "copy" button. The customer reading your "how do I authenticate" article can paste the example without selecting it character by character.

Embedded media

Screenshots, GIFs, short videos

Drag a file into the editor — uploads through Nexus Files, renders in the article, served from the same domain. No "Loom not loading because of CORS".

Analytics

Which articles actually work

Per-article views, "was this helpful?" thumbs, search queries that returned no results. The articles your customers need but you don't have are right there in the report.

External help

A help center that loads fast and looks like you.

Branded with your logo, accent color, and metadata. Server-rendered, indexed by search engines. Articles render with table of contents, copy-link headings, and "edit on Nexus" — for your team, not the customer.

Internal runbooks

The wiki that doesn't need a separate SaaS subscription.

Same editor, same search, same workspace — but only your team can see them. New-hire onboarding checklists, oncall runbooks, "how we deploy" — the things you don't want a 50-seat license for. They're free with the same workspace.

What you won't find

The things we left out — on purpose.

A knowledge base earns its keep by being a place people return to. Here's what we deliberately won't ship.

No WYSIWYG-only editor.

WYSIWYG sounds friendly until your bullet list nests itself for the fourth time. Markdown is the input, rendered Markdown is the output, the gap is zero.

No 7-level folder hierarchy.

You don't need it, your customer doesn't need it, your search certainly doesn't need it. One level of categories, plus tags, plus search. That's the whole API.

No per-author seat tax.

Editing is included with your workspace. We don't charge you a "writer license" on top of the seat you already pay for. Anyone with workspace access can author.

No template lock-in.

Articles are Markdown. Export them, import them, version them in your repo if you want. Your knowledge belongs to your workspace, not to our database.

Connected

How Nexus Knowledge Base fits the rest of Nexus.

A help article is just a ticket reply written before the question is asked. Nexus Knowledge Base sits next to Helpdesk, Team & HR, and your CRM — same workspace, same brand, same search.

Try Nexus Knowledge Base free for 7 days.

No credit card. Comes with every workspace trial.

Start free trial