A Confluence-class knowledge base, built into the platform — and because it lives next to your automation, a page or a whiteboard can render your live network.
The wiki is organized into spaces, each with its own page tree. A page is authored in a modern block editor: headings and rich text, tables, info/warning panels, columns, code blocks, expandable sections, a table of contents, and embedded draw.io diagrams. Press / in any empty block for the full block menu. Pages carry labels, linked Desk issues, attached runbooks, attachments, comments with @mentions, watchers, and full version history with visual diff and restore.
Start from the template library rather than a blank page — runbooks, incident postmortems, standard operating procedures, RFCs, project plans, release notes, and more. Templates marked Wizardprompt you for the details and fill the page in for you.
The AI Assist panel drafts or augments a section from a prompt — write mode composes prose (and can read an attached image), diagram mode sketches a draw.io diagram. It uses the platform's configured AI provider.
This is the difference from a generic wiki. On a whiteboard or a slide, Insert from Versusdraws an existing object onto the canvas — a certificate, an ADC virtual server, a WideIP, a workflow, an AI diagnostic session, or the network map of a whole site. Pages can embed a live inventory table the same way.
A whiteboard is a free-form canvas — sticky notes, shapes, connectors, and vendor device stencils (F5, Cisco, Palo Alto, Arista, Cloudflare). It's ideal for architecture and incident war-rooms. To render a real topology, use Insert from Versus → Network map and pick a site: Versus lays out every device as a live card — real management IP, vendor, and current status — wired with the discovered links and HA groupings, the same graph as the Network Map. You can also just ask the AI to draw it. “Seed topology” builds the same live cards from a change or incident ticket's impacted CIs.
See it end-to-end in the Academy tour “Wiki & Whiteboards”.