Automation
Self-Host Activepieces On Your Own Server
Open-Source Automation With Its Own Database
Build flows that connect your apps, with AI steps and a no-code builder. It runs with its own Postgres database and Redis queue on your server, so every flow and connection stays with you.
What ZipLoom Does When You Launch It
The Publisher's Own Image
ZipLoom runs Activepieces Inc.'s official image (ghcr.io/activepieces/activepieces:0.90.4) on a server you rent from Vultr, DigitalOcean, Contabo or Amazon Lightsail. Nothing is rebuilt or repackaged on the way.
Secrets Generated For You
The 3 secrets this app needs are generated at launch and kept in your project's encrypted vault, never typed by hand or stored in plain settings.
Everything It Needs, Beside It
pgvector/pgvector:0.8.0-pg14 and redis:7.0.7 start next to it on the same server, on a private network the internet cannot reach.
Your Data Stays On Your Server
Its data folders live on your server and are kept across every redeploy and update.
Its Address Set For You
The app is told its own public address at every deploy, on your custom domain with https or on the server's IP.
An Image Vulnerability Scan
At every deploy the image is scanned on your server for known vulnerabilities and the counts are shown in the deploy log. The scan reports; it does not block the deploy.
The Facts
- Publisher
- Activepieces Inc.
- Official image
ghcr.io/activepieces/activepieces:0.90.4- Runs beside it
- pgvector/pgvector:0.8.0-pg14, redis:7.0.7
- Server memory
- 2 GB RAM or more
- Licence
- MIT for the Community Edition; some enterprise features are under Activepieces' commercial licence.
- Links
- Homepage · Documentation
Good To Know Before You Launch
- The first visitor creates the admin account — open the app and set it up right after it deploys.
- Flows run their code directly on your server (the publisher's standard single-server mode), so only add pieces and code steps you trust.
- Add a custom domain so webhooks get a stable https address.