Dify vs Activepieces

Side by side, as alternatives to Zapier. Rows that differ are highlighted; the strongest value in a row is marked. Unknown means no source yet.

Also replaces Zapier: + n8n + Langflow + Huginn + Windmill

Difylanggenius/dify

Activepiecesactivepieces/activepieces

Zapierpaid product

Cost and coverage

Price

$0 software; you run it

Free (100 tasks per month, two-step Zaps); Professional from $19.99/month; Team from $69/month source ↗

App-to-app workflows

Partly

Yes

Scheduled automations

Partly

Yes

AI agent workflows

Partly

Yes

Webhooks

Partly

Yes

Jobs covered

3 of 4 jobs

4 of 4 jobs

All 4

Popularity and activity (from GitHub)

Stars

159,161Top

25,165

—

Gain this week

Unknown

104

—

Signal

Building history

—

Commits / 4 wk

775Top

496

—

Latest release

1.17.1 · 2026-09-10

0.92.3 · 2026-10-12Top

—

Commits / 12 wk

2,560

1,316

—

People committing / 12 mo

253+

177+

—

Issues opened / closed, 30 days

392 / 319

108 / 81

—

Facts, with sources on each project page

Runs on my machine?Differs

Self-hosted with Docker Compose on your machine or server; Dify Cloud also offered

Self-hosted with Docker; Activepieces Cloud also offered

Hosted by the vendor

Code licenceDiffers

Dify Open Source License: Apache 2.0 with extra conditions (no multi-tenant service without permission; keep the logo and copyright in the frontend); not an OSI licence

MIT (Community Edition); packages/ee and server ee directories under a commercial licence

—

Model weights licenceDiffers

No separate model weights

No model weights

—

Commercial useDiffers

Commercial use allowed, but a multi-tenant service needs written permission and the web frontend's logo and copyright may not be removed

Yes for the MIT Community Edition; enterprise features need a paid licence

—

Paid services needed?Differs

Not required with local models via the Ollama plugin; cloud model APIs, Dify Cloud and Dify Enterprise are optional

None required; enterprise licence and Activepieces Cloud are optional

Subscription

HardwareDiffers

Minimum 2 CPU cores and 4 GiB RAM; on macOS the docs ask for a Docker VM with 2 vCPUs and 8 GiB

Production sizing: app 1 vCPU / 1 GB per ten workers; each worker 0.5 vCPU / 1 GB; Postgres 2 vCPU / 4 GB; Redis 1 vCPU / 1 GB

—

Operating systemsDiffers

Docker on Linux, macOS 10.14+ and Windows (with WSL 2)

Docker or Kubernetes (Helm); host operating systems not listed

—

Setup effortDiffers

Medium; clone the repo, copy .env and run docker compose up

Medium, install script or a single docker run with embedded database

—

Stars over time

Switch to Growth % to compare projects of different sizes fairly.

Dify
Activepieces

Focus a point, use arrow keys, or tap for its value.

Tracked daily since 15 Oct 2026. Dashed history: estimated from public records of when people starred the repo. Lines connect observations only; gaps contain no measured points.

Growth % starts at each project's first observed point in the shown range. Zero-star starts are unavailable.

Notes for a video or post

A plain summary with today's date and a link to the sources. Check each project page before you publish.

Dify vs Activepieces (as alternatives to Zapier)
Figures from RepoQuarry, 22 Oct 2026. Sources: https://repoquarry.dev/compare?ids=dify,activepieces&product=zapier

Zapier: Free (100 tasks per month, two-step Zaps); Professional from $19.99/month; Team from $69/month
Dify: free software; does 3 of 4 Zapier jobs
Activepieces: free software; does 4 of 4 Zapier jobs

- Dify: 159,161 GitHub stars, 2,560 commits in 12 weeks, licence Dify Open Source License: Apache 2.0 with extra conditions (no multi-tenant service without permission; keep the logo and copyright in the frontend); not an OSI licence
- Activepieces: 25,165 GitHub stars, +104 in the last 7 days, 1,316 commits in 12 weeks, licence MIT (Community Edition); packages/ee and server ee directories under a commercial licence

Where they differ:
- Runs on my machine?: Dify Self-hosted with Docker Compose on your machine or server; Dify Cloud also offered; Activepieces Self-hosted with Docker; Activepieces Cloud also offered
- Code licence: Dify Dify Open Source License: Apache 2.0 with extra conditions (no multi-tenant service without permission; keep the logo and copyright in the frontend); not an OSI licence; Activepieces MIT (Community Edition); packages/ee and server ee directories under a commercial licence
- Model weights licence: Dify No separate model weights; Activepieces No model weights
- Commercial use: Dify Commercial use allowed, but a multi-tenant service needs written permission and the web frontend's logo and copyright may not be removed; Activepieces Yes for the MIT Community Edition; enterprise features need a paid licence
- Paid services needed?: Dify Not required with local models via the Ollama plugin; cloud model APIs, Dify Cloud and Dify Enterprise are optional; Activepieces None required; enterprise licence and Activepieces Cloud are optional
- Hardware: Dify Minimum 2 CPU cores and 4 GiB RAM; on macOS the docs ask for a Docker VM with 2 vCPUs and 8 GiB; Activepieces Production sizing: app 1 vCPU / 1 GB per ten workers; each worker 0.5 vCPU / 1 GB; Postgres 2 vCPU / 4 GB; Redis 1 vCPU / 1 GB
- Operating systems: Dify Docker on Linux, macOS 10.14+ and Windows (with WSL 2); Activepieces Docker or Kubernetes (Helm); host operating systems not listed
- Setup effort: Dify Medium; clone the repo, copy .env and run docker compose up; Activepieces Medium, install script or a single docker run with embedded database

Stars show popularity, not quality. Check each project page before publishing.

Want share images and a ready video description? Open a project's creator kit.

Numbers: GitHub, fetched nightly. Facts: read from each project's own documentation, with the source on its page. How we check. langgenius/dify ↗activepieces/activepieces ↗

Dify vs Activepieces

Stars over time

Notes for a video or post

Cookie preferences

Report a problem