What are the minimum VPS requirements for Activepieces?

Activepieces minimum requirements in the RunOnVPS dataset are RAM 4 GB, CPU 2 vCPU, disk 20 GB. Values marked Estimated were not published as complete hardware requirements by the checked source.

What VPS tier does RunOnVPS suggest for Activepieces?

RunOnVPS suggests the 8 GB RAM tier as a starting point. This is our own sizing suggestion derived from the recommended RAM (8 GB), not an official provider recommendation.

Does Activepieces support Docker?

The checked dataset records Docker support for Activepieces as: Yes.

Does Activepieces need a GPU?

Activepieces GPU requirement: Not required. See the source notes on this page for workload-specific exceptions.

Automation / AI / Dev

Activepieces on VPS

Open-source workflow/business automation platform with a visual flow builder and 200+ integrations

See requirements View on GitHub

GitHub stars: 25192
License: MIT (core; ee portions under separate enterprise license)
Docker: Yes
GPU: Not required

Requirements

Minimum and recommended VPS specs

Badges are attached to each value. An estimate is never presented as an official project requirement.

Activepieces hardware requirements
Resource	Minimum	Recommended
RAM	4 GB Official	8 GB Estimated
CPU	2 vCPU Official	4 vCPU Estimated
Disk	20 GB Estimated	Not stated Not stated

Disk figures describe the application footprint recorded in the dataset. Personal media, documents, backups and other user data can require substantially more storage.

RunOnVPS sizing suggestion

Suggested VPS tier

8 GB RAM tier

This is our sizing suggestion, derived from Activepieces’s recommended RAM of 8 GB. It is not an official requirement and it does not guarantee that every workload, plug-in set or media library will fit comfortably.

Affiliate link placeholder — no provider selected

This placeholder intentionally has no URL or affiliate ID in the Day 2 build.

Deployment

Docker & GPU

Docker support: Yes

GPU: Not required

Check the source notes below before assuming a GPU, transcoding workload or machine-learning feature is included in the baseline deployment.

Commercial alternative

What it can replace

Zapier / Make

Activepieces is catalogued here as a self-hosted alternative to Zapier / Make. Feature parity varies, so compare your required workflow before migrating.

Add it to a multi-app VPS estimate →

Source check

Important notes

最低配置为官方数字: the official Self Host (Docker Compose) docs state 'At least 2 vCPU and 4 GB RAM' (checked 2026-10-24). Official docs give no disk minimum, so min_disk is a conservative estimate for the 4-container stack (app/worker/PostgreSQL/Redis images plus database growth). Recommended values are estimates for a small team; the official Production Setup doc instead sizes components separately (App 1 vCPU/1 GB, Worker 0.5 vCPU/1 GB per concurrent flow, managed Postgres 2 vCPU/4 GB, Redis 1 vCPU/1 GB, S3 required). Docker: official Docker Compose install is the recommended path; a single-container hobby install (embedded PGLite + in-memory Redis) also exists. License anomaly: the repo LICENSE file puts everything outside packages/ee/ under 'MIT Expat', with the ee portions under a separate Activepieces enterprise license — GitHub's API therefore reports the license as NOASSERTION. Stars 25192 and not archived, checked via GitHub API on 2026-10-24.

Data source: https://raw.githubusercontent.com/activepieces/activepieces/main/docs/install/options/docker-compose.mdx

Project repository: https://github.com/activepieces/activepieces

Keep comparing