Skip to main content
Activepieces is a self-hosted workflow automation platform that you can deploy in your own infrastructure. This gives you complete control over your data and workflows.

​
Deployment Options

Activepieces offers flexible deployment options to suit different use cases:

Docker

Quick single-container deployment for development and small-scale production

Docker Compose

Multi-container setup with PostgreSQL and Redis for production use

Kubernetes

Scalable production deployment using Helm charts

Cloud Platforms

Deploy on AWS, GCP, Azure, or DigitalOcean

​
Self-Hosted vs Cloud

​
Benefits

  • Full Control: Complete ownership of your data and infrastructure
  • Customization: Modify and extend the platform as needed
  • Privacy: Keep sensitive workflows and data within your network
  • Cost: No subscription fees for the Community Edition

​
Requirements

  • Server infrastructure to host the application
  • Technical expertise to manage deployments
  • Responsibility for updates and maintenance

​
System Requirements

​
Minimum Requirements

For small deployments (< 100 workflows):
  • CPU: 2 cores
  • RAM: 4 GB
  • Storage: 10 GB SSD
  • OS: Linux (Ubuntu 20.04+, Debian 11+, etc.)
For production deployments (> 100 workflows):
  • CPU: 4+ cores
  • RAM: 8+ GB
  • Storage: 50+ GB SSD
  • OS: Linux (Ubuntu 22.04 LTS recommended)

​
Dependencies

Activepieces requires the following services:
1

PostgreSQL 14+

Primary database for storing workflows, executions, and user data
  • Minimum: PostgreSQL 14
  • Recommended: PostgreSQL 15 or 16
  • SQLite can be used for development only
2

Redis 7+

Job queue management using BullMQ
  • Minimum: Redis 7.0
  • Recommended: Redis 7.2+
  • Required for production deployments
3

Node.js Runtime

Built into the Docker image
  • Node.js 20.x (included in container)
  • Bun 1.3.1 for package management

​
Architecture Components

Activepieces consists of several key components:

​
Component Breakdown

The main application server that handles:
  • User authentication and authorization
  • Flow management (CRUD operations)
  • Webhook endpoints
  • REST API for integrations
  • Background job scheduling
Runs on Node.js with Fastify framework.
Static web application served by Nginx:
  • Angular-based UI
  • Flow builder interface
  • Execution logs viewer
  • Configuration management
Served on port 80 by default.
Workflow execution runtime:
  • Processes flow steps sequentially
  • Handles code execution with isolated-vm
  • Manages piece (integration) execution
  • Error handling and retries
Located at dist/packages/engine/main.js
Background job processors using BullMQ:
  • Flow execution jobs
  • Scheduled triggers (polling)
  • Webhook renewals
  • User interaction jobs
Can be scaled horizontally for high throughput.

​
Execution Modes

Activepieces supports different execution modes for running workflows: 
AP_EXECUTION_MODE=SANDBOX_CODE_ONLY
Sandboxed execution uses isolated-vm to run code in a secure V8 isolate with memory limits (128MB per execution). This is recommended for production to prevent malicious code from affecting the host system.
Unsandboxed execution runs code directly in the Node.js process. Only use this for development or trusted environments.

​
Next Steps

Choose your deployment method:

Quick Start

Get started with Docker in 5 minutes

Production Setup

Deploy with Docker Compose

Enterprise Scale

Kubernetes deployment guide