Layer 5 · self-hosting reality check
What it actually takes to self-host Activepieces
The docs say 1 GB. In practice you want 2 GB. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Zapier alternatives, where Activepieces is one of the picks.
Wondering whether you need to at all? Is Zapier free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 1 GB |
|---|---|
| RAM — what it really needs | 2 GB |
| CPU | 2 vCPU |
| Disk | 20 GB |
| Monthly cost | $12–25/mo |
| Setup time | 45 minutes |
| How you install it | docker compose with PostgreSQL and Redis |
| Ongoing maintenance | Active. It is a young project moving quickly. |
| Where it stops scaling | Small to medium automation loads. Worker scaling exists but is less proven than n8n's. |
The thing that catches people out
The licence is not one licence. The core is MIT but a set of enterprise features sits under a commercial licence in the same repository, and the boundary moves as the project develops. Read `LICENSE` in the directory you actually depend on rather than the one at the repository root — this is the same shape that catches people with Chatwoot and Grafana.
When not to self-host Activepieces
You need a large library of pre-built integrations today. The catalogue is growing but is not n8n's, let alone Zapier's.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does Activepieces actually need?
- 2 GB in practice. The documented minimum is 1 GB, which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU alongside it.
- What does self-hosting Activepieces cost per month?
- $12–25/mo This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for active. It is a young project moving quickly.
- How long does it take to set up Activepieces?
- 45 minutes, via docker compose with PostgreSQL and Redis.
- When should I NOT self-host Activepieces?
- You need a large library of pre-built integrations today. The catalogue is growing but is not n8n's, let alone Zapier's.
- What is the most common mistake when self-hosting Activepieces?
- The licence is not one licence. The core is MIT but a set of enterprise features sits under a commercial licence in the same repository, and the boundary moves as the project develops. Read `LICENSE` in the directory you actually depend on rather than the one at the repository root — this is the same shape that catches people with Chatwoot and Grafana.