Skip to main content

Deploy ActivePieces

Before using the one-click template, here is a minimal Docker Compose example for running ActivePieces locally or on your own server.

If you're new to Docker Compose, check out our guide on how to self-host a Docker Compose app. You can also browse more examples in our Docker Compose library.

Self-host ActivePieces with Docker Compose (minimal)​

services:
  activepieces:
    image: ghcr.io/activepieces/activepieces:latest
    ports:
      - "3000:80"
    environment:
      AP_ENVIRONMENT: production
      AP_PUBLIC_URL: http://localhost:3000
      AP_POSTGRES_URL: postgres://postgres:postgres@postgres:5432/postgres
      AP_REDIS_URL: redis://redis:6379
    volumes:
      - activepieces-cache:/usr/src/app/cache

  postgres:
    image: postgres:15
    environment:
      POSTGRES_PASSWORD: postgres
    volumes:
      - pgdata:/var/lib/postgresql/data

  redis:
    image: redis:7

volumes:
  pgdata:
  activepieces-cache:

Deploy ActivePieces on Hostim.dev (One-Click)

ActivePieces is an open-source automation platform designed to replace tools like Zapier. It offers a type-safe, extensible framework with over 280 integrations.

🤖 Build powerful automations. Extend with TypeScript. Own your data.

Try it Yourself

Guest project runs for 1 hour. Log in to save and extend to 5 days.

Why Host ActivePieces on Hostim.dev?​

  • One-click Docker deployment
  • Persistent volume included
  • Automatic HTTPS + domain
  • Real-time logs and metrics
  • Fully self-hosted and secure

What's included​

ResourceDetails
Appghcr.io/activepieces/activepieces:0.67.0
DatabasePostgreSQL (auto-provisioned)
CacheRedis (auto-provisioned)
Volume/usr/src/app/cache
DomainFree *.hostim.dev
SSLAuto-enabled
Port80

How to Deploy​

  1. Go to your Hostim.dev dashboard.
  2. Click Create Project → Use a Template.
  3. Select ActivePieces.
  4. choose plan
  5. deploy

Post-Deploy Notes​

  • Add a custom domain under Networking → Domains
  • Extend functionality with the TypeScript SDK
  • Check logs and metrics inside the App panel

FAQ​

How much memory and CPU does ActivePieces need?

For small workflows, 512MB–1GB RAM is usually enough. For heavier or AI-powered flows, 2GB+ RAM is recommended.

Where is data stored?

Workflow definitions and execution history are stored in PostgreSQL. Redis handles job queues and scheduling. Cache lives in the volume mounted at /usr/src/app/cache .

How do I run ActivePieces behind a reverse proxy (Nginx, Traefik, Caddy)?

Set AP_PUBLIC_URL to your final HTTPS URL and forward traffic to container port 80.

Jobs are stuck in “pending”. What should I check?

Ensure Redis is reachable. Verify AP_REDIS_URL and check that the Redis container is healthy.

Why does the dashboard not load correctly?

Most often caused by an incorrect AP_PUBLIC_URL. It must match the exact URL you open in the browser, including https://.

How do I back up my instance?
  • PostgreSQL: pg_dump
  • Redis: optional RDB/AOF snapshot
  • Volume: archive /usr/src/app/cache
Can ActivePieces scale horizontally?

Yes. Multiple app containers can run in parallel as long as they point to the same PostgreSQL and Redis.

How do I update to a newer version?

Docker Compose: docker compose pull && docker compose up -d Hostim.dev: redeploy the app.

Alternatives​

  • n8n
  • Cronicle
  • Node-RED

Source + Docs​

Looking for something else? Browse all templates →

Try it now​

Deploy ActivePieces Now – in less than 60 seconds