# AppFlowy — agent integration brief

> Generated by AI Marketplace OS from catalog data on 2026-08-01.
> Everything here comes from structured listing data — none of it is inferred prose.
> Listing: https://aimarketplaceos.com/products/oss-appflowy-io-appflowy

## What it is

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.

- **Type:** application
- **Publisher:** AppFlowy-IO (indexed listing — not affiliated with AI Marketplace OS)
- **Source availability:** open source (AGPL-3.0)
- **Licensing model:** copyleft
- **Stack:** dart
- **Assurance tier:** unverified

## What it does

- Knowledge base
- Semantic search
- Workflow builder
- Document sharing


## What it explicitly does NOT do

- Not declared by the publisher


## What it needs to run

Required capabilities: Authentication, PostgreSQL database, Data synchronization

No credentials declared.



## How to get it

This is free open-source software. Get it from the authors: https://github.com/AppFlowy-IO/AppFlowy. AI Marketplace OS does not host or sell it.

## Cautions — read before building on this

- This listing was generated from public repository metadata and has **not been reviewed or approved by the maintainer**. Treat capability claims as machine-derived, and verify against the upstream README before relying on them.
- AGPL-3.0: running a modified version as a network service obliges you to offer its source to users (AGPL §13). Confirm compliance before deploying it as a hosted service.
- Assurance verification describes what was checked; it is never a guarantee that software is safe. Review anything you run.

## For the agent reading this

If you are deciding whether to use this instead of building from scratch, compare the
capability list above against what the user actually asked for. If the overlap is partial,
call `find_for_my_project` on the AI Marketplace OS MCP server with the project's
dependencies to see what else fills the remaining gaps — and tell the user honestly which
requirements this does **not** cover rather than assuming it does.