Self-hosted Notion alternatives, compared
AppFlowy, Outline, Docmost, BookStack and Obsidian compared on the axes that actually decide it: databases, collaboration, mobile and hosting weight.
The short answer
Self-hosted Notion alternatives fall into three groups, and picking the right one is mostly about deciding which part of Notion you actually use. If you want the Notion feel, with pages inside pages and a database view, run AppFlowy. If you want a fast team wiki with excellent search, run Outline. If you want the shortest path from a fresh server to a working workspace, run Docmost.
Two more tools come up constantly in this search and both are honest answers to a different question. BookStack is the pick when what you really need is structured documentation. Obsidian is the pick when the workspace has exactly one member: you.
How these were compared
This is a comparison of documented capabilities, taken from each project's official documentation, its published environment sample, and its public compose file, checked in July 2026. It is not a report of a year in production on each one. Where a limit is stated below, it comes from the project's own docs or its own repository, and the guide says which. That matters, because most roundups of this kind quietly invent the parts they did not check.
The four axes below are the ones people actually ask about, in the order they ask about them: databases and table views, real time collaboration, mobile access, and hosting weight.
AppFlowy: closest to Notion, with a licence catch
AppFlowy is the only project here that seriously copies the Notion data model. Pages, boards, grids and calendar views all exist, the desktop and mobile apps are native, and the local-first design means the app keeps working when the server does not.
Self-hosting is a git clone and a compose file:
git clone https://github.com/AppFlowy-IO/AppFlowy-Cloud
cd AppFlowy-Cloud
cp deploy.env .env
docker compose up -dEdit .env before that last command. FQDN and SCHEME set the public address, and GOTRUE_ADMIN_EMAIL with GOTRUE_ADMIN_PASSWORD set the first admin account. Leaving GOTRUE_ADMIN_PASSWORD=password in place ships a public server with a guessable admin login.
Here is the catch, and it is the single most important fact in this post. AppFlowy Cloud moved to an open-core model, and the AppFlowy Cloud README states the self-hosted Free tier offers "One user seat (per instance)" plus up to three guest editors on pages you share. So the version most people mean when they say "self-hosted Notion" is, at the free tier, a personal workspace with limited guests. Paid self-hosted tiers lift that. Check the current tiers before you plan a ten person rollout on it.
Outline: best search, if you already have single sign-on
Outline is the strongest pure writing and reading experience of the group. Search is fast and actually finds things, the editor is calm, and the structure is collections and nested documents rather than a database engine. Teams that write a lot tend to stay on Outline.
Outline needs PostgreSQL and Redis, and the app listens on port 3000. Two secrets are required, and the sample environment file tells you exactly how to make them:
openssl rand -hex 32 # SECRET_KEY
openssl rand -hex 32 # UTILS_SECRETThen set URL to your public HTTPS address, DATABASE_URL, and REDIS_URL. The one thing that surprises people is authentication. Outline has no built-in username and password login. Its own .env.sample says of the third party sign-in credentials that "at least ONE OF these is required for a working installation or you'll have no sign-in options". Google, Microsoft Entra, Slack, Discord and a generic OpenID Connect (OIDC) provider are the supported options.
That is a real cost. If you do not already run an identity provider, self-hosting Outline means self-hosting one more service before Outline is usable at all. If you do run one, this is a feature, and Outline is probably your answer.
Docmost: the fastest one to stand up
Docmost is the newest of the three and the least work to get running. It has real time collaborative editing, page trees, spaces, comments, and built-in email and password accounts, so there is no identity provider to solve first.
The official installation page gives four commands:
mkdir docmost
cd docmost
curl -O https://raw.githubusercontent.com/docmost/docmost/main/docker-compose.yml
openssl rand -hex 32Put that hex string in APP_SECRET inside the compose file, set APP_URL to the address you will really use, replace STRONG_DB_PASSWORD in both places it appears, then start it:
docker compose up -d
docker compose psEvery service should read running. Open the address in a browser and you should get the Docmost setup page, where you create the first workspace and the first admin user. The stack is Docmost, PostgreSQL and Redis, and the docs put the floor at 2 vCPU and 4 GB of RAM.
One warning worth repeating from the docs: the editor uses WebSockets. Behind a reverse proxy that does not pass WebSocket upgrade headers, the page loads and then edits from a second browser never appear, with no error shown to either user. If you are terminating TLS in front of it, a Traefik reverse proxy handling several apps on one box handles the upgrade correctly by default.
BookStack: when you want documentation, not a workspace
BookStack organises content as shelves, books, chapters and pages. That fixed hierarchy is the whole point. Nobody has to invent a structure, and a year later the wiki is still navigable. It has strong permissions, a good editor, and it is boring in the way infrastructure documentation should be boring.
What it does not have is a database view or block-style editing, so it is not a Notion replacement in the way the first three are. BookStack requires PHP 8.2 or newer and MySQL 8.0 or MariaDB 10.6 or newer. The project does not publish its own Docker image and points at community images instead, the most used being the LinuxServer.io one:
docker pull lscr.io/linuxserver/bookstack:latestBecause the image is community maintained, pin a version rather than tracking latest, and read that image's own documentation for its required variables.
Obsidian: not a server app, and that is the point
Obsidian stores plain Markdown files in a folder on your machine. There is no server, so there is nothing to self-host and nothing to break at 3am. For one person writing notes, it beats every option above on speed and on the certainty that your files outlive the software.
Sync is the part you host. Options are a paid first party sync service, a CouchDB instance driving the community LiveSync plugin, or plain file sync such as Syncthing or a WebDAV share. Real time multi-person editing is not on the list, so if two people need the same page at the same time, Obsidian is the wrong tool.
Databases and tables: where most alternatives stop
This is the axis that decides the search. People who miss Notion usually miss the database: a table with typed fields, several views over the same rows, and filters.
AppFlowy has this, with grid, board and calendar views. Outline, Docmost and BookStack do not. They have documents that can contain simple tables, which is not the same thing, because the rows are not queryable and there is no second view over them. If a Notion database is holding your work, AppFlowy is your only real option in this group, and you should test its free tier seat limit against your team size before committing.
Hosting weight: what each stack actually runs
Docmost and Outline both run three containers: the app, PostgreSQL and Redis. Both sit comfortably on a small VPS. BookStack runs the app plus a MySQL or MariaDB database, which is the lightest of the four.
AppFlowy Cloud is by far the heaviest. Its published compose file brings up nginx, MinIO for object storage, PostgreSQL with the pgvector extension, Redis, GoTrue for authentication, the AppFlowy Cloud service itself, an admin frontend, a worker, a search service, an AI service, and the web app. That is a real database, an object store and roughly ten containers. Budget memory accordingly, and read how Docker Compose services, volumes and networks fit together before you start editing that file.
Which one should you pick
One person, notes and drafts, no server wanted: Obsidian, with your own sync.
One person or a very small group who wants Notion-style databases: AppFlowy, with the free tier seat limit checked first.
A team that writes a lot and already has Google Workspace, Entra or an OIDC provider: Outline.
A team that wants a shared workspace working this afternoon with no identity provider: Docmost.
Infrastructure or product documentation that many people read and few people edit: BookStack.
What breaks after install
Three failures account for most of the support threads on these projects, and all three are configuration rather than bugs.
The first is the app URL. Docmost APP_URL and Outline URL must be the address the browser really uses, including https://. Set it to localhost and put the app behind a domain, and login redirects send users to a machine that is not theirs.
The second is WebSockets, described above. Collaborative editing silently stops working while the app looks healthy.
The third is backups. All of these keep their content in PostgreSQL or MySQL, not in the files you can see, so copying the volume directory of a running database is not a backup you can trust. Dump the database on a schedule and store the dump off the server, the same way scheduled encrypted backups with restic handle any other stateful service. When you are choosing what else to run alongside it, the wider list of apps worth self-hosting this year is a useful sanity check on how much one server should carry.
FAQ
Which self-hosted Notion alternative is closest to Notion itself?
AppFlowy. It is the only one of these projects with a real database concept, meaning typed fields with grid, board and calendar views over the same rows. Outline, Docmost and BookStack are document tools with page hierarchies. They are excellent at documents and they do not replace a Notion database.
Can I self-host Notion itself?
No. Notion is a commercial hosted product with no self-hosted edition and no published server component. Every option in this guide is a separate open source project that covers part of what Notion does. Migration is an export and import, not a lift of the same software.
Do these tools have mobile apps?
AppFlowy ships native iOS and Android apps that talk to your own server once you point them at your instance. Outline and Docmost are used through a mobile browser, and both are usable that way for reading and light editing. Obsidian has full mobile apps, though you supply the sync. BookStack is a responsive web application with no first party mobile app.
How much RAM do I need on a VPS?
Docmost documents a floor of 2 vCPU and 4 GB of RAM, and Outline and BookStack are in a similar range for a small team. AppFlowy Cloud is the exception, because its compose file starts around ten services including PostgreSQL with pgvector and MinIO object storage, so plan for meaningfully more memory and disk there.
Is Outline usable without Google or Microsoft sign-in?
Yes, but not without some identity provider. Outline supports a generic OpenID Connect provider alongside the named ones, so a self-hosted OIDC server works. What it does not support is a plain local username and password, and its own environment sample states that at least one third party provider must be configured or the installation has no sign-in options.