Notion crossed 100 million users in 2025. It also quietly moved Notion AI out of standalone add-on pricing and bundled it exclusively into the Business plan, raising the effective cost of AI access for teams from $8/user/month to $20/user/month. For a 20-person team, that's a jump from $1,920/year to $4,800/year — just to keep the AI features that were available on every plan before.

The per-seat model compounds the problem. Notion charges per member, so every new hire adds to the annual bill. At 50 people on Business, you're paying $9,000–$12,000/year for a workspace that stores your notes and databases.

AppFlowy is the open-source alternative that maps most directly to Notion's feature set. It stores your data locally by default, can be self-hosted on your own server, and costs nothing in per-seat licensing. This guide covers what AppFlowy delivers, where it falls short, and how to actually set it up.

1. What Notion Costs in 2026

Notion's pricing as of August 2026 (always confirm current rates at notion.com/pricing before budgeting):

The key change in early 2026: Notion AI is no longer a standalone add-on available on any plan. It's now bundled exclusively into Business and Enterprise. Teams that were paying $10/user/month on Plus and adding $8/user/month for AI now need Business to maintain that workflow — at nearly double the previous cost.

Here's what that looks like at different team sizes on the Business plan:

Team SizeMonthly CostAnnual Cost
10 people$200/month$2,400/year
25 people$500/month$6,000/year
50 people$1,000/month$12,000/year
100 people$2,000/month$24,000/year

Beyond the per-seat cost, there's the data dependency. Everything your team writes in Notion lives on Notion's servers. For most teams that's fine. For teams in regulated industries — healthcare, legal, finance, government — it's often a compliance problem.

2. What AppFlowy Actually Offers

AppFlowy is built on Rust and Flutter, which gives it native desktop performance rather than the web-app feel of browser-based tools. It's genuinely local-first: your data lives on your device by default, and cloud sync is optional rather than assumed.

The core feature set covers what most teams actually use Notion for:

Documents and wikis: Block-based editor with the same basic primitives as Notion — headings, toggles, callouts, code blocks, embeds, and rich text. The editing experience is responsive and fast because it's a native app rather than a web app loaded in a browser.

Databases: Grid view, board (kanban) view, and calendar view are all available. Relations between databases are supported. Complex relational database views with linked properties are less mature than Notion's implementation, but the fundamentals work.

AI features: AppFlowy has AI writing assistance built in. On the cloud version this requires the Pro plan ($10/month for teams up to 50). On a self-hosted instance you can configure your own AI provider — OpenAI, Anthropic, or a local model — which means AI features at zero per-seat cost if you have your own API key.

Offline access: This is AppFlowy's clearest practical advantage over Notion. The desktop app works fully offline. Changes sync when you reconnect. For teams that work on flights, in areas with unreliable connectivity, or simply want their tools to work without an internet dependency, this matters.

Self-hosting: AppFlowy Cloud — the team collaboration server — can be deployed on your own infrastructure via Docker Compose. The minimum requirement is 4–8GB RAM for active multi-user use. The official documentation covers deployment on any major cloud provider or bare metal.

Data ownership: Self-hosted AppFlowy means your documents, databases, and files never leave your infrastructure. You control the backup schedule, the retention policy, and who has access at the server level.

3. Who Should Consider Switching

The teams that benefit most from AppFlowy fall into distinct categories.

Cost-driven teams at 20+ people. Below 20 people, Notion's Plus plan at $10/user/month is manageable. Above that, especially if AI features matter, the Business plan cost starts looking like a significant monthly line item. A 50-person team saves $9,000–$12,000/year by switching to self-hosted AppFlowy. The migration is a one-time effort; the savings are permanent.

Teams with data residency requirements. Healthcare organizations operating under HIPAA, legal firms handling privileged documents, financial services companies subject to data sovereignty regulations, and government contractors working with sensitive information often cannot use cloud SaaS for their internal knowledge base. Self-hosted AppFlowy resolves this at the infrastructure level: data never leaves your servers.

Developer and engineering teams. AppFlowy's technical profile — Rust backend, Docker deployment, API access, self-hostable AI — maps naturally to teams that already manage their own infrastructure. The setup complexity that would deter a non-technical team is routine for an engineering team that already runs Kubernetes or a self-hosted GitLab instance.

Privacy-conscious individuals and small teams. For solo users or teams under five people who don't need the collaboration layer, AppFlowy's desktop app is a straightforward local notes and database tool with no account required, no data sent anywhere, and no subscription.

4. Where AppFlowy Falls Short

An honest assessment requires naming the gaps.

Relational database maturity. Notion's linked databases — where a property in one database pulls data from another, with rollups, formulas, and filtered views — are more mature and flexible than AppFlowy's current implementation. Teams with complex database structures built in Notion may find AppFlowy's equivalents limited.

Template library. Notion has a large community template ecosystem. AppFlowy's template library is smaller. Teams that rely on community-built Notion templates for specific workflows will need to recreate those in AppFlowy or build from scratch.

Web clipper. Notion's browser extension for clipping web content into your workspace has no equivalent in AppFlowy. Teams that use the web clipper heavily — for research, content curation, or saving articles — will need an alternative workflow.

Collaboration UX. Real-time multi-user editing in AppFlowy Cloud works, but the collaborative experience is less polished than Notion's. For teams where simultaneous document editing is frequent, the difference is noticeable.

Mobile apps. AppFlowy has iOS and Android apps, but they lag behind the desktop experience. Notion's mobile apps are more refined. For teams where mobile editing is important, this is worth testing before committing.

Self-hosting overhead. The free tier comes with the cost of operating your own server: initial setup, periodic updates, backup management, and occasional troubleshooting. This is real ongoing work, even if it's measured in hours per month rather than hours per week.

5. Setting Up Self-Hosted AppFlowy: A Practical Walkthrough

The official deployment path uses Docker Compose. Here's what the process actually involves.

What you need:

Step 1: Provision the server. Any major VPS provider works — DigitalOcean, Vultr, Hetzner, Linode. A 2-CPU, 4GB RAM instance is the practical minimum. Set up your domain's DNS to point an A record at the server's IP address.

Step 2: Clone the AppFlowy Cloud repository. The official repo at github.com/AppFlowy-IO/AppFlowy-Cloud contains the Docker Compose configuration. Clone it onto your server.

Step 3: Configure environment variables. Copy the example .env file and fill in your domain, email provider settings, and optionally your AI API key. The configuration is documented and most values have sensible defaults.

Step 4: Run Docker Compose. A single docker compose up -d command starts all the required containers — the AppFlowy backend, PostgreSQL, Redis, and the web frontend. The first startup takes a few minutes as images are pulled.

Step 5: Configure SSL. Caddy (included in the Docker Compose setup) handles SSL certificate provisioning automatically via Let's Encrypt. Point your domain at the server and SSL is handled without additional configuration.

Step 6: Invite your team. Once the server is running, you access AppFlowy Cloud through your domain. Team members install the AppFlowy desktop or mobile app, select "self-hosted" when signing in, and point it at your server URL.

Total time for someone comfortable with Docker: 1–2 hours. Ongoing maintenance: roughly 1 hour per month for updates and backups.

6. Migrating Your Data from Notion

Notion provides a full export and AppFlowy has a direct import function.

Export from Notion: Go to Settings → Export all workspace content → select Markdown & CSV. Notion generates a zip file containing all your pages as Markdown files and all your databases as CSV exports.

Import into AppFlowy: AppFlowy's import function accepts Notion exports directly. In the desktop app, click the import button, select the Notion export zip, and AppFlowy reconstructs your page hierarchy.

What migrates cleanly: Document text, headings, lists, code blocks, and basic page structure migrate without issues. Simple databases with standard properties also import correctly.

What requires manual cleanup: Complex database relations and rollup formulas don't transfer automatically — these need to be rebuilt in AppFlowy. Embedded content like PDFs and videos need to be re-uploaded. Pages with heavy use of Notion-specific blocks (synced blocks, linked databases with complex views) need manual attention.

Practical advice: Run the import on a test workspace first. Pick your 10 most important documents, import them, and verify the output before migrating everything. For most teams, 80% of the content migrates without issues; the remaining 20% needs varying degrees of cleanup depending on how heavily the team used Notion-specific features.

Plan for the migration to take a full day for a medium-sized workspace — a few hours of technical work, plus time for the team to verify their key documents.

7. Should Your Team Switch?

The decision is straightforward if you're honest about two things: what Notion actually costs you annually, and whether your team has someone who can manage a self-hosted server.

Switch to AppFlowy if: your team is 20+ people on Notion Business and the annual cost is a real concern; you have compliance or data residency requirements that Notion's cloud model can't satisfy; someone on your team is comfortable with Docker and Linux; your team's primary use is documents and basic databases rather than complex relational database structures; or offline access matters for your workflow.

Stay with Notion if: your team depends on the web clipper; you have complex linked databases with rollups and formulas that would take significant effort to rebuild; your team uses Notion AI heavily and doesn't want to manage a separate AI API key; mobile editing is important and you need the more polished Notion mobile experience; or you have no one who can manage server infrastructure.

The cost calculation is the clearest test. For a 25-person team on Notion Business, self-hosted AppFlowy saves $4,500–$6,000 per year. The migration takes roughly one day of technical work. The payback period is measured in weeks, not years.

OSALFinder tracks open-source alternatives to popular SaaS tools. See our Notion vs AppFlowy comparison page for a regularly updated feature and pricing breakdown.

📊 Read the full comparison
Notion vs AppFlowy — pricing, features, migration guide →