Layer 5 · self-hosting reality check
What it actually takes to self-host AppFlowy
The docs say 512 MB. In practice you want 1 GB for the desktop app; 2 GB for the self-hosted cloud. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Notion alternatives, where AppFlowy is one of the picks.
Wondering whether you need to at all? Is Notion free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 512 MB |
|---|---|
| RAM — what it really needs | 1 GB for the desktop app; 2 GB for the self-hosted cloud |
| CPU | 2 vCPU for AppFlowy Cloud |
| Disk | 20 GB self-hosted |
| Monthly cost | $0 — it runs on the machine you already own, or $12–20/mo if you self-host AppFlowy Cloud for sync |
| Setup time | 20 minutes local; 2 hours for self-hosted sync |
| How you install it | Desktop installer; AppFlowy Cloud is a separate docker compose stack |
| Ongoing maintenance | Active. It is young and moving quickly. |
| Where it stops scaling | Personal and small-team use. The self-hosted cloud is not yet a large-team product. |
The thing that catches people out
The desktop app is local-first and works offline immediately — but multi-device sync needs AppFlowy Cloud, which is a separate self-hosted stack you have to run yourself. People install the app expecting Notion's sync to just be there, then find their notes only exist on one machine. Decide up front whether you need sync, because retrofitting it means standing up the server.
When not to self-host AppFlowy
You need Notion's database views and formulas at parity today. AppFlowy is the closest of the three and still catching up.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does AppFlowy actually need?
- 1 GB for the desktop app; 2 GB for the self-hosted cloud in practice. The documented minimum is 512 MB, which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU for AppFlowy Cloud alongside it.
- What does self-hosting AppFlowy cost per month?
- $0 — it runs on the machine you already own, or $12–20/mo if you self-host AppFlowy Cloud for sync This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for active. It is young and moving quickly.
- How long does it take to set up AppFlowy?
- 20 minutes local; 2 hours for self-hosted sync, via Desktop installer; AppFlowy Cloud is a separate docker compose stack.
- When should I NOT self-host AppFlowy?
- You need Notion's database views and formulas at parity today. AppFlowy is the closest of the three and still catching up.
- What is the most common mistake when self-hosting AppFlowy?
- The desktop app is local-first and works offline immediately — but multi-device sync needs AppFlowy Cloud, which is a separate self-hosted stack you have to run yourself. People install the app expecting Notion's sync to just be there, then find their notes only exist on one machine. Decide up front whether you need sync, because retrofitting it means standing up the server.