[{"data":1,"prerenderedAt":236},["ShallowReactive",2],{"seo-verification":3,"blog-appflowy-agpl-archived-docmost-only-notion-alternative-en":6},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"key":7,"data":8},"blog-appflowy-agpl-archived-docmost-only-notion-alternative-en",{"id":9,"slug":10,"slugs":11,"title":15,"excerpt":16,"readTime":17,"views":18,"isPinned":19,"publishedAt":20,"updatedAt":21,"category":22,"categories":27,"featuredImage":29,"bgImage":30,"posterImage":31,"relatedSolution":32,"intro":35,"sections":36,"ctaTitle":177,"ctaBody":178,"ctaButton":179,"ctaUrl":180,"relatedPosts":181},425,"appflowy-agpl-archived-docmost-only-notion-alternative",{"fr":12,"en":10,"ar":13,"es":14},"appflowy-agpl-archive-docmost-seule-alternative-notion","أرشفة-appflowy-agpl-docmost-البديل-الوحيد-لـ-notion","appflowy-agpl-archivado-docmost-unica-alternativa-notion","AppFlowy AGPL archived: Docmost, the only Notion alternative left","AppFlowy-Cloud AGPL archived September 2026: what changes for your team and why Docmost is now the only truly open-source Notion alternative.",10,0,false,"2026-10-09T00:00:00+00:00","2026-10-09T22:36:09+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":25},5,"Comparison","comparatif","bg-info\u002F10 text-info",[28],{"id":23,"name":24,"slug":25,"color":26,"icon":25},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fappflowy-agpl-archive-docmost-seule-alternative-notion-poster.svg",{"categorySlug":33,"appSlug":34},"collaboration-productivity","docmost","In September 2026, AppFlowy-IO archived its AppFlowy-Cloud repository under AGPL. The multi-user server is no longer distributed as open source — it has moved to a proprietary commercial codebase. For teams that self-hosted AppFlowy to keep control of their data, this is a structural shift. One tool remains — Docmost — whose core is published under AGPL-3.0 and is actively maintained. This article explains what changed, what it means in practice, and how to move to a solid foundation.",[37,41,51,54,95,98,102,105,114,133,160,163,166,169],{"type":38,"title":39,"body":40},"h2","What AppFlowy's AGPL repository archiving actually changes","AppFlowy had two distinct parts: the client application (Flutter + Rust, still active) and AppFlowy-Cloud, the multi-user collaboration server. It is this second repository — `AppFlowy-IO\u002FAppFlowy-Cloud` — that was archived on September 11, 2026 by the organization.\n\nThe organization now directs users to `AppFlowy-SelfHost-Commercial`: a repository whose codebase is proprietary. You can still deploy AppFlowy as a server, but no longer under a free license. This is not a license change on the same code: it is a closed commercial fork that replaces the public repository.\n\nFor teams that cited the AGPL license as a deployment condition — compliance requirements, IT policy, client contracts — that argument disappears overnight. And for those who chose AppFlowy specifically because an organization shutting down would not leave users stranded, the irony is real: the piece that manages team collaboration is no longer auditable.",{"type":42,"title":43,"items":44},"ul","What stays the same — and what actually changes",[45,46,47,48,49,50],"The AppFlowy client application remains open source (AGPL-3.0) and receives regular updates — v0.14.8 released October 8, 2026.","In solo or local mode, AppFlowy still works: archiving does not disable anything on the client side.","The multi-user server is no longer under a free license: no third-party security audit can cover the commercial codebase.","Security patches for the server side will not be released as open source. A CVE on the server can no longer be independently verified.","The community that maintained forks and plugins around AppFlowy-Cloud has lost its base: a fork of the last AGPL commit exists, but receives no downstream patches.","The forced migration to the commercial server introduces a vendor dependency that AGPL was precisely designed to avoid.",{"type":38,"title":52,"body":53},"Docmost: what AGPL still covers in 2026","Docmost is a collaborative knowledge base published under AGPL-3.0 on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocmost\u002Fdocmost\">github.com\u002Fdocmost\u002Fdocmost\u003C\u002Fa>. Its distribution model resembles what AppFlowy once promised: a fully free core, with opt-in commercial extensions for large organizations.\n\nThe Open Source edition covers the essentials: hierarchical spaces and pages, real-time collaborative editing, comments, version history, granular space permissions, and RTL support (added in v0.96.0 — September 2026). No member caps, no features locked behind a paywall in the base edition.\n\nBusiness and Enterprise editions add audit, DOCX export, and governance features for teams that need them — but they layer on top of an Open Source base that remains complete. The AGPL-3.0 license on the core requires any network service operator who modifies the code to publish those modifications: this is the guarantee that the server code handling your documents remains auditable.",{"type":55,"title":56,"headers":57,"rows":61},"comparison","AppFlowy-Cloud AGPL vs Docmost — status as of October 9, 2026",[58,59,60],"Criterion","AppFlowy-Cloud (AGPL)","Docmost",[62,66,70,74,78,81,85,87,91],[63,64,65],"Server license","AGPL-3.0 → archived Sept. 2026","AGPL-3.0 active",[67,68,69],"Server repository","Archived (read-only)","Active, v0.96.0 (Sept. 2026)",[71,72,73],"Server security patches","No more public patches","Published on GitHub",[75,76,77],"Real-time collaboration","Yes (client)","Yes (server + client)",[79,80,80],"Browser-based editing","Yes",[82,83,84],"Space permissions","Limited in AGPL","Included in free edition",[86,80,80],"Version history",[88,89,90],"RTL support (Arabic)","Partial","Full since v0.96.0",[92,93,94],"Docker self-hosting","AppFlowy-SelfHost-Commercial (proprietary)","Official Docker Compose",{"type":38,"title":96,"body":97},"Why an active client repository does not offset server archiving","A common argument in discussion threads: the main `AppFlowy-IO\u002FAppFlowy` repository — the desktop and mobile application — is still active. That is true. But this argument conflates the client layer and the server layer.\n\nIn a team deployment, the server handles authentication, data synchronization, permissions, and page storage. It is the component that receives your documents. It is the component that enforces access rules. The client application, however open source, does not change the nature of the component it communicates with.\n\nStaying on the last AGPL commit of AppFlowy-Cloud means: no future security fixes, progressive incompatibilities with the client (which keeps evolving), and an unmaintained codebase. This is the definition of short-horizon technical debt.",{"type":99,"title":100,"body":101},"tip","What the AGPL license says about this case","AGPL-3.0 requires that a network service that modifies the source code distribute its modifications. It does not require a publisher to continue developing an open source project. A publisher can archive a repository and move to a commercial model: that is legal. What AGPL guarantees is that already-distributed code remains redistributable. What it does not guarantee is that this code will receive security patches. Hence the long-term importance of an active community around the repository — or a project whose publisher has a commercial interest in maintaining the open source core.",{"type":38,"title":103,"body":104},"Migrating from AppFlowy to Docmost: what to plan for","AppFlowy and Docmost do not share a native common export format. The cleanest migration goes through Markdown export from AppFlowy (available from the client interface) and import into Docmost. Images and file attachments require separate handling.\n\nDocmost handles Markdown file imports and hierarchical page structures. For large volumes, bulk import via the API is the most reliable path.\n\nFour things to check before switching: the structure of your AppFlowy spaces (one space = one Docmost space), third-party integrations connected to AppFlowy-Cloud (webhooks, automation scripts), group-based permissions, and users without a verified email who will not pass Docmost's standard invitation flow.",{"type":42,"title":106,"items":107},"Prerequisites for hosting Docmost on a VPS",[108,109,110,111,112,113],"Minimum 2 vCPU and 4 GB RAM — sufficient for a team of 20 to 50 members.","Docker and Docker Compose installed on the server.","A domain name with a valid TLS certificate — Docmost does not serve plain HTTP traffic.","A reverse proxy (nginx or Caddy) to terminate TLS and route to the Docmost container.","A persistent volume for the PostgreSQL database and attached file storage.","An SMTP server or transactional email relay for team invitations.",{"type":115,"title":116,"steps":117},"steps","Deploy Docmost on a VPS in 5 steps",[118,121,124,127,130],{"title":119,"body":120},"Prepare the server","Connect to your VPS via SSH. Install Docker and Docker Compose:\n\n```bash\ncurl -fsSL https:\u002F\u002Fget.docker.com | sh\napt install -y docker-compose-plugin\n```\n\nVerify that ports 80 and 443 are open in your firewall.",{"title":122,"body":123},"Fetch the official configuration","Clone the repository or download the `docker-compose.yml` directly from the `docmost\u002Fdocmost` repository:\n\n```bash\nmkdir -p \u002Fopt\u002Fdocmost && cd \u002Fopt\u002Fdocmost\ncurl -O https:\u002F\u002Fraw.githubusercontent.com\u002Fdocmost\u002Fdocmost\u002Fmain\u002Fdocker-compose.yml\ncurl -O https:\u002F\u002Fraw.githubusercontent.com\u002Fdocmost\u002Fdocmost\u002Fmain\u002F.env.example\ncp .env.example .env\n```",{"title":125,"body":126},"Configure environment variables","Edit `.env` and set at minimum:\n\n- `APP_URL`: your domain (`https:\u002F\u002Fwiki.your-domain.com`)\n- `APP_SECRET`: a long random string (generate with `openssl rand -hex 32`)\n- `DATABASE_URL`: keep the default value if using the Compose PostgreSQL\n- `SMTP_HOST`, `SMTP_PORT`, `SMTP_USERNAME`, `SMTP_PASSWORD`: your email relay",{"title":128,"body":129},"Start the containers","```bash\ndocker compose up -d\n```\n\nDocmost starts with PostgreSQL and Redis. Verify all three containers are `Up`:\n\n```bash\ndocker compose ps\n```\n\nThe first access through your domain triggers the admin account creation wizard.",{"title":131,"body":132},"Configure TLS reverse proxy","Point your domain to the VPS IP. With nginx, add a vhost that proxies to Docmost's internal port (default `3000`) and terminate TLS with Let's Encrypt:\n\n```bash\napt install -y certbot python3-certbot-nginx\ncertbot --nginx -d wiki.your-domain.com\n```\n\nRestart nginx. Docmost is now accessible over HTTPS.",{"type":55,"title":134,"headers":135,"rows":140},"Notion \u002F Docmost \u002F AppFlowy — what you actually pay",[136,137,138,139],"Tool","Server cost (team of 20)","Server code license","Security updates",[141,146,151,156],[142,143,144,145],"Notion Business","$400\u002Fmonth (AI included)","Proprietary SaaS","Notion's responsibility",[147,148,149,150],"AppFlowy + commercial server","Infrastructure + publisher license","Proprietary (since Sept. 2026)","Publisher's responsibility",[152,153,154,155],"Docmost Open Source","VPS cost only","AGPL-3.0","Published on GitHub, auditable",[157,158,159,155],"Docmost Business","VPS cost + Business license","AGPL-3.0 (core)",{"type":38,"title":161,"body":162},"What AppFlowy's archiving says about the open-core model","AppFlowy is not the first project to take this step. The pattern is documented: a tool starts under a permissive or copyleft license, gains popularity, raises funding, and progressively reserves the server code. What this archiving illustrates is the limit of the open-core model when the commercial core is the server.\n\nThe distinction that matters for a technical lead: a project whose publisher draws revenue from the server license has a direct interest in making that server difficult to replace. A project whose publisher draws revenue from Enterprise editions — built on a stable open source core — has an interest in keeping that core in good shape. This is the tension AGPL attempts to reduce: by requiring publication of modifications, it makes the core harder to close.\n\nDocmost follows the second model. Its AGPL core is the foundation on which teams choosing to self-host place their trust. Removing that foundation would destroy the value proposition the project sells to its Business and Enterprise customers.",{"type":99,"title":164,"body":165},"Checking the health of an open source project before migrating","Before migrating a team knowledge base to a self-hosted tool, three signals to check: commit frequency on the server repository (not just the client), the CVE disclosure policy, and the publisher's business model. A project with no revenue or whose revenue comes exclusively from SaaS has little incentive to maintain the self-hosted version. A project whose paying customers self-host has a strong incentive.",{"type":38,"title":167,"body":168},"Docmost in production: things to know","Docmost has been stable in production since late 2025. A few things to know before a team deployment.\n\n**Backups**: data lives in PostgreSQL and in the file storage volume. An automated daily backup of both is sufficient. `pg_dump` scheduled via cron, and `rsync` or an S3 snapshot for attachments.\n\n**Updates**: Docmost publishes regular releases — approximately one per month in 2026. The procedure is a `docker compose pull` followed by `docker compose up -d`. Schema migrations are applied at startup. Read release notes before updating: some versions introduce non-reversible migrations.\n\n**SSO authentication**: Docmost supports SAML 2.0 and OIDC in Business and Enterprise editions. The Open Source edition handles email-based authentication and invitations. For teams with an LDAP\u002FAD directory, the Business edition is required.\n\n**Performance**: on 2 vCPU \u002F 4 GB RAM, Docmost comfortably handles 20 to 50 simultaneously active members. Beyond 100 members with heavily used spaces, plan for 4 vCPU \u002F 8 GB and a dedicated PostgreSQL node.",{"type":42,"title":170,"items":171},"Why host Docmost on a dedicated VPS rather than shared hosting",[172,173,174,175,176],"Docmost requires Docker: shared hosting does not offer it.","PostgreSQL must be accessible from the container: most shared plans do not provide access to a local PostgreSQL instance.","Persistent volumes for attached files must survive restarts: a VPS with NVMe storage provides this guarantee.","Root access is required to configure the TLS reverse proxy and firewall rules.","Vertical scalability of a VPS — adding RAM or CPU without migration — covers team growth without infrastructure overhaul.","Your Docmost workspace on a ServOrbit VPS","Docmost runs on 2 vCPU \u002F 4 GB RAM — a VPS Start is enough for a team of 20 to 50 members. Root access, pre-installed Docker, dedicated IPv4, European data centers.","Explore Cloud VPS","\u002Fvps-cloud",[182,198,215],{"id":183,"slug":184,"slugs":185,"title":189,"excerpt":190,"readTime":17,"views":18,"isPinned":19,"publishedAt":191,"updatedAt":192,"category":193,"categories":194,"featuredImage":29,"bgImage":30,"posterImage":196,"relatedSolution":197},309,"notion-ai-bundled-migrate-to-docmost-or-appflowy-in-2026",{"fr":186,"en":184,"ar":187,"es":188},"notion-ai-bundle-alternatives-self-hosted-2026","بديل-notion-المستضاف-ذاتيا-docmost-أو-appflowy-2026","notion-ai-incluido-migrar-a-docmost-o-appflowy-en-2026","Notion AI bundled: migrate to Docmost or AppFlowy in 2026","Notion bundled AI into Business at $20\u002Fuser\u002Fmonth. Two self-hosted alternatives: Docmost (AGPL-3.0) and AppFlowy — VPS requirements and export steps.","2026-08-28T00:00:00+00:00","2026-09-07T11:26:10+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":25},[195],{"id":23,"name":24,"slug":25,"color":26,"icon":25},"\u002Fblog\u002Fcovers\u002Fnotion-ai-bundle-alternatives-self-hosted-2026-poster.svg",{"categorySlug":33,"appSlug":34},{"id":199,"slug":200,"slugs":201,"title":205,"excerpt":206,"readTime":207,"views":18,"isPinned":19,"publishedAt":208,"updatedAt":209,"category":210,"categories":211,"featuredImage":29,"bgImage":30,"posterImage":213,"relatedSolution":214},342,"notion-2026-price-increase-docmost-self-hosted",{"fr":202,"en":200,"ar":203,"es":204},"notion-hausse-tarifaire-docmost-self-hosted","notion-2026-ziyadat-assaar-docmost-self-hosted","notion-2026-aumento-precios-docmost-self-hosted","Notion 2026 price hike: migrating to self-hosted Docmost","Notion bundled AI into its Business plan in 2026 with a price increase. Is Docmost (AGPL-3.0) a viable self-hosted alternative for agencies?",9,"2026-09-09T00:00:00+00:00","2026-09-09T21:41:07+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":25},[212],{"id":23,"name":24,"slug":25,"color":26,"icon":25},"\u002Fblog\u002Fcovers\u002Fnotion-hausse-tarifaire-docmost-self-hosted-poster.svg",{"categorySlug":33,"appSlug":34},{"id":216,"slug":217,"slugs":218,"title":222,"excerpt":223,"readTime":224,"views":18,"isPinned":19,"publishedAt":225,"updatedAt":192,"category":226,"categories":232,"featuredImage":29,"bgImage":30,"posterImage":234,"relatedSolution":235},148,"how-to-self-host-docmost-on-a-vps",{"fr":219,"en":217,"ar":220,"es":221},"self-host-docmost-vps","كيفية-استضافة-docmost-ذاتيا-على-vps","como-autoalojar-docmost-en-un-vps","How to Self-Host Docmost on a VPS","Deploy Docmost on your VPS for a self-hosted team wiki with real-time collaboration. Open-source Notion and Confluence alternative — Docker Compose in 15 minutes.",3,"2026-01-28T00:00:00+00:00",{"id":227,"name":228,"slug":229,"color":230,"icon":231},7,"Self-hosting","self-hosting","bg-indigo-500\u002F10 text-indigo-400","cloud",[233],{"id":227,"name":228,"slug":229,"color":230,"icon":231},"\u002Fblog\u002Fcovers\u002Fself-host-docmost-vps-poster.svg",{"categorySlug":33,"appSlug":34},1791585703726]