Plugins

Plugins

Plugins add capabilities to docu.nexus without changing the core wiki. They ship inside the application, so there is nothing to download or copy into a directory. What decides whether a plugin runs is your license key.

What a plugin can add

A plugin contributes two things you can see.

SurfaceWhat it looks like
Document typesNew kinds of page. They appear in the New content menu next to Page and Folder, and in the space rail. A board or a collection is a page: it lives in a space, inherits permissions and sharing, shows up in search, and has a normal URL.
Admin tabsThe plugin’s own section in the Admin panel, under a Plugins heading below the core groups (Instance, People & access, Content, Licensing).

Plugins also add their own API routes (under /api/x/<plugin>) and their own database tables, both handled for you at startup.

What ships today

PluginAddsLicensed
KanbanThe Board page type, plus a Kanban admin tabPaid, SKU kanban
RequirementsThe Requirements page type, plus a Requirements admin tabPaid, SKU requirements
DatabasesThe Database View page type, plus a Databases admin tabFree, always on
Git DocsThe Git Docs page type: a git repo’s docs as a read-only live viewFree, always on
WhiteboardThe Whiteboard page type: boxes, connectors, freehand, framesFree, always on
Agent surface (MCP)An MCP endpoint at /api/x/mcp, Agent tokens in the account menu, and an Agent tokens admin tabFree, always on
OtisThe assistant drawer and its commands, plus an Otis admin tabPaid, SKU otis
Chat#general, a channel for every nexus and space, the Channel page type, and a Chat admin tabPaid, SKU chat

Licensing

Paid plugins are gated by the signed license key installed under Admin -> Licensing. A key carries a list of entitled SKUs. If your key does not include a plugin’s SKU, the plugin is locked, not removed: its pages show a locked panel and its API returns 403.

Free plugins carry no SKU and are always available.

See Licensing for installing and replacing keys.

In this chapter

  • Installing and Enabling Plugins - how plugins load, where their settings live, and what “not entitled” means.
  • Kanban - boards backed by your GitLab issues.
  • Requirements - collections, schema, traceability, systems tree, and the verification matrix.
  • Databases - the storage backend report, external data sources, and the Database View page.
  • Git Docs - a git repository’s markdown or CI-built docs rendered as a read-only doc site, kept fresh by webhooks.
  • Whiteboard - boards, connectors that bend, frames, showing a board in a page, and the agent tools.
  • Otis - the assistant’s commands, and the switch for outside web pages.
  • Chat - #general, nexus and space channels, channels in the tree, direct messages, joining, Browse, archiving, agents and asking Otis.