AppFlowy

Last reviewed Aug 26, 2026 · 759 words

Treat AppFlowy as two products, because your setup effort and your risk live in different places. Product one is a local-first desktop and mobile app that replaces Notion for a single person: free, AGPL-3.0, 75,954 GitHub stars, and it needs no server at all. Product two is AppFlowy Cloud, the self-hostable sync backend that gets your workspace onto multiple devices and shared with other people. The app is mature. The backend is the newer, still-maturing half, and it alone accounts for the catalogue's Medium difficulty rating.

The app alone covers more than you'd expect

Install AppFlowy on Windows, macOS, Linux, iOS, or Android and you get the familiar Notion shape: pages made of blocks, grids and boards and calendars over the same data, nested wikis, the works. Because the app is local-first (it is built in Dart with Flutter, hence one codebase across all five platforms), every document lives on your disk and everything works offline — no server, no account, no monthly fee. For a lot of people this is the correct stopping point. A single-device notes-and-projects workspace has no sync problem to solve, and skipping the backend means skipping every operational commitment this guide describes. If you are still choosing a tool, the notes category has the full field.

AppFlowy Cloud is a real stack, not one container

The self-hosted backend is where the work is. AppFlowy Cloud ships as a Docker Compose deployment, and it is a proper multi-service stack — Postgres for storage plus supporting services for auth, caching, and file storage — rather than a single tidy container. Budget an evening, not ten minutes, and note the catalogue's 1 GB RAM figure is the floor for the backend, not a sizing recommendation once several people sync real workspaces. The payoff is real-time collaboration and multi-device sync where the server is yours, so nobody's product pivot or pricing change can hold your second brain hostage. The honest caveat, straight from the catalogue's cons: this backend is years younger than the app it serves. First released in 2021, AppFlowy spent its early life purely local, and the cloud half still moves fast. Read release notes before upgrading, and back up the Postgres volume before every version bump.

As a Notion replacement, the gaps are integrations, not editing

Day-to-day writing and databases hold up well against Notion, and there is an importer for getting your existing Notion export in. What you give up is the ecosystem: Notion's thousands of integrations, its public API surface, its web-first sharing where any page becomes a link anyone can open. AppFlowy is strongest for workspaces whose value is the content itself — personal knowledge bases, team wikis, project boards — and weakest when your Notion is really a lightweight app platform wired into six other SaaS tools. The broader switching math is in the Notion alternatives guide, and if you are weighing it against its closest open-source rival, see AFFiNE vs AppFlowy.

AGPL plus local-first is a strong ownership story

Two properties compound here. The AGPL-3.0 license means the project cannot quietly go proprietary-cloud-only, and the local-first architecture means your documents are on your own disk in the app's own storage even when a sync server exists. That combination puts a floor under the worst-case scenario: if AppFlowy the company disappeared tomorrow, your data is local and the entire stack is source-available to keep running. Very few Notion-shaped products can say both halves of that sentence.

What I'd do

Start with just the app, from appflowy.io, and use it for two weeks with no server anywhere — that costs nothing and tells you whether the editor fits your brain, which no amount of infrastructure will fix if it doesn't. If it sticks and you need sync, self-host AppFlowy Cloud on a box you already run Docker on, put it behind your existing reverse proxy, and schedule Postgres backups before you invite a second user. If you need sync but cannot commit to operating a young multi-service backend, use the official hosted cloud for now and keep the self-host option in your back pocket; local-first means switching later is a migration measured in minutes, not weekends. My default for a solo user in 2026: local app only, plus your normal machine backup covering its data directory.