Self-hosted Confluence alternative: a team wiki you own with Docmost

Every team eventually builds a second brain: the onboarding docs, the runbooks, the "why did we decide that" pages nobody wants to lose. The tools that hold it — Confluence, Notion — are happy to keep it, and to meter it. Confluence bills per user, so your wiki gets more expensive with every hire. Notion keeps the whole thing on its servers, which is a strange place to store the memory of your company. When the renewal lands, the thing you are paying more for is the same set of pages you already wrote. Docmost is the same category of tool, running on hardware you control.

What Docmost is

Docmost is an open-source collaborative wiki and documentation platform. It is not a stripped-down clone; it is a full knowledge base with real-time editing, a modern block editor, nested page trees, spaces, permissions, comments, and search. If you have used Confluence or Notion, the shape is immediately familiar: you make spaces, fill them with pages, invite people, and control who can see what. The learning curve for a team switching over is close to nothing.

The difference is where it lives and what it costs. The hosted incumbents gate the useful parts — granular permissions, more seats, deeper version history — behind escalating plans, and the price climbs with every person you add. Docmost ships those capabilities in software you run yourself, with no per-seat meter and no third party sitting between your team and its own documentation.

The features that actually matter

• Real-time collaborative editing. Multiple people can edit the same page at once, with live cursors and changes that appear as they happen — the feature Confluence and Notion both put at the top of the page.
• Spaces. Separate areas for each team, project, or department, each with its own page tree and its own membership, so engineering docs and HR policies don't live in the same pile.
• Granular permissions. Group-based roles and space-level access control decide who can read, edit, or administer — the kind of control the SaaS tools tend to reserve for their pricier tiers.
• A modern block editor. Slash commands, callouts, tables, code blocks, toggles, and deeply nestable pages, so documents read like documents instead of walls of text.
• Diagrams built in. Draw.io, Excalidraw, and Mermaid diagrams embed directly into pages — architecture sketches and flowcharts live next to the words that describe them.
• Inline comments. Comment on a selection, hold a thread, and resolve it, so review happens in context rather than in a separate chat.
• Mentions and page links. @-mention a teammate to pull them into a page, and link to any other page inline, so the wiki cross-references itself instead of scattering context across tools.
• Page history. Every page keeps versions you can review and restore, so a bad edit is an undo, not a loss.
• Public sharing. Publish a single page to a read-only link when something needs to be readable outside the team, without opening up the rest of the space.
• Full-text search and import/export. Search across your spaces, and move content in and out as Markdown or HTML — your knowledge base is never trapped in a proprietary format.

Why self-host it instead of the hosted version

Your knowledge stays yours. A wiki is the most sensitive thing a company writes down: infrastructure notes, incident post-mortems, half-finished strategy. Self-hosting means that content sits in your database, on your disk, readable only by the people you invite — not indexed, analyzed, or held by a vendor whose terms you don't set.

The cost doesn't scale per seat. Confluence and Notion charge for every user, so growing the team quietly grows the bill for the same pages. Docmost costs what the server costs. Add your tenth teammate or your hundredth and the price is the same.

You own the branding and the rules. It runs on your domain, behind your login policy, at your uptime expectations. No forced feature changes, no sunset emails, no "we've updated our terms." You decide when to upgrade and what the thing looks like.

Who it's for

Small and mid-size teams who want a real internal wiki without a Confluence contract that gets worse every hiring quarter.

Privacy-conscious and regulated organizations — agencies, healthcare, legal, anyone who cannot put internal documentation on someone else's servers as a matter of policy, and who needs to point at exactly where the data lives.

Technical teams and homelabbers who already run their own stack and would rather their runbooks and architecture diagrams live alongside everything else they operate, on infrastructure they trust.

The honest setup notes

Raw self-hosting is real work, and we'll be straight about it. Docmost needs a PostgreSQL database and a Redis instance to run, and those are yours to provision, tune, and keep alive. Backups are on you — the database holds your pages, and uploaded attachments live on disk, so a real backup plan has to cover both. Updates are yours to run, which means watching releases and applying them without breaking the pieces underneath. You'll put the app behind a reverse proxy to terminate TLS, and decide where attachments go — local disk, which then has to be in the backup, or S3-compatible object storage you configure and point it at. And if you want invitation and notification emails to work, you'll wire up SMTP yourself. None of this is exotic, but it is a standing chore that never fully goes away, and getting any one piece wrong is how a wiki quietly stops being backed up.

Or let us run it. We host Docmost for people who want the ownership without becoming a part-time database administrator — the Postgres, the Redis, the backups, and the updates handled, with the data still unmistakably yours.

Deploy it in one click

Rolling your own means standing up Postgres and Redis, writing a compose file, terminating TLS, configuring storage and SMTP, and then owning the upgrade path forever. It's doable, and plenty of people enjoy it. It is also an afternoon that turns into a maintenance commitment.

On Caliber Node it's one click. You deploy Docmost in one click, and it comes up with its database, cache, storage, and a real domain already wired together. You get a running wiki in a few minutes instead of a weekend — and you still get the parts that make it genuinely yours: real logs, SFTP access, and export whenever you want it.

First run

1. Deploy Docmost from the Caliber Node app catalog and wait for it to come up on your domain.
2. Open the app and create the first admin account — that's your workspace owner.
3. Create your first space — start with something concrete like "Engineering" or "Company Handbook."
4. Add your first page, try the slash commands, and drop in a table and a diagram to see the editor for what it is.
5. Invite a teammate, watch their cursor appear live in the same page, and you have a working, collaborative wiki.

From there it grows the way a wiki should: more spaces, more pages, permissions tightened where they need to be.

The bigger picture

A company's knowledge base is a strange thing to rent. It's the accumulated memory of how you work — and for that to sit on a vendor's servers, priced by the head, is a quiet kind of dependency. Owning it is the saner default. You keep the pages, the history, the diagrams, and the ability to walk away with all of it, because it was always on your disk. And walking away is a real export, not a support ticket — the same Markdown and HTML on the way out as on the way in.

Docmost makes that ownership practical, and we make Docmost practical to run.

Deploy Docmost in a few minutes →

Or browse the full app catalog to see what else you can own.

One-click self-hosted apps, managed for you — real logs, SFTP, and your data always exportable. Never a black box.