Skip to content
Remote Desk
Built in — not an integration

A structured wiki where your team already works

Organize knowledge into spaces and pages, write with rich blocks, and find anything with full-text search. Every version is kept and sharing is one click, so the wiki sits beside the rooms and chat — the place a decision is made is the place it gets written down.

ENGINEERINGOverviewOnboardingSetupDeployRunbooksPostmortemsv12UPDATED BY MAYA · 2H AGOnpm run deploy --prod
The flowMeetCaptureAct

Spaces & pages

Structure that scales past the first ten pages

Group knowledge into spaces, nest pages into a real hierarchy, and compose each page from rich blocks — headings, tables, callouts, code, and embeds. The tree stays navigable whether you have ten pages or ten thousand.

  • Spaces and nested page hierarchies
  • Rich-block editor: tables, callouts, code, embeds
  • Favorites and a trash bin so nothing's lost by accident
ENGINEERINGOverviewOnboardingSetupDeployRunbooksPostmortemsv12UPDATED BY MAYA · 2H AGOnpm run deploy --prod

History & search

Every version kept, every word findable

Version history records each edit, so you can see what changed and roll back without ceremony. Full-text search spans every space, turning the wiki into something you actually retrieve from, not just file into.

  • Full version history with rollback
  • Full-text search across every space
  • Internal sharing grants with one click
ENGINEERINGOverviewOnboardingSetupDeployRunbooksPostmortemsv12UPDATED BY MAYA · 2H AGOnpm run deploy --prod

Connected knowledge

Docs that link to the discussion and the canvas

A page doesn't stand alone — link it to the channel where it was debated and the whiteboard where it was sketched. Because chat, the canvas, and the wiki share one workspace, the context never lives in a different tool.

  • Reference channels and threads from any page
  • Carry whiteboard decisions into a written page
  • @mention teammates who are already in the office
See built-in messaging
CHANNELS# launch# design# support# standup-roomDIRECTMayaLeoNoah# LAUNCH · LINKED TO WAR ROOM · 3 SEATED NOWSaraOnboarding ships Friday — summary from the sync is attached.+1 · 4rocket · 2THREAD · 3 REPLIES@Maya can your team take the QA pass?On it — making it a task so it doesn't get lost.CONVERTED TO TASK ✓Message #launch — @mention, attach, or search anything…
We retired Confluence in a month. New pages get written right after the meeting that prompted them, search actually finds things, and version history settled every who-changed-what argument we used to have.
Daniel VågenEngineering Manager, Northvane

FAQ

Questions, answered

Is the wiki included or a separate product?
It's built into Remote Desk and included on every plan, including Free. Plans differ in page and history limits, never in whether the capability exists.
How is it different from Confluence or Notion?
Those are separate apps you integrate and pay for on the side. Here the wiki lives in the same office as your meetings, chat, and tracker, so a page is written where the conversation happened rather than in another tab.
Can I import existing documents?
You can bring content in by pasting rich text and embedding files; the rich-block editor preserves headings, lists, tables, and code. Bulk migration tooling is on the roadmap.
Is version history really kept for every edit?
Yes — every page keeps a full version history, so you can compare revisions and roll back at any time. Retention depth varies by plan.
Does it work self-hosted?
Yes. On a self-hosted deployment, all spaces, pages, and version history stay on your own infrastructure.

Write it down where the decision was made

Docs are included on every plan — start a space in the same workspace your team already uses.