Links checked 2026-10-14
Self-hosting Activepieces
The self-hosted route instead of Zapier.
The documented path is a compose stack with a database and a queue, so this is a step past 'one container and go'.
What it is
An open-source automation builder: triggers, actions, branching and AI or MCP steps, assembled from pieces. The core is published openly, with some directories held under a separate enterprise licence.
What you actually need
This is the reader's own hardware and configuration, not a price. We describe what a job needs; we do not put a figure on what self-hosting costs, because that depends on the provider, the term and the disk you choose.
- The server
- A VPS running the compose stack: the application plus its database and queue. This is not a single-container install.
- How it installs
- Docker Compose, following the project's self-hosting documentation.
- Data store
- PostgreSQL, with Redis alongside it for the queue and workers.
- What grows
- The database holds run history and connections; the volume grows with how much you run and how much you log.
Before it is safe to expose
- A public URL for webhooks, with DNS and TLS
- An encryption key for stored connection credentials, backed up off the server
- SMTP if you want the platform to send its own email
The trade-offs, specifically for Activepieces
- The repository splits its licence: the core is open, while some directories sit under a separate enterprise licence. Check which pieces you need before committing a workflow to it.
- Three moving parts — application, PostgreSQL and Redis — mean three things to back up and keep current.
- Integrations are community-maintained, so a piece can lag behind a vendor's API change until someone updates it.
- You are the person who restarts it when a worker wedges, and the person who notices.
And the six things you own from now on
These are true of every tool in this section, including Activepieces. They are also the reason to decide against self-hosting, which is a legitimate decision.
- You own the updates. Security releases have to be applied by you, on your schedule, and a project that stops publishing releases becomes your problem to notice.
- You own the backups, and a backup is not a backup until you have restored from it once.
- You own the uptime. There is no status page to watch and no support line to call when it stops answering.
- You own the security patches, the TLS certificate, the reverse proxy and the firewall in front of it.
- You are the on-call rota. The failure mode nobody plans for is being the only person who knows how the thing was set up.
- The hardware has a running cost and a lifetime. Disks fail, and the replacement is on you.
What you give up
- The managed cloud's upgrades and piece maintenance
- A support contract to escalate to
What you gain
- No per-task billing from a vendor; the ceiling is your own hardware
- Connections and payloads stay on your infrastructure
Elsewhere in the index
The box it runs on
A VPS running the compose stack: the application plus its database and queue. This is not a single-container install. That machine is the purchase this page is really about, and it is the one number we will not invent for you: the right size depends on the provider, the term and the disk, so check it on the provider's own page.
Hostinger
Hostinger's VPS product is the closest fit to a self-hosted application: its own page advertises root access, Docker and NVMe storage, with data centres in several regions.
See Hostinger's plansRead Hostinger's published pricing ↗DigitalOcean
Virtual machines billed as you use them, with separate volumes, snapshots and object storage for the parts you want to keep outside the server.
See DigitalOcean's plansRead DigitalOcean's published pricing ↗Hetzner
Cloud instances and dedicated servers with rates published per instance size, so the cost of a bigger box is visible before you move.
See Hetzner's plansRead Hetzner's published pricing ↗What to check before you buy
- A virtual machine you have root on, not a website plan with a control panel bolted on top.
- Snapshots or automated backups, and where those backups are stored.
- Block storage or object storage for the data that will outgrow the server's own disk.
- What the monthly rate renews at, rather than the first-term rate on the signup page.
- Where the data centre is, if the data has a jurisdiction attached to it.
The “See plans” links go through our own /go/ redirect and some are affiliate links, which pay us if you sign up. The descriptions and trade-offs on this page are written from the project's own documentation and are unaffected. The plain pricing link under each provider is not an affiliate link. See our disclosure.
Frequently asked questions about self-hosting Activepieces
Answers restate the notes on this page or point at the project's own documentation. Self-hosting moves work to you rather than removing it, and these answers say so.
What is Activepieces?
An open-source automation builder: triggers, actions, branching and AI or MCP steps, assembled from pieces. We cover it as a replacement for Zapier.
What do you need to run Activepieces yourself?
Docker Compose, following the project's self-hosting documentation. The requirements table on this page lists the server, the data store, what grows and what else to arrange first. Setup steps are at Activepieces' documentation.
How hard is Activepieces to run yourself?
We rate it Moderate. The documented path is a compose stack with a database and a queue, so this is a step past 'one container and go'.
What are the trade-offs of self-hosting Activepieces?
Our notes list these costs. The repository splits its licence: the core is open, while some directories sit under a separate enterprise licence. Check which pieces you need before committing a workflow to it. Three moving parts — application, PostgreSQL and Redis — mean three things to back up and keep current.
What do you give up by running Activepieces yourself?
You take on what Zapier used to do for you. The managed cloud's upgrades and piece maintenance. A support contract to escalate to. Self-hosting moves that work to you rather than removing it.
What do you gain by running Activepieces yourself?
Our notes list these. No per-task billing from a vendor; the ceiling is your own hardware. Connections and payloads stay on your infrastructure.