Self-hosted Notion alternative: own your team wiki with Outline
A team wiki is the closest thing a company has to a memory: how the deploy works, why pricing is shaped the way it is, what was decided in March and for what reason. Keep that in a hosted tool and you are renting your own memory back, at a price that scales with headcount -- every hire is another seat, so the knowledge base gets more expensive at exactly the rate it gets more valuable. And on the day you decide to leave, the export never quite captures everything: the nesting flattens, the links break, the permissions vanish, and someone spends a week reassembling what your team already wrote once. Outline is the version you own.
What Outline is
Outline is an open-source knowledge base for teams -- the wiki, the docs, the handbook, in one place. Its editor is real-time collaborative: two people in the same document see each other's cursors and edits as they happen, so a meeting can produce one set of notes instead of three drafts to merge later.
It is markdown-first in the way that matters. Markdown shortcuts work as you type, pasted markdown becomes formatted structure, and any document exports back to plain markdown. Your team's writing stays portable text rather than becoming a proprietary blob -- the exit is as clean as the entrance.
Structure comes from collections and nesting: documents live inside collections, and documents nest inside documents, so an engineering collection can hold a runbooks tree next to an architecture tree without a folder taxonomy fight. Full-text search spans all of it. Permissions apply per collection, which is the granularity teams actually think in: the handbook readable by everyone, the runbooks scoped to engineering, the leadership notes private.
Sign-in is delegated to an identity provider -- Slack, Google, or any OIDC-compatible service -- so there is no separate password to manage. On our platform, email-based sign-in also works out of the box, which we will come back to. And there is an API covering documents, collections, and users, so the wiki can be written to and read by automation, not only by people.
The features that actually matter
- An editor people do not fight. Wiki adoption dies on editor friction: if writing a doc feels like filling in a form, people write in chat instead and the knowledge evaporates in a week. Outline's editor is fast, keyboard-driven, and collaborative in real time, which is the difference between a wiki that gets written and one that gets referenced in eulogies.
- Nesting that matches how teams think. Collections hold areas, documents hold topics, and sub-documents hold detail. The structure grows out of the writing instead of being designed up front by whoever cared most about taxonomy that day.
- Search that makes the wiki the default answer. A knowledge base is only used when searching it is faster than interrupting a colleague. Full-text search across every collection you can read is what makes "check the wiki" a habit rather than a scolding.
- Permissions at the collection level. One workspace serves the whole company instead of splintering into a public wiki, a private wiki, and a folder of sensitive docs nobody can find. Who can read and who can edit is decided where the content lives.
- Markdown in, markdown out. Import what you have written elsewhere; export everything you write here. The format your knowledge lives in should not be a retention strategy.
- An API for the documents robots write. Changelogs published from CI, runbooks generated from infrastructure, onboarding checklists stamped out from a template -- the docs that stay accurate are the ones a machine updates, and the API is what makes that possible.
What it's like to run
Outline is a real production stack, not a single container. The application runs alongside PostgreSQL, which holds your documents, and Redis, which backs the real-time collaboration -- and before the first user can log in, an authentication provider has to be configured, with file storage decided somewhere along the way. None of this is difficult, but all of it is work: provisioning the database, wiring connection strings, setting up mail so invites actually send, and making sure backups cover the database rather than just files on disk.
That gap -- between "runs on my machine" and "the place the company keeps its memory" -- is wider for a wiki than for most apps, because the whole point of a knowledge base is to be more dependable than the person you would otherwise ask. A wiki that might be down is a wiki nobody trusts with anything important, and then it is not a wiki, it is a graveyard of drafts.
Running it on Caliber Node
Outline deploys from the Caliber Node app catalog as a complete stack: PostgreSQL and Redis are provisioned and wired to the application automatically, with neither database ever exposed to the internet -- only the app itself gets a public route. The stack shares the resources of your capacity subscription, so the databases are not separate services to size, pay for, or forget to back up.
Sign-in is the part that surprises people. Normally, self-hosting Outline means standing up Slack or Google OAuth credentials before anyone can log in. On Caliber Node, email-based sign-in works out of the box through the platform's built-in transactional mail -- invites and sign-in links simply send, with no OAuth application to register and no third-party workspace required. If you later want Slack, Google, or your own OIDC provider, that path stays open.
The rest is the platform doing its job: HTTPS on your app's subdomain from the first minute, a custom domain when you want the wiki living at your own address, snapshots and backups covering the database where your documents actually live, and SFTP access to your volume.
Per-seat pricing means your knowledge base bills you for growing. Owning it inverts that: you pay for capacity, and the fifth hire and the fiftieth cost the wiki nothing at all. Deploy Outline, move the handbook in, and let the company memory live somewhere the company controls.