A knowledge base
that’s wired to the work.

Documentation isn’t valuable because it exists. It’s valuable when it sits next to the thing it describes.

Confluence is a superb general-purpose wiki — and a separate product. Your runbook lives in Confluence; the issue it fixes lives in Jira; the change that executes it lives in your ITSM tool; the automation that runs it lives somewhere else again. Each boundary is an app-link, a macro, a copy-paste, and a chance for the page to fall out of date the moment the system it documents changes.

Versus Desk puts the knowledge base in the same platform as issues, changes, the workflow engine, the device inventory and the vault. A page isn’t a description of the work — it can be part of it: link the live issue, show a workflow run’s status inline, and launch the actual runbook from the article. The KB module lives under Versus Desk → Wiki (Spaces).

The editing experience is table stakes. Versus Desk meets it — and stores content as a clean, portable model rather than a proprietary storage format.

The editor is a real WYSIWYG surface: bold / italic / inline-code, H1–H4, bullet, numbered and task lists, quotes, code blocks, dividers, links and inline images (upload or paste). A “/” slash menu and a + Block menu insert structured blocks, exactly like a modern doc tool. Under the hood every page is portable block JSON — headings, paragraphs with typed marks (bold / italic / code / link), lists, tasks, images, code and smart-blocks — rendered server-side through an XSS-safe allow-list. The same content round-trips to Markdown and HTML losslessly, and imports from Markdown cleanly.

Diagrams are native, not a paid add-on: embedded draw.io (diagrams.net). Insert a diagram, draw it in the full draw.io editor, and it saves inside the page — the source XML plus a rendered SVG travel with the article and stay re-editable. In Confluence, draw.io is a marketplace app you license separately.

This is the wedge. A Versus page can contain live platform objects, not just text about them.

Smart-blocks are dynamic blocks rendered from the platform on read:

• Issue link — pick an issue from a searchable dropdown of your real backlog; the block renders as a live link into the tracker, and the page appears under that issue’s linked docs.
• Workflow run — embed a specific automation run so the article shows its status where the documentation lives.
• Table of contents — generated server-side from the page’s own headings.

And a page can carry a runbook reference: promote a documented procedure into a real Versus workflow you can launch from the article. In an incident, the responder reads the known-good procedure and executes it in place — no swivel-chair from wiki to automation console. A Known-Error problem record can be promoted into a published KB article in a single action, so hard-won fixes become findable knowledge instead of dying in a ticket.

Everything you expect from a mature wiki — spaces, trees, versions, comments, mentions, watches — is present, in one product.

Spaces organize content; pages form a hierarchical tree with breadcrumbs and ordering. Every save is a copy-on-write version with author and edit-comment, and any prior version can be restored. Collaboration is first-class: inline comments, @mentions that notify, and per-page watching that pushes updates through the same notification layer as the rest of the platform. Labels and templates (runbook, meeting notes, decision record, postmortem…) speed authoring, and pages export to Markdown or print-to-PDF, and import from Markdown.

KB content inherits the platform’s governance instead of maintaining its own.

Access is enforced with space- and page-level restrictions that inherit down the tree (a restricted parent hides its descendants), with server-side edit-permission enforcement, not just UI hiding. Because the KB is part of the platform, it carries multi-tenant isolation, the same RBAC as every other module, and the platform’s tamper-evident, hash-chained audit — so a knowledge article’s history is as defensible as a change record’s. Search is a PostgreSQL full-text index over title and rendered body (with an icontains fallback), ranked and scoped to what the reader is allowed to see.

The license is the small number. The integration tax between separate products is the big one.

Running Confluence usually means running the surrounding stack too — Confluence for docs, Jira for issues, a separate ITSM tool, and marketplace apps for diagrams, tables and automation — each with its own seats, admins, identity wiring and upgrade cadence, and brittle links in between. Versus Desk’s KB is part of Platform Core, included with every license alongside Workflow, AI Ops, Vulnerability Management, Observe and Compliance. There’s no separate wiki license, no diagram add-on, and no integration project to make the docs know about the work — because they already share a database.

Every item is a shipping capability of the Versus Desk knowledge base.

Where a network / infrastructure team feels the difference.

Versus capabilities are drawn from the shipping product and its documentation (the Versus Desk knowledge base: WYSIWYG block editor, embedded draw.io, smart-blocks, runbook references, spaces / versions / comments / watchers, permission inheritance, PostgreSQL full-text search, Markdown / HTML export & import). Confluence capabilities reflect its widely-documented feature set; verify current details and obtain marketing / legal review before external distribution.