AppFlowy

AppFlowy-IO/AppFlowy

Bring projects, wikis, and teams together with AI. AppFlowy is the AI collaborative workspace where you achieve more without losing control of your data. The leading open source Notion alternative.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 1, 2026
1 day ago
Ship score
80/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 75,692 → 76,980 (Aug 18 – Sep 29, 2026)
+824 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
77.1K
Forks
6.1K
Open issues
1K
Watchers
408
Primary language
Dart
Created
Jun 16, 2021
Owner
AppFlowy-IO · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 8 startups in the directory ship primarily in Dart.

Topics

#blog#confluence-alternative#content-management#content-services#documentation#flutter#note-taking#notion-alternative#project-management#task-management#team-collaboration#wiki

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 100%, self-hostable 76%, hosted offering 66%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-01This is the badge for AppFlowy-IO/AppFlowy, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/AppFlowy-IO/AppFlowy.svg)](https://ossean.com/AppFlowy-IO/AppFlowy)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.