How to self-host Activepieces in 2026: Zapier-style automation without the task meter

What Activepieces is and why people self-host it

Activepieces is no-code automation in the shape you already know: pick a trigger, chain actions under it, connect the apps you use. Integrations are called pieces — hundreds of them, from Gmail, Slack and Sheets to Notion, Stripe and OpenAI — plus branches, loops, AI steps, and generic webhooks and HTTP for anything without a native piece. If you can build a Zap, you can build an Activepieces flow. MIT licence, 23,500+ GitHub stars, TypeScript.

Skip the manual setup: livemy.app has a one-click Activepieces template — free SSL, persistent storage, and a live builder in about two minutes.

The reason to self-host is one sentence long: task-based pricing punishes automations that actually run. On hosted automation platforms, every run of every flow counts against a quota — the flow that checks something every five minutes is the one that quietly triples the invoice. Self-hosted Activepieces has no task counter. Flows run as often as they need to, and the bill is the price of the server.

The second reason is the usual one for self-hosting anything: the credentials your flows use and the data moving through them stay in your own database, not on an automation vendor's account.

Activepieces or n8n?

The honest comparison, since both are in our template gallery and both solve the same problem:

• Pick Activepieces if you want the gentlest no-code experience, closest to Zapier. Triggers and actions read in plain language, and you get real value without writing a single expression. This is the one to hand to a marketer or an operations person.

• Pick n8n if you want power-user control — a bigger node ecosystem, code steps in JavaScript and Python, and finer-grained data handling. The learning curve is steeper and the ceiling higher. (Its cloud pricing has its own quirks — covered in our n8n pricing breakdown.)

Both self-host at the same flat price, so the cheapest way to decide is to deploy each on a free project and rebuild one real automation in both. An afternoon settles it.

Two ways to self-host Activepieces

Path A: Docker on your own server

Activepieces ships a Docker Compose setup that brings up the app and its database. Around it you'll add the production wrapper yourself: a reverse proxy with SSL, a stable public URL for webhooks, persistent volumes, and an update routine — the project moves quickly. Budget 1–2 hours for a proper first deploy.

Path B: livemy.app one-click template

Pick the Activepieces template, deploy, get a live URL with SSL and the database wired up. Point a custom domain when ready. Flat $10/month on the Maker plan; backups are a $5/month add-on — recommended, since your flows and credentials live in that database.

Five things that quietly break self-hosted Activepieces

1. Webhook triggers point at the wrong URL

Webhook-triggered flows only work if the outside world can reach your instance at a stable public address. If the configured public URL still references a temporary subdomain — or changed when you added a custom domain — every webhook registered with a third-party service fires into the void.

Fix. After any domain change, update the instance's public URL setting, redeploy, and re-test one webhook end to end. Same discipline as any automation host: the URL in the flow must be the URL on the internet.

2. Flows and credentials lost on redeploy

Everything you build lives in the database. Without persistent storage, a container rebuild resets the instance — flows, connections, run history, all gone.

Fix. Verify persistence before building anything real: create a test flow, redeploy, confirm it survived. Then turn on scheduled backups.

3. Polling triggers set too aggressive

Without a task meter, nothing stops you from polling an API every minute — except the API. Third-party services rate-limit, and an over-eager polling trigger gets your credentials throttled or temporarily banned.

Fix. Match the polling interval to how often the data actually changes. Every 15 minutes is enough for almost everything; prefer webhook triggers over polling wherever a piece offers one.

4. Production automations on an experimenting tier

An automation host has one job: fire on time, every time. Free tiers — ours included — are built for experimenting, not for the always-on reliability scheduled flows assume. (Some other hosts' free tiers sleep on inactivity and silently miss schedule slots entirely.)

Fix. Run real automations on a production tier. livemy.app Maker is $10/month flat with a 99.5% uptime SLA — the fit for flows other people or processes depend on.

5. Skipping updates in a fast-moving project

Activepieces ships new pieces and fixes constantly. An instance frozen on a six-month-old version accumulates missing integrations and known bugs — and then a big-jump upgrade is scarier than it needed to be.

Fix. Update monthly-ish. On livemy.app that's one click on redeploy (or a command over MCP); back up before major versions.

What it costs

• Software — $0. MIT-licensed Community Edition, unlimited flows and runs.

• Hosting — $10/month flat on livemy.app Maker (custom domain, SSL, 99.5% SLA), or $5–15/month on a self-managed VPS. Backups +$5/month.

• Runs — unmetered. The flow that fires every five minutes costs the same as the one that fires weekly. This is the whole argument.

Compare that with task-based pricing on hosted automation tools, where a handful of busy flows can outgrow entry tiers within a month — the same dynamic we walked through for n8n's execution quotas. Self-hosting turns the variable into a constant.

FAQ

Is Activepieces free?

The Community Edition is free and open source under the MIT licence, with unlimited flows and runs. Self-hosted, you pay only for the server — about $10/month — with no per-task or per-flow fees.

Which apps can Activepieces connect to?

Hundreds of pieces — Gmail, Slack, Sheets, Notion, Stripe, OpenAI and more — plus generic webhooks and HTTP requests for anything without a native piece. The catalog grows with each release, and pieces themselves are open source.

Is Activepieces a real Zapier alternative?

For the common shape of automation — trigger, actions, branches — yes, and it's the closest self-hosted tool to Zapier's ease of use. Zapier still wins on sheer catalog size; Activepieces wins on unlimited runs, data ownership, and cost at any real volume.

Activepieces or n8n — which should I pick?

Activepieces for the gentlest no-code experience; n8n for power-user control and a bigger ecosystem. Both run at the same flat price self-hosted, so deploy both on free projects and rebuild one real automation in each — the answer becomes obvious quickly.

Can I migrate my Zaps from Zapier?

There's no automatic importer — you rebuild flows by hand. In practice that's faster than it sounds: most Zaps are a trigger and two or three actions, and rebuilding is a good excuse to retire the ones nobody remembers creating.

What does it need to run?

Docker, a database (wired up automatically in the livemy.app template), persistent storage, and a stable public URL for webhook triggers. Around 2 GB of RAM is comfortable for typical use.

Will it auto-update?

On livemy.app, redeploy is one click in the dashboard — or trigger it over MCP. Activepieces releases frequently, so plan a monthly update pass and back up before major versions.

Automation that costs the same whether it works or not

The quiet absurdity of task-based pricing is that your bill grows because your automations succeed. Self-hosted Activepieces removes that tax while keeping the part that made Zapier great — anyone on the team can build a flow. Deploy it, do the webhook-URL check, set sane polling intervals, and let the busy flows run as busy as they like.

→ Deploy Activepieces on livemy.app · One-click template · Flat $10/month · Unlimited runs, custom domain and SSL included.