Activepieces Hosting

Open your pod URL and create your local Activepieces account when prompted. Create a flow, choose its trigger, connect the services it needs and test its actions before publishing. The flow-building guide explains triggers and actions.

No. PikaPods sets up and runs Activepieces for you, including OS and app updates and HTTPS. You won't touch Docker or a server. Your data stays available over SFTP if you ever want to move it elsewhere.

You need an account or API credentials for each external service your flow connects to. Those services may charge for access, requests or AI usage. The Community Edition is MIT licensed; commercial enterprise features have separate licensing, as explained in the project’s license summary. Hosting does not unlock those paid features.

Build and manage flows in the web interface at your pod URL. Automations connect to other services through their integrations and APIs; you do not need a separate desktop application to use the workflow builder.

Set up incremental backups to S3 in your pod settings for automatic nightly snapshots, or copy your files over SFTP. We keep whole-server backups for server failures, but they aren't a per-pod restore service, so your own backup is what protects your data.

Activepieces is an open source alternative to Zapier. Its source code is public, so anyone can inspect or improve it, and you aren't tied to one vendor.

No. You add prepaid credit and your pods are billed by the hour from that balance, rounded up to full hours. There are no contracts or minimum terms: delete a pod anytime and billing stops. Optional automatic top-ups keep your pods running without manual payments.

You do. And you're in full control. If you ever want to download, migrate, edit or delete your data, just enable SFTP access to your pod and it will be right there.