head to head · open source

ActivePieces vs puck

ActivePieces has 24,584 GitHub stars, 4,214 forks, 573 open issues and last shipped 2 days ago. puck has 13,342 stars, 977 forks, 200 open issues and last shipped 2 days ago. ActivePieces leads on adoption by 84% (24,584 vs 13,342 stars). ActivePieces is written in TypeScript under a custom or non-standard licence; puck is written in TypeScript under MIT. ActivePieces has attracted 17% as many forks as stars, puck 7%. ActivePieces was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

ActivePieces ★ 25K puck ★ 13K category Productivity & Utilities

← all 20902 open source comparisons

Side by side

ActivePieces puck
GitHub stars ★ 25K ★ 13K
License Custom / other MIT
Written in TypeScript TypeScript
Last push 2026-09-18 2026-09-18
Forks ⑂ 4.2K ⑂ 977
Self-hosting Yes Yes
Data ownership Your server Your server

pick ActivePieces if

  • You weight community size — 25K stars and counting
  • You want the Custom / other license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full ActivePieces profile →

pick puck if

  • You want the puck feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches TypeScript
  • You evaluated both and puck fits your workflow better

full puck profile →

About ActivePieces

ActivePieces is an open source, TypeScript based no code automation platform for building AI workflows and exposing integrations as MCP servers, aimed at both technical and non technical users who want Zapier style automation while keeping control of their own data.

read the full ActivePieces overview →

About puck

Puck is a modular, open source visual editor for React.js that lets teams assemble their own drag and drop editing experiences from their existing React components, and it is aimed at developers building internal systems or commercial products who want to own both the editor and the data behind it.

read the full puck overview →

More in Productivity & Utilities

n8n ★ 205K Excalidraw ★ 132K RustDesk ★ 124K LocalSend ★ 92K AppFlowy ★ 77K OBS Studio ★ 76K

Related comparisons

n8n vs activepieces n8n vs langchain n8n vs browser-use firecrawl vs browser-use n8n vs langgraph n8n vs frigate n8n vs lightpanda n8n vs proxmoxve openclaw vs khoj open-webui vs open-notebook open-webui vs khoj appflowy vs affine appflowy vs memos appflowy vs plane appflowy vs joplin mem0 vs memos n8n vs obs-studio n8n vs sharex n8n vs kap excalidraw vs obs-studio n8n vs snapify excalidraw vs sharex excalidraw vs kap excalidraw vs snapify

More Automation projects

Compare either of these against the rest of the Automation field.

ActivePieces vs n8n ActivePieces vs ProxmoxVE ActivePieces vs LiveKit ActivePieces vs amis ActivePieces vs Windmill ActivePieces vs Botpress ActivePieces vs mitosis ActivePieces vs Automatisch ActivePieces vs Typebot ActivePieces vs cadence ActivePieces vs local-deep-research ActivePieces vs teslamate

Frequently asked questions

Is ActivePieces or puck more popular?

ActivePieces has 24,584 GitHub stars and puck has 13,342. ActivePieces has the larger community by that measure.

Are ActivePieces and puck free?

Both are open source. ActivePieces has no licence declared in this registry, and puck is licensed under MIT. Both are free to self-host.

What is the difference between ActivePieces and puck?

ActivePieces is written in TypeScript and puck in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, ActivePieces or puck?

Choose ActivePieces if you want the larger community (24,584 stars) or its Custom / other licence terms. Choose puck if its feature set, stack or MIT licence fits better. Both are self-hostable.