← Automation

ActivepiecesActivepieces

Activepieces Inc.

开源Open source MIT混合Mixed MIT 自托管Self-hosted 低代码Low-code 工作流Workflows partial lifecycle: active 核验Checked 2026-10-30

Activepieces 是开源低代码自动化平台：主体 MIT Expat，只有 ee/ 目录是商业许可区—— 比 n8n 的 SUL 宽松，代价是连接器体量小得多。自托管 + 官方云两条线。

Activepieces is an open-source low-code automation platform: MIT Expat for the main body, only the ee/ directory is the commercial-license zone — looser than n8n's SUL, at the cost of a much smaller connector catalog. Self-hosted + official cloud, two lines.

适合与不适合When to use it, when not to

适合：要 MIT 级许可自由度、要自托管、要能读源码魔改。不适合：要海量现成连接器（先核你要的 piece 存不存在）；要企业功能开箱（SSO 在 ee 线）。

A fit for: MIT-level license freedom, self-hosting, reading and modifying the source. Not a fit for huge ready-made connector catalogs (check whether your piece exists first); out-of-the-box enterprise features (SSO sits on the ee line).

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-21

出品属地Origin: 国外出品foreign-made　Activepieces Inc.（美国）。Activepieces Inc. (US).
国内使用Direct access: 大陆可直连direct OK　activepieces.com/docs 直连实测 200（2026-10-21）。activepieces.com/docs measured 200 direct (2026-10-21).
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-21 检索）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-21); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

8 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: AI pieces 经凭据接各家模型（OpenAI 等）；具体清单未逐条核验。自托管时凭据在你实例上。
AI pieces reach each vendor's models via credentials (OpenAI etc.); the specific list has not been verified item by item. When self-hosted, credentials live on your instance.
运行位置Where it runs: 开源自托管（Docker）+ 官方云两条线；GitHub 25,150★、最近推送 2026-10-21（API 核验，活跃）。
Open-source self-hosting (Docker) + official cloud, two lines; GitHub 25,150★, last push 2026-10-21 (API-verified, active).
本地文件Local files: 自托管实例数据落自有环境；pieces 生态的凭据与执行数据在实例内。
Self-hosted instance data lands in your own environment; the pieces ecosystem's credentials and execution data sit inside the instance.
关机后的任务Tasks after shutdown: 自托管实例常开即承载定时/webhook；官方给 queue worker 模式（细节未逐条核验）。
A continuously running self-hosted instance carries schedules/webhooks; the official docs provide a queue-worker mode (details not verified item by item).
工具与扩展Tools & extensions: pieces（集成）生态 + 社区贡献机制是核心；MCP 支持状态未逐条核验。
The pieces (integration) ecosystem + community-contribution mechanism are the core; MCP support status has not been verified item by item.
上下文与记忆Context & memory: flow 内步骤间的数据传递与变量引用是官方上下文主轴；跨流程的共享记忆机制未逐条核验（未知就说未知）。实例内的执行历史按 flow 持久保存。
Step-to-step data passing and variable references within a flow are the official context main axis; cross-flow shared memory mechanisms have not been verified item by item (unknown means unknown). Execution history within the instance persists per flow.
权限与限制Permissions & limits: 社区版基础角色；SSO/项目等属 ee 目录（商业许可区）——功能分界即许可分界。
Community edition has basic roles; SSO/projects etc. live in the ee/ directory (commercial-license zone) — the feature boundary is the license boundary.
适合什么任务Best for: 适合：要 MIT 主体许可的自托管自动化、要可魔改的低代码。不适合：要企业功能开箱（在 ee 商业线）；要连接器生态与 Zapier 同量级（体量小得多）。
Fits: self-hosted automation wanting an MIT-main license, low-code you can hack on. Does not fit: out-of-the-box enterprise features (in the ee commercial line); a connector ecosystem on Zapier's scale (much smaller).

头号误解Top misconception

把「MIT 主体」读成全仓 MIT——ee/ 目录是商业许可区Reading “MIT at the core” as whole-repo MIT — the ee/ directory is the commercial-license zone
与 Zapier/Make 比连接器数量——体量差距大，先核自己要的集成有没有Comparing connector counts with Zapier/Make — the gap is large; verify the integrations you need exist
把云版与自托管版功能混同——SSO 等在 ee 线Conflating cloud and self-hosted feature sets — SSO etc. are on the ee line

未知项清单Known unknowns

pieces 生态的确切数量（未逐条核验）
MCP 支持状态（未核验到官方文档）
queue worker 模式在社区版的完整边界

The exact count of the pieces ecosystem (not verified item by item)
MCP support status (no official documentation found)
The full boundary of queue-worker mode in the community edition

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-30，内容更新日content updated on 2026-10-21。

类型Type	名称Name	链接Link
docs	Activepieces/Activepieces · LICENSE（MIT Expat + ee 商业区，2026-10-21 直抓核验）Activepieces/Activepieces · LICENSE (MIT Expat + ee commercial zone, direct-fetched & verified 2026-10-21)	https://github.com/Activepieces/Activepieces/blob/main/LICENSE
repo	Activepieces/Activepieces · 仓库（25,150★，最近推送 2026-10-21，GitHub API 核验）Activepieces/Activepieces · repository (25,150★, last push 2026-10-21, verified via GitHub API)	https://github.com/Activepieces/Activepieces
docs	Activepieces · 官方文档Activepieces · official docs	https://www.activepieces.com/docs
changelog	Activepieces/Activepieces · Releases（changelog）Activepieces/Activepieces · Releases (changelog)	https://github.com/Activepieces/Activepieces/releases

实测记录Measured runs

本档未跑工作流搭建实测；结论只覆盖平台能力与权限边界。

This site has not completed measured runs. The closest test protocol is the code-side protocols/framework/_protocol.md (the tool-calling and credential-boundary sections are reusable; no workflow-platform-specific protocol exists on this site yet).