Never the cloud.
Always yours.

A self-hosted knowledge base. Spaces, pages, a real editor, and live editing, running on hardware you control.

Like Confluence, if you owned it.

Self-host it See pricing

A Solar System Overview page open in docu.nexus, with an author byline, body text and a NASA image, beside a sidebar tree of nested planet folders

Local-first, on purpose

Your data lives on your servers.

Not someone else's. Your people sign in to your server, not to a service of ours. No telemetry, no harvesting, no lock-in. The whole relationship is a license key and your own hardware.

You own the box

It runs on hardware you own, wherever you choose to put it. No big tech company sits in the middle of it, and nothing your team writes passes through one.

Built for federated & on-prem

Made for the places the cloud isn't allowed, so you skip the GovCloud tax and the compliance theater that comes with it.

Punch above your weight

Small teams get the tooling of a big org, without the headcount or the invoice that usually comes with it.

No surprises

Flat pricing, a license key, and your data where you put it. No per-seat tax, and nothing phones home.

The core

See it in use.

Two people in the same page, at the same time.

Two people editing one docu.nexus page: a collaborator count of two with both avatars, and a remote cursor labelled "Elsie MacGill" in the opening paragraph

Slash commands, tables, diagrams and math.

A Galactic Center page in docu.nexus: an image of the galactic core above a Quick facts table giving the distance from the Sun, the central object and the mass of Sagittarius A*, beside the Milky Way Galaxy page tree

Nested pages inside spaces, with access control.

The Solar System space in docu.nexus: eight planet folders with item counts, three page cards, and the nested page tree in the sidebar

Search that finds it, across every space.

The docu.nexus search dialog showing six results for "titan" across three spaces, each with its space name and a matching snippet

Otis

Private AI that operates on your docs.

Otis answers questions, writes summaries, and builds content you ask for directly in docu.nexus, on a model you choose.

The Otis drawer open beside the TRAPPIST-1 page in docu.nexus: a question about how many of its planets could hold liquid water, a thinking indicator, a card reading core_get_page against that page, and an answer giving seven planets and three in the habitable zone, taken from the Quick facts table visible on the page

Plugins

Add what your team needs

A Database View page in docu.nexus titled Solar System Bodies, reading the demo.astro_bodies table from the local instance database: a Grid and Plot switch above a table of bodies with their type, parent body, mass, mean radius, surface gravity and orbital period — Your own database, live, as a page.

The same docu.nexus Database View in plot mode: a three-dimensional scatter of orbit size against orbital period against mass on log axes, points sized by radius and coloured by body type, above selects mapping each column to an axis — Your own database, live, as a page.

A traceability graph in docu.nexus, with requirement cards showing reference key, text, safety category and verification method, connected by labeled derives, refines and allocated edges to subsystem nodes — Requirements decomposed, with the traces drawn.

The same GTV-1 requirements as a verification matrix in docu.nexus: twenty numbered requirements with their status and safety category, and a tick in the Test, Analysis, Inspection or Review-of-design column that verifies each one — Requirements decomposed, with the traces drawn.

A whiteboard page in docu.nexus: a monochrome five-box mission-phase diagram marked up by hand in one pen color, with notes reading 'no abort past here', '2.4 years' and 'dose budget?' joined to boxes by hand-drawn arrows, a bracket under two phases labeled 'cost these together', and a check mark against the first box — A whiteboard that is a page in your space.

The agent tokens screen in docu.nexus, with fields for a token name, a read-only access mode, a nexus scope, and an expiry, each explained underneath — An MCP server, so Claude Code can read and write your docs.